Google-drive-ocamlfuse: cannot write to google drive

[Erik]

I installed "google-drive-ocamlfuse" on my mageia installtionss and found that it is impossible to write filles to the folder that is linked to my "my-drive" on google.com. I getnthis error:

Could not write to file /home/[my user name]/GoogleDrive/[my file name]

On installations of Linux Mint and Rosa Linux I do not have this probem. So it must be some setting in Mageia. I did not have this problem before.

Is there anyone who recognizes this problem, knows a solution?

Greetings,

Erik Jan.

[doktor5000]

I did not have this problem before.

Seems like you did have that exact same issue before, no ? viewtopic.php?f=8&t=12889

What about mounting it in debug mode, or with -o allow_other ?
Also, the linked github page contains a section about troubleshooting, what from there did you try out already?
https://github.com/astrada/google-drive ... leshooting

Apart from that, I just tried this out in a new Mageia 7 VM, and cannot reproduce your issue.
All the existing files below the google drive mountpoint belong to my user, and I can also copy/move files there and don't get any issues.

Maybe the issue is, that you kept your /home partition when you reinstalled, as you mentioned in the other thread on tesseract, and also kept some of the old problems that came with some settings ?

[Erik]

Dear Doktor,

You are quite right! I had this problem before, but there was a time that google-drive-ocamlfuse worked well on Mageia too. I am afraid I shall have to live with these "senior moments" . Yesterday I got an update of google-drive-ocamlfuse on Linux Mint. This made me look for the date of the latest patch of Mageia's version. It is: may 11 2019. Since then we had several patches of Mageia's kernel. So it is now my hypothesis that the program needs a patch to work fully again with the newest patched kernel. This may very well be the reason that Mageia's verson does not work well, so that I do not have to look for a solution on my computer.

Following your advice I made a new user on my computer and tried working with the google drive. The problems are exactly the same, so that the cause is not some inherited setting from the past.

Regretfully, my "solution" for the time being will be to use Linux Mint whenever I need to work with google drive, until a patch comes from mageia.

Thank you for the help and patience with the problems of us simple users.

Greetiongs,

Erik Jan.

[doktor5000]

So it is now my hypothesis that the program needs a patch to work fully again with the newest patched kernel.

Well, it works fine here on a fresh setup. If the problem is not easily reproducable, then who should create that patch and what should it contain, in your opinion ?

Or asked the other way around - if nobody else has the problem that you describe here, and your stance is "I do not have to look for a solution on my computer" then this problem will most likely stay exactly as it is.

[Erik]

You are right, Doktor. I shall try again.

Thanks.

Erik Jan

[Erik]

Dear Doktor,

I made a fresh new installation of Mageia 7 on an external hard drive connected to a laptop instead of my desktop, updated it and installed google-drive-ocamlfuse. I moved a file from the google drive to my home directory and after this tried to put it back again. The result is stil the same as on my desktop, although the reported error is now different. The system tells me that it could not finish copying the file; it could not rename the temporary file. Thus the process ended with a file with the correct name but with zero length, and a hidden file that I discovered in Firefox after having opened my google drive this way. I made the hidden files visible in Dophin and saw it on my computer too. The length was not correct, and I could not open it. I do not know what else to do to make the connection to the google drive work. Are you sure that an installation on a virtaul machine works exactly the same as a real installation??

Greetings,

Erik.

[doktor5000]

You just mentioned that you cannot even reproduce the initial issue yourself.
And depending on how long you waited after you moved the file to your google drive, it might not have synced completely so it could not be removed on your google drive because it was not fully written there.

And yes, an installation in a virtual machine works the same as a real installation for this purpose - because it is just that - a real installation in a different host.

Apart from that, I've already provided some pointers on the documentation regarding troubleshooting / debugging, it's up to you whether, you're interested to find out why it doesn't work for you or not.

[Erik]

Dear Doktor,

the result of my trying to debug is:

[erikjan@localhost ~]$ google-drive-ocamlfuse -debug ~/GoogleDrive
Starting application setup (label=default, base_dir=).
[0.000405] TID=0: Loading configuration from /home/erikjan/.gdfuse/default/config...done
Opening log file: /home/erikjan/.gdfuse/default/gdfuse.log
Segmentatiefout (geheugendump gemaakt)
[erikjan@localhost ~]$

So the file "curl.log" is very short:

[0.025533] curl: info: Trying 172.217.168.202:443...
[0.025606] curl: info: TCP_NODELAY set
[0.038344] curl: info: Connected to www.googleapis.com (172.217.168.202) port 443 (#0)
[0.039508] curl: info: ALPN, offering h2
[0.039527] curl: info: ALPN, offering http/1.1
[0.051458] curl: info: successfully set certificate verify locations:
[0.051491] curl: info: CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none

I did the same in Linux Mint. There the log files grow very fast, becoming several MegaBytes long in a short time.

All my three Mageia installations show the same error: a segmentation fault, caused by

google-drive-ocamlfuse -debug ~/GoogleDrive

Another result was, that after this fault I could no longer open /home/erikjan/ in Dolphin, and ~/.gdfuse/cache contained a lot of zero-length files that were perfectly in order just before. I also found that after trying to move a file to GoogleDrive several files in cache had become zero-length.

I have been using Mandrake/Mandriva/Mageia for sixteen years now and maintain several Mageia computers for friends, but I still can only maintain a working installation. With problems like segmentation faults I am helpless, I am sorry to say.

Greetings and many thanks for all the help that enables us end-users to maintan our computers and stay away from Windows and its commercial maintainers.

Erik Jan

[doktor5000]

There are a few issues upstream that also mention segmentation faults, like you got:
https://github.com/astrada/google-drive ... /issues/54
https://github.com/astrada/google-drive ... /issues/71
https://github.com/astrada/google-drive ... issues/543

You could try to change curl_debug_off=false to curl_debug_off=true in ~/.gdfuse/default/config and try the debug again, that works fine here.
Afterwards ~/.gdfuse/default/gdfuse.log should contain some more information, then you would need to check for the file transactions that you described initially.

Also, it's recommended to change the ulimits as mentioned, before you start google-drive-ocamlfuse

Code: Select all

ulimit -c unlimited

Also, was your google drive mounted before you tried the debug run ?

[Erik]

Dear Doktor,

I read all your referemces, ans some more. Very illuminating. I know now that it is useless to try and get google-drive-ocamlfuse working in Mageia 7. I shall have to work with Google Drive via firefox.

Greetings and thank you for your help.

Erik Jan

[doktor5000]

I know now that it is useless to try and get google-drive-ocamlfuse working in Mageia 7.

And how do you know that? Must be something specific to your setup, as it is working just fine here on Mageia 7.

[Erik]

Dear Doktor,
good question!

I have three installation of Mageia 7, two on desktop computers and one on a laptop. The one with the older home directory cannot connect to google drive, perhaps because of some old setting in the home directory, I don't know. The two others are new instalations, with new home directories and the default desktop settings, one on a desktop computer (XFCE) and the other on a laptop (Plasma). With none of them I can put a file on the google drive via google-drive-ocamlfuse. The only thing I did not try, is an installation in a virtual machine. I am not at all technical; the only thing I can do is to try and avoid changing the default settings that are supposed to work; which I did.

When I try to move a file into GoogleDrive in Dolphin, I get the error I mentioned, many files disappear from the cache, and I must log out and sometimes after some more trials restart the computer to get back to normal again. After this I find a zero-length file in GoogleDrive with the name of the one I wanted to put there.

You do not know what is wrong, nor are you able find any suggestion on the internet. If you cannot, how could I?

There is nothing left for me but to give up.

Thanks and greetings

Erik Jan

[doktor5000]

You do not know what is wrong, nor are you able find any suggestion on the internet. If you cannot, how could I?

Huh? I gave you instructions on how to enable debugging and check the logs on what is happening on your installation, and your response was that it's useless to try and to give up.

[isadora]

Dear Doktor,

I am sorry I did not express myself well. I looked at the debug file; on one computer it is huge (1,6MB), and and on the other it is very small:

[0.000440] TID=0: Setting up default filesystem...
[0.000465] TID=0: BEGIN: Saving configuration in /home/erikjan/.gdfuse/default/config
[0.000579] TID=0: END: Saving configuration in /home/erikjan/.gdfuse/default/config
[0.000606] TID=0: Loading application state from /home/erikjan/.gdfuse/default/state...done
Current version: 0.7.2
Setting up cache db...done
Setting up CURL...done
[0.003564] TID=0: Starting flush DB thread (TID=1, interval=30s)
Refresh token already present.
[0.003608] TID=0: Starting filesystem /home/erikjan/GoogleDrive
[0.008286] TID=2: init_filesystem
[0.008325] TID=2: BEGIN: Getting root folder id (team drive id=, root folder=) from server
[0.008354] TID=2: BEGIN: Getting root resource from server

On the other computer I get:

.........
.........
[39.847807] TID=862: BEGIN: Getting metadata from context
[39.847823] TID=862: END: Getting metadata: Valid
[39.881928] TID=863: getattr /backupmaken.txt
[39.882011] TID=863: BEGIN: Getting metadata from context
[39.882026] TID=863: END: Getting metadata: Valid
[39.882041] TID=863: BEGIN: Loading resource /backupmaken.txt (trashed=false) from db
[39.882129] TID=863: END: Loading resource /backupmaken.txt (trashed=false) from db: Not found
[39.882148] TID=863: BEGIN: Loading resource / (trashed=false) from db
[39.882168] TID=863: END: Loading resource / (trashed=false) from db: Found (id=1, state=Synchronized)
[39.882254] TID=863: File not found: stat /backupmaken.txt
[39.882614] TID=864: getattr /backupmaken.txt
[39.882661] TID=864: BEGIN: Getting metadata from context
[39.882675] TID=864: END: Getting metadata: Valid
[39.882689] TID=864: BEGIN: Loading resource /backupmaken.txt (trashed=false) from db
[39.882765] TID=864: END: Loading resource /backupmaken.txt (trashed=false) from db: Not found
[39.882781] TID=864: BEGIN: Loading resource / (trashed=false) from db
[39.882799] TID=864: END: Loading resource / (trashed=false) from db: Found (id=1, state=Synchronized)
[39.882851] TID=864: File not found: stat /backupmaken.txt
[39.883169] TID=866: mknod /backupmaken.txt 100664
[39.883258] TID=866: BEGIN: Getting metadata from context
[39.883297] TID=866: END: Getting metadata: Valid
[39.883311] TID=866: BEGIN: Loading resource / (trashed=false) from db
[39.883341] TID=866: END: Loading resource / (trashed=false) from db: Found (id=1, state=Synchronized)
[39.883387] TID=866: BEGIN: Creating file (path=/backupmaken.txt, trashed=false) on server
[39.946212] TID=867: getxattr / system.posix_acl_access
[39.946287] TID=867: BEGIN: Getting metadata from context
[39.946303] TID=867: END: Getting metadata: Valid
............
............
[202.096077] TID=3972: BEGIN: Getting metadata from context
[202.096088] TID=3972: END: Getting metadata: Valid
[202.096098] TID=3972: BEGIN: Loading resource /backupmaken.txt (trashed=false) from db
[202.096127] TID=3972: END: Loading resource /backupmaken.txt (trashed=false) from db: Found (id=281, state=Synchronized)
[202.099436] TID=3973: fopen /backupmaken.txt O_RDONLY
[202.099495] TID=3973: BEGIN: Getting metadata from context
[202.099506] TID=3973: END: Getting metadata: Valid
[202.099517] TID=3973: BEGIN: Loading resource /backupmaken.txt (trashed=false) from db
[202.099557] TID=3973: END: Loading resource /backupmaken.txt (trashed=false) from db: Found (id=281, state=Synchronized)
[202.099809] TID=3974: read /backupmaken.txt [4096 bytes] 0 0
[202.099835] TID=3974: BEGIN: Getting metadata from context
[202.099846] TID=3974: END: Getting metadata: Valid
[202.099856] TID=3974: BEGIN: Loading resource /backupmaken.txt (trashed=false) from db
[202.099879] TID=3974: END: Loading resource /backupmaken.txt (trashed=false) from db: Found (id=281, state=Synchronized)
[202.099892] TID=3974: BEGIN: Getting metadata from context
[202.099901] TID=3974: END: Getting metadata: Valid
[202.099910] TID=3974: BEGIN: Loading resource /backupmaken.txt (trashed=false) from db
[202.099928] TID=3974: END: Loading resource /backupmaken.txt (trashed=false) from db: Found (id=281, state=Synchronized)
[202.100221] TID=3975: flush /backupmaken.txt 0
[202.100245] TID=3975: BEGIN: Loading resource /backupmaken.txt (trashed=false) from db
[202.100267] TID=3975: END: Loading resource /backupmaken.txt (trashed=false) from db: Found (id=281, state=Synchronized)
[202.100415] TID=3976: release /backupmaken.txt O_RDONLY
[202.100430] TID=3976: BEGIN: Loading resource /backupmaken.txt (trashed=false) from db
[202.100453] TID=3976: END: Loading resource /backupmaken.txt (trashed=false) from db: Found (id=281, state=Synchronized)
[207.894018] TID=3977: getattr /
[207.894097] TID=3977: BEGIN: Getting metadata from context
[207.894114] TID=3977: END: Getting metadata: Valid
[207.894130] TID=3977: BEGIN: Loading resource / (trashed=false) from db
[207.894164] TID=3977: END: Loading resource / (trashed=false) from db: Found (id=280, state=Synchronized)
[211.207270] TID=1: Flushing DB...done
[218.895186] TID=0: Exiting.
Waiting for pending upload threads (0)...done
Stopping flush DB thread (TID=1)...done
Flushing cache...
Storing clean shutdown flag...done
CURL cleanup...done
Clearing context...done

I finished the debugging with Ctrl-C in Konsole.

I could not find anything in it that can help me further. The program cannot find the file at the beginning, and it flushes it at the end...... ????
I read a bit about segmentation faults and the forum of Alessandro Strada. The problem is: it is all beyond me. I am sorry.

I know it is my own failure. I do appreciate your help.

Greetings.

Erik jan

[Erik]

@Isadora:

Dear Isadora,

I am sorry I undid your change. I only saw your remark after heving corrected my post. I thought it was my mistake to use the code tag instead of the quote tag. My eyesight nowadays is not what it was. I has become difficult for me to avoid mistakes at typing and reading errors.

Thank you for your help.

Greetings

Erik Jan