forked from TrueCloudLab/rclone
b2: note that b2's encoding now allows \ but rclone's hasn't changed
See: https://forum.rclone.org/t/why-are-there-error-messages-about-non-existing-files-in-the-log/17608
This commit is contained in:
parent
f524a4c1cc
commit
80fe1f16db
1 changed files with 6 additions and 0 deletions
|
@ -117,6 +117,12 @@ the following characters are also replaced:
|
||||||
Invalid UTF-8 bytes will also be [replaced](/overview/#invalid-utf8),
|
Invalid UTF-8 bytes will also be [replaced](/overview/#invalid-utf8),
|
||||||
as they can't be used in JSON strings.
|
as they can't be used in JSON strings.
|
||||||
|
|
||||||
|
Note that in 2020-05 Backblaze started allowing \ characters in file
|
||||||
|
names. Rclone hasn't changed its encoding as this could cause syncs to
|
||||||
|
re-transfer files. If you want rclone not to replace \ then see the
|
||||||
|
`--b2-encoding` flag below and remove the `BackSlash` from the
|
||||||
|
string. This can be set in the config.
|
||||||
|
|
||||||
### SHA1 checksums ###
|
### SHA1 checksums ###
|
||||||
|
|
||||||
The SHA1 checksums of the files are checked on upload and download and
|
The SHA1 checksums of the files are checked on upload and download and
|
||||||
|
|
Loading…
Reference in a new issue