Correct, we have a separate mount for each project client and its files and combine them. Each mount is encrypted. However, the encryptions on all the mounts are identical to each other. It just saves me from having to start multiple mounts or work via rc.
The problem occurs with an "mv" which affects the combined mount. I can't provide a debug log right now, because it would endanger the production operation to restart the mount.
Thanks, I used to need it. Legacy in the meantime.
"use-nmap" was not known to me, is also not in the official documentation of the mount (rclone mount)
Then I misunderstood the documentation at that point. Thanks for the hint!
There can be a lot of small files, but there can also be a lot of big ones. I had to find a good balance so that it works in both cases. So far also no problems.
Correctly guessed, legacy from Google Drive times. Were with the company previously at Google Workspace. Is probably not necessary, but also does not hurt anyone.
However, the configuration has nothing to do with the actual problem (just the moving of files does not work on a combined mount). I think I have already found the cause... and that is the use of Combine and the moving of files beyond a mount, which is merged via Combine. I think this is an edge case that is not currently provided for in rclone.
It doesn't matter if I copy a folder or a single file, the error always occurs when it affects another remote that was merged via Combine. Files can be moved within a remote. I have just tested this again for safety.
My guess: The respective remote is isolated for itself and cannot access the other one and therefore cannot move the files. So I would probably have to change the scope to solve the problem. That would at least explain the Dropbox Error... or do you have another idea? At the end you could also make it a copy in the background when moving files if it goes beyond a remote. Or?
We have the identical problem with Google drive, and I've avoided putting a commit in like that because it gives a permission denied error and I wasn't confident we could tell it apart from any other. But I realised just now that we can tell if we are doing a cross remote transfer and only engage the fallback then. @Animosity022 should I add that to the google drive backend too do you think?
If we are doing a cross remote transfer then attempting a
Move/Copy/DirMove where we don't have permission gives
This patch notices that error and only if we are doing a cross remote
transfer it engages the fallback where the file is streamed.
Now I had time to test (v1.61.0-beta.6567.4660f5f15.fix-dropbox-cross-account-move) the whole thing. I created a file and moved it before uploading. The upload was canceled, the file was moved by "mv" and also uploaded at the new location. But at the old place the file remained.
2022/11/18 10:42:47 ERROR : Folder1/test.txt: Failed to copy: context canceled
2022/11/18 10:42:47 INFO : Folder1/test.txt: vfs cache: upload canceled
2022/11/18 10:42:47 INFO : Folder1/test.txt: vfs cache: renamed in cache to "Folder2/test.txt"
2022/11/18 10:42:58 INFO : vfs cache: cleaned: objects 1 (was 1) in use 1, to upload 1, uploading 0, total size 7 (was 7)
2022/11/18 10:43:22 INFO : Folder2/test.txt: Copied (new)
2022/11/18 10:43:22 INFO : Folder2/test.txt: vfs cache: upload succeeded try #2
2022/11/18 10:43:58 INFO : Folder2/test.txt: vfs cache: removed cache file as Removing old cache file not in use
2022/11/18 10:43:58 INFO : vfs cache RemoveNotInUse (maxAge=60000000000, emptyOnly=false): item Folder2/test.txt was removed, freed 7 bytes
2022/11/18 10:43:58 INFO : vfs cache: cleaned: objects 0 (was 1) in use 0, to upload 0, uploading 0, total size 0 (was 7)
2022/11/18 10:44:58 INFO : vfs cache: cleaned: objects 1 (was 1) in use 0, to upload 0, uploading 0, total size 0 (was 0)
Edit: I just did a test with a file that is already uploaded, it works. It seems only with not uploaded files to the fact that this then remains and is not deleted.
2022/11/18 10:47:34 INFO : Folder2/test.txt: Copied (new) to: Folder1/test.txt
2022/11/18 10:47:34 INFO : Folder2/test.txt: Deleted
2022/11/18 10:47:58 INFO : vfs cache: cleaned: objects 1 (was 1) in use 0, to upload 0, uploading 0, total size 0 (was 0)
Single files are probably not a problem but whole folders probably cause a problem.