Google Drive with service account and restricted scope

[ncw (Nick Craig-Wood)]

Yes, I guess I'll do that, though I wonder whether it'll improve correctness to replace the single move command with a sequence of commands like

rclone rc sync/copy
rclone rc vfs/refresh
rclone rc operations/delete

It probably won't make any difference since the things rclone move deletes are not in the mount anyway.

The current implementation is as I suspected, then. I note the word "yet" in there, though

I have a possible plan for rclone backends to use the VFS layer which would fix this. Just ideas at the moment though!

[1xe]

It probably won't make any difference since the things rclone move deletes are not in the mount anyway.

These things are not in the rclone mount, but they are in the mergerfs mount, in the "local" filesystem part. With the single move command, from the "local" filesystem part to the "remote" rclone part, they disappear from the mergerfs mount because they are available neither in the local filesystem part nor in the remote rclone part until a vfs/refresh command has been run.

With the copy, refresh, delete sequence of commands instead of move, files don't disappear from the mergerfs mount because they become available in the remote rclone part before they are deleted from the local filesystem part. In this way, the copy, refresh, delete sequence of commands looks more like an ordinary "mv" command between two local filesystems than does the single move command.

I have a possible plan for rclone backends to use the VFS layer which would fix this. Just ideas at the moment though!

I'll keep an eye out. Until then I seem to have found a workaround.

[ncw (Nick Craig-Wood)]

These things are not in the rclone mount, but they are in the mergerfs mount

Oh, I see - thanks for explaining.

I'll keep an eye out. Until then I seem to have found a workaround.

Grand!