You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
The text was updated successfully, but these errors were encountered: