All the writes are done via the mount. Occasionally I have observed that the mount simply freezes for a particular directory or file. Doing anything in that directory also freezes, even a simple ls.
I have not been able to reproduce this with any consistency. Sometimes it happens immediately and sometimes after a few days. I have tried putting debug logs but since I can’t reproduce it manually, the logs are always rotated out by the time I notice this again.
Anything that looks wrong in the command or that may help in debugging this issue?
That means that the mount is stuck in the kernel. Specifically it means the kernel has asked rclone mount via FUSE to do something and rclone hasn’t responded yet.
Ok, I will enable debug logging and turn off any log rotation so they don’t get rotated out. Hopefully it appears sooner rather than later to avoid the rather large log file that will be the result otherwise.
I haven’t touched the --poll-interval flag in my config and have let it remain at the default 1m. What I have reduced the value for is the --vfs-cache-poll-interval. Is there any relation between these two parameters?
I don’t modify my drive other than through rclone, so do you think there would be any disadvantage in increasing it to a much higher value like 15m or even 30m to mostly avoid any chance of a deadlock, till the issue is fixed?
If you aren’t writing to your GDrive from another location, you could set it really high. For me, I’m all self contained on a single machine so that value could be set super high and I wouldn’t see an issue.