Certain files fail to copy via rclone mount regardless of the mount settings but work fine with 'rclone copy' command. most files work but some, seemingly larger ones fail repeatedly. Have tried different filenames etc
Run the command 'rclone version' and share the full output of the command.
rclone version
rclone v1.65.1
os/version: debian 11.6 (64 bit)
os/kernel: 6.2.16-8-pve (x86_64)
os/type: linux
os/arch: amd64
go/version: go1.21.5
go/linking: static
go/tags: none
Which cloud storage system are you using? (eg Google Drive)
iDrive e2
The command you were trying to run (eg rclone copy /tmp remote:tmp)
You should not be using base32768 encoding with iDrive.
$ rclone test info --check-length --check-base32768 iDrive:test
// iDrive
maxFileLength = 255 // for 1 byte unicode characters
maxFileLength = 127 // for 2 byte unicode characters
maxFileLength = 85 // for 3 byte unicode characters
maxFileLength = 63 // for 4 byte unicode characters
base32768isOK = true // make sure maxFileLength for 2 byte unicode chars is the same as for 1 byte characters
by using base32768 you are using 2 byte unicode characters which shorten your max file name length which I guess was not your intent.
For any S3 remote the most appropriate is base64
In terms of upload failures,
this is your mount command:
2024/01/19 11:49:03 DEBUG : rclone: Version "v1.65.1" starting with parameters ["/usr/bin/rclone" "mount" "--config=/root/.config/rclone/rclone.conf" "--log-file=/tmp/idrive_test.log" "--log-level" "DEBUG" "--dir-cache-time" "1m" "crypt-e2:" "/mnt/idrivetest"]
I suggest you add --vfs-cache-mode writes or even --vfs-cache-mode full with optional --vfs-cache-max-size to limit cache size used.
Default --vfs-cache-mode off most likely makes multi part uploads impossible (for large files). It would explain why rclone copy works and mount not.
How do I go about changing filename_encoding, I assume changing it now would render all the current files as useless?
Thanks for the tip on --vfs-cache-mode writes I did have this before and had the same issue so stripped it out but will retry. For vfs-cache-max-size is there a recommended size?
What you do is set up a new crypt remote by copying the old one in the config file, renaming it and adding filename_encoding = base64. Choosing a different destination directory is a good idea here too so the old and the new don't overlap.
root@dl-vm:~# tail -n 100000 /tmp/idrive.log | grep ERROR
2024/01/19 13:11:27 ERROR : Media/TV/TV 4K/Tom Clancy's Jack Ryan/Season 4/Tom.Clancys.Jack.Ryan.(2018).S04E05.(2160p.AMZN.WEB-DL.H265.DV.DDP.Atmos.5.1.English.-.HONE).mkv: Failed to copy: failed to upload chunk 1 with 16777216 bytes: NoSuchUpload: The specified multipart upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed.
2024/01/19 13:11:27 ERROR : Media/TV/TV 4K/Tom Clancy's Jack Ryan/Season 4/Tom.Clancys.Jack.Ryan.(2018).S04E05.(2160p.AMZN.WEB-DL.H265.DV.DDP.Atmos.5.1.English.-.HONE).mkv: vfs cache: failed to upload try #1, will retry in 10s: vfs cache: failed to transfer file from cache to remote: failed to upload chunk 1 with 16777216 bytes: NoSuchUpload: The specified multipart upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed.
2024/01/19 13:11:33 ERROR : Media/TV/TV 4K/Tom Clancy's Jack Ryan/Season 4/Tom.Clancys.Jack.Ryan.(2018).S04E04.(2160p.AMZN.WEB-DL.H265.DV.DDP.Atmos.5.1.English.-.HONE).mkv: Failed to copy: failed to upload chunk 1 with 16777216 bytes: NoSuchUpload: The specified multipart upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed.
2024/01/19 13:11:33 ERROR : Media/TV/TV 4K/Tom Clancy's Jack Ryan/Season 4/Tom.Clancys.Jack.Ryan.(2018).S04E04.(2160p.AMZN.WEB-DL.H265.DV.DDP.Atmos.5.1.English.-.HONE).mkv: vfs cache: failed to upload try #3, will retry in 40s: vfs cache: failed to transfer file from cache to remote: failed to upload chunk 1 with 16777216 bytes: NoSuchUpload: The specified multipart upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed.
2024/01/19 13:11:47 ERROR : Media/TV/TV 4K/Tom Clancy's Jack Ryan/Season 4/Tom.Clancys.Jack.Ryan.(2018).S04E03.(2160p.AMZN.WEB-DL.H265.DV.DDP.Atmos.5.1.English.-.HONE).mkv: Failed to copy: failed to upload chunk 1 with 16777216 bytes: NoSuchUpload: The specified multipart upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed.
2024/01/19 13:11:47 ERROR : Media/TV/TV 4K/Tom Clancy's Jack Ryan/Season 4/Tom.Clancys.Jack.Ryan.(2018).S04E03.(2160p.AMZN.WEB-DL.H265.DV.DDP.Atmos.5.1.English.-.HONE).mkv: vfs cache: failed to upload try #4, will retry in 1m20s: vfs cache: failed to transfer file from cache to remote: failed to upload chunk 1 with 16777216 bytes: NoSuchUpload: The specified multipart upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed.
So just tested with a new crypt with base64 and uploaded first time. Still can't figure out why rclone copy works, but I guess now I will have a crack at moving everything from base32768 to base64.
My own fault, I reused the crypt settings from my failed attempt to use box, should have worked out what was best for my specific provider.
crypt-e2 (base32768)
rclone copy - works
rclone mount and cp xx - doesn't work
crypt-e2-base64 (base64)
rclone copy - works
rclone mount and cp xx - works (at least for the 1 file I tested that was previously failing)
What confuses me is that if base32768 is the problem I would expect rclone copy to also fail as that is common across both the rclone copy and rclone mount procedures.
Admittedly I only tested copying the one file on crypt-e2-base64 and it worked, the real test will be how it behaves going forward. The move of files from base32768 to base64 is very slowly progressing.
Problem might be more nuance than simple name length. I am a bit puzzled by this issue (especially that rclone copy works). Let's see how things stand with base64 when you start using it.
The cool thing is I have unioned crypt-e2 and crypt-e2-base64 together in an rclone mount on my content server, so downtime for the copy should actually be minimal