GDriveFS icon indicating copy to clipboard operation
GDriveFS copied to clipboard

Write operations create 0 byte files

Open vondrt4 opened this issue 4 years ago • 3 comments

I've been using GDriveFS successfully in the past (1 year back, maybe). Now, I can read what I've written before, but creating or overwriting any file causes an error and leaves a 0 byte file behind. Any clue why? The log looks like this:

unique: 59, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 3537 statfs / unique: 59, success, outsize: 96 unique: 60, opcode: LOOKUP (1), nodeid: 1, insize: 55, pid: 3537 LOOKUP /crossover2.txt getattr /crossover2.txt unique: 60, error: -2 (No such file or directory), outsize: 16 unique: 61, opcode: LOOKUP (1), nodeid: 1, insize: 55, pid: 3537 LOOKUP /crossover2.txt getattr /crossover2.txt unique: 61, error: -2 (No such file or directory), outsize: 16 unique: 62, opcode: CREATE (35), nodeid: 1, insize: 71, pid: 3537 create flags: 0x80c1 /crossover2.txt 0100640 umask=0022 unique: 62, error: -5 (Input/output error), outsize: 16

vondrt4 avatar Sep 08 '20 08:09 vondrt4

Thanks for reporting. I'm unable to look at this until next week. Thanks for your patience.

dsoprea avatar Sep 09 '20 18:09 dsoprea

I am having this problem on MacOS Catalina. Any resolution yet?

lokeb avatar May 17 '21 06:05 lokeb

the same problem on openSUSE

Fak3 avatar Mar 14 '22 08:03 Fak3