cannot access 'directory': Input/output error

[winmos]

Hi, I tried to install the program on a headless aws-server, but after mounting I get the above error message. Any ideas, what might be the case here? Thanks so much! Winfried

[astrada]

Have you tried remounting with -debug and checking the log files for errors?

[winmos]

i tried, but I'm not much wiser now...

google-drive-ocamlfuse -debug ~/drv

gives me the following message:

Starting application setup (label=default, base_dir=).
[0.000067] TID=0: Loading configuration from /home/ubuntu/.gdfuse/default/config...done
Opening log file: /home/ubuntu/.gdfuse/default/gdfuse.log

after that the procedure hangs.

there are no errors in gdfuse.log:

[0.000245] TID=0: Setting up default filesystem...
[0.000257] TID=0: BEGIN: Saving configuration in /home/ubuntu/.gdfuse/default/config
[0.000344] TID=0: END: Saving configuration in /home/ubuntu/.gdfuse/default/config
[0.000362] TID=0: Loading application state from /home/ubuntu/.gdfuse/default/state...done
Current version: 0.7.17
Docs mode not changed!
Setting up cache db...done
Setting up CURL...done
Refresh token already present.
[0.001362] TID=0: Starting filesystem /home/ubuntu/drv
[0.003130] TID=1: init_filesystem
[0.003171] TID=1: Starting flush DB thread (TID=2, interval=30s)
[119.416039] TID=0: Exiting.
Stopping flush DB thread (TID=2)...done
Flushing cache...
Storing clean shutdown flag...done
CURL cleanup...done
Clearing context...done

[magicknight]

same here. os: ubuntu 18.04

[astrada]

@magicknight: do you see any error in the log files?

[dmorand17]

I'm getting the same behavior in 18.04

[astrada]

@dmorand17 do you get an input/output error? Can you reproduce after remounting with -debug and send the logs to [email protected]? Thanks!

[dmorand17]

@astrada there was an issue refreshing the token, I removed my .gdfuse/default directory and restarted, and things corrected themselves. Thanks!

[basharkhan6]

same here

[xperseguers]

I constantly get this problem, removing the .gdfuse/<label> directory, reauthenticating, and mounting, it works, but all of a sudden, after 1 min or so, I cannot access it anymore:

d?????????  ? ?        ?         ?            ? gdrive

the only way I find is deleting the configuration and starting over!

Using Ubuntu 18 LTS, kernel 4.15.0-88-generic.

[astrada]

You should remount with -debug and check the logs after you get the error.

[xperseguers]

By “everything” I meant that as well because I looked for similar but reports before commenting. Nothing, -debug shows nothing, nor does the log file, it just stops working :(

[astrada]

You get that line with question marks when the file-system is still mounted but the process was killed. You should check with ps if the process is still running, and if not you should try to understand what it's killing it (maybe an out of memory error)?

[xperseguers]

OK, will check, thanks for the inner detail. Sounds strange and worrying if mounting a gdrive requires an enormous and indecent amount of RAM but worth double-checking.

[volupheles]

Having the same issue on ubuntu 18.04. Will work the first time, but freeze up after a while. Have plenty of RAM

[jagauthier]

I have two machines that i use to to mount and backup files to my Google Drive. This exact thing happens about every 7-10 days. It's solved by deleting the .gddfude/default directory, running google-drive-ocamlfuse -headless -id -secret and getting a new token. I must do this on each system. The token is always the same, but I still must go through the process.

[jagauthier]

This occurred again yesterday, making it about a week in between.

[valentinloiseau]

Same here on Ubuntu 20.04.2. After removing .gdfuse/default as advised here, when running google-drive-ocamlfuse -headless -id -secret nothing happens. Reboot os doesn't change anything. How is your exact workflow to rerungoogle-drive-ocamlfuse @jagauthier?

[jagauthier]

Here's what I've been doing: rm -r .gdfuse/default/ google-drive-ocamlfuse -debug -headless -id -secret Then I get prompted for a token, and I go to the provided web address and get it. I enter the token in, and done.

[valentinloiseau]

Thanks @jagauthier! I said nothing happens when runnning google-drive-ocamlfusez after deleting the conf but mounting the folder seems to take a while.

[T-G-M]

I kept running into this issue with my headless servers on AWS:

I worked around it by installing xrdp desktop app https://linuxconfig.org/ubuntu-20-04-remote-desktop-access-from-windows-10 on to the server which gave me a full set of tools to connect through the Google prompt job done… I also find it quite useful to XRDP into the server and run some of my processes locally….

Hope this is useful

Terence Mothers

TSIG – Because Everything Happens Somewhere…

From: Valentin Loiseau @.> Sent: 22 May 2021 21:44 To: astrada/google-drive-ocamlfuse @.> Cc: Subscribed @.***> Subject: Re: [astrada/google-drive-ocamlfuse] cannot access 'directory': Input/output error (#607)

Same here on Ubuntu 20.04.2. After removing .gdfuse/default as advised here, when running google-drive-ocamlfuse -headless -id -secret nothing happens. Reboot os doesn't change anything. How is your exact workflow to rerungoogle-drive-ocamlfuse @jagauthier https://github.com/jagauthier ?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/astrada/google-drive-ocamlfuse/issues/607#issuecomment-846461307 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACVV2JBITPTXCNFB27SQM63TPAJR5ANCNFSM4KPM76WQ . https://github.com/notifications/beacon/ACVV2JFNJRDSA74QA7J6QX3TPAJR5A5CNFSM4KPM76W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGJZ7S6Y.gif

[iambenmitchell]

Randomly got this issue too. Only noticed after my backups had suddenly stopped running for 7 days. I have a script that backs up a directory at 3am every morning and uploads a encrypted zip to my google drive. Also have another one that deletes zips older than 7 days. All my backups are in my trash and the directory was empty. Seems it started having issues 7 days ago. Deleted the config folder and re-authenticated and it seems to be working now.

Any long term fix?

[guyster104]

I am having this problem also. I just installed google-drive-ocamlfuse on two computers, running Ubuntu Mate 21.04. I went through the process of allowing gdfuse to access Google, and I'm getting the input/output error. If I cd into the mountpoint directory, it will give me the I/O error when I perform an ls, but then will proceed to list the folders. I can't see them at all, if I access it through the Mate file manager though. Is there anything specific I need to be looking for in the logs?

[iambenmitchell]

This is still an issue when using headless

[iambenmitchell]

root@mail:~# google-drive-ocamlfuse -debug /mnt/googleDriveStarting application setup (label=default, base_dir=).
[0.000951] TID=0: Loading configuration from /root/.gdfuse/default/config...done
Opening log file: /root/.gdfuse/default/gdfuse.log

root@mail:~# cd /mnt
root@mail:/mnt# ls
ls: cannot access 'googleDrive': Input/output error
googleDrive
root@mail:/mnt# 

[JVTEAM]

Had this issue arise out of nowhere after several weeks of no problems.
This is the error when trying to open the google drive "cannot open directory '.': Input/output error"

When I run the debug command listed above it hangs on the log

Deleting the folder and trying again did make it work, however once I reboot it's back to the same issue.

[baagiiSW]

Any update on the issue? My setup is Centos 7 and opam 4.02.3, google-drive-ocamlfuse 0.7.20. And "Current version: 0.7.20 Docs mode not changed! Setting up cache db...done Setting up CURL...done" this is the last of the gdfuse.log.

Not successfull mounting.

[nosuz]

Hi,

I met the similar error. But the error message was a little bit different.

$ ls gdrive ls: reading directory 'gdrive': Input/output error

In my case, clearing cache files under .gdfuse/default/cache and remount a drive solved the problem.

I hope this will help you.

Thank you,

[JadeFabrice]

Hi, same problem here on a BananaPI M2 Berry with Armbian. Clearing the cache didn't solve, had to delete all .gdfuse/default to get it working again. Anyway this is a great project, keep going on! Thanks