In the logging is an error complaining rclone can not delete a file that is not present on the remote. But the file is also no longer present on the local system. So why does rclone think this file exists? The file used to exist in the past but I manually delete it on the remote (as a test)
What is your rclone version (output from rclone version)
rclone v1.52.1
os/arch: linux/amd64
go version: go1.14.4
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Which cloud storage system are you using? (eg Google Drive)
BackBlaze B2
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone: Version "v1.52.1" starting with parameters ["rclone" "-vv" "sync" "/" "Backblaze-inzicht-Crypt:/" "--filter-from" "/usr/local/share/rclone/rclone_backup.filter" "--log-file=/var/log/rclone/rclone_backup.sh-donderdag.log" "--fast-list" "--skip-links" "--delete-excluded" "--ignore-errors"]
The rclone config contents with secrets removed.
[Backblaze]
type = b2
account =
key =
endpoint =
[Backblaze-inzicht-Crypt]
type = crypt
remote = Backblaze:inzicht
filename_encryption = off
password =
password2 =
A log from the command with the -vv flag
2020/07/02 03:18:35 ERROR : etc/systemd/system/snap-signal\x2ddesktop-308.mount: Couldn't delete: failed to hide "etc/systemd/system/snap-signal\\x2ddesktop-308.mount.bin": File not present: etc/systemd/system/snap-signal＼x2ddesktop-308.mount.bin (400 no_such_file)
root@inzicht:/var/log/rclone# ls -la /etc/systemd/system/snap-pycharm*
-rw-r--r-- 1 root root 279 mei 7 10:20 '/etc/systemd/system/snap-pycharm\x2dcommunity-194.mount'
-rw-r--r-- 1 root root 279 jun 3 20:14 '/etc/systemd/system/snap-pycharm\x2dcommunity-197.mount'
-rw-r--r-- 1 root root 288 mei 7 13:46 '/etc/systemd/system/snap-pycharm\x2dprofessional-198.mount'
-rw-r--r-- 1 root root 288 jun 3 20:15 '/etc/systemd/system/snap-pycharm\x2dprofessional-201.mount'
It has been like this for at least the last week. I have no idea how rclone thinks that he should backup a non-existing directory. there are no stale mounts as far as I can see.
This is rclone in the delete phase of the sync. What it is saying is that it tried to delete etc/systemd/system/snap-pycharm\x2dcommunity-188.mount which isn't there any more on the source but is on the destination, but it received this error from b2: File not present: etc/systemd/system/snap-pycharm＼x2dcommunity-188.mount.bin (400 no_such_file)
I note that you are using crypt but with filename_encryption = off - I wonder if this is part of the problem. You can't write \ to b2 file names so rclone translates them transparently between that and a similar unicode character ＼.
Did all the failures have ＼ in them?
If you try to find that directory on the b2 web interface what does it look like?
Can you try rclone lsf on etc/systemd/system/ for the crypted b2 and the normal b2?
Let's see if I can delete the file manually from the command line:
So the file is present remote, but I can't seem to find a way to select just this single file. I can do lsf for the directory, but not for that specific file:
# rclone ls "Backblaze-inzicht-Crypt:etc/systemd/system/snap-pycharm/community-188.mount.bin"
# rclone ls "Backblaze-inzicht-Crypt:etc/systemd/system/snap-pycharm\x2dcommunity-188.mount.b in"
# rclone ls Backblaze-inzicht-Crypt:etc/systemd/system/snap-pycharm\x2dcommunity-188.mount.bin
So, rclone can save a file containing a slash in the filename but it can not address it anymore. is this a bug?
By the way, thanks so much for thinking with me on this one.
Best, Jeroen
Sorry that should be --b2-encoding (two dashes at the start)
I think what happened is that this file was uploaded with a pre encoding B2 backend - that explains the problem and you rclone versions match that hypothesis.
I think adding the encoding should work.
I now need to decide whether to change the default encoding.
If I do it potentially means people's syncs will upload stuff with back slashes again which is annoying but not the end of the world. If I don't then your problem will happen and rclone will be incompatible with other B2 tools.
So, with this last cli I can 'grab' and probably delete the file.
As my problem only pertains to a small number of files it is no hassle to manually delete them. Larger numbers can be done by scripting.
I would advice against changing the default encoding. Maybe some people need to check or fix their remote contents, but I think it is way better than introducing a change that could effect everybody.
But, of course, I am only a humble rclone user and no backup expert and these are just my 2 cents.
I will no go ahead and try to remove the files manually.
