New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dropbox and Box move not working if destination file exists #2569
Comments
As a side note/question. I am confused why it keeps looking for ".git" and "HEAD". In the test directory there is no git stuff. |
However mv in a mount doesn't
Gives
The solution to this (and partially #1965) is to get VFS layer to use the operations.Move primitive rather than calling the Fs |
@brechmos wrote:
That is likely your shell - do you have a prompt which shows special things when you are in a git repo? |
@B4dM4n do you think using |
D'oh, you are right. Sorry for the noise. |
I don't think We could hide |
Excellent idea - thanks! I'll have a go at that. |
See also forum thread which I think is the same issue but on drive a duplicate is created. |
Before this change remotes without server side Move (eg swift, s3, gcs) would not be able to rename files. After it means nearly all remotes will be able to rename files on rclone mount with the notable exceptions of b2 and yandex. This changes checks to see if the remote can do Move or Copy then calls `operations.Move` to do the actual move. This will do a server side Move or Copy but won't download and re-upload the file. It also checks to see if the destination exists first which avoids conflicts or duplicates. Fixes #1965 Fixes #2569
I have attempted to fix this here https://beta.rclone.org/branch/v1.43-096-ga9fc86f5-fix-2569-mount-move-beta/ (uploaded in 15-30 mins) Feedback welcome :-) |
@ncw I grabbed the branch in github and rebuilt. I tested both Dropbox and Box. In both I can do the I also tried it with a cached mount of Dropbox and Box and they both seem to work. Mega still works. In this simple testing, it looks good! If you have any ideas of edge cases you want me to try, I am happy to do that. Thanks for working on this!! |
@brechmos Great - thanks for testing. I can't think of anything else at the moment! I'll leave this open for the moment for feedback from the other issue that this fixes. |
I've merged this fix to master now, it will be in the latest beta in 15-30 mins an in v1.44. |
What is the problem you are having with rclone?
I am trying to move a file on top of another one and I am getting input/output errors.
What is your rclone version (eg output from
rclone -V
)Which OS you are using and how many bits (eg Windows 7, 64 bit)
ODROID Arm :)
Which cloud storage system are you using? (eg Google Drive)
Box and Dropbox are the ones not working (see below for others that are).
The command you were trying to run (eg
rclone copy /tmp remote:tmp
)A log from the command with the
-vv
flag (eg output fromrclone -vv copy /tmp remote:tmp
)This is the mounting:
The error above came when I did:
I am quite new at rclone, so there might be some helpful other flags but with the reasonably bare mount command I am seeing an error.
Oh... so, interesting. I just did the same thing with Mega and it worked:
It also works with pCloud:
It also worked with Google Drive.
Tried Box and it did not work.
Huh, so it seems to be only Box and Dropbox (of the ones I tested) that are giving me issues.
All of the above is based on:
If you want me to test a PR, I am happy to do it.
Detailed log:
The text was updated successfully, but these errors were encountered: