Box move file within the same remote without redownload

[Comica]

I have been using rlcone with box.com, where the structure is chunker -> crypt -> Box. So far, everything seems to be working fine. However, when attempting to move a single file that has multiple chunks from one directory to another directory within the same remote, the file is not moved but rather downloaded and re-uploaded, which takes a considerable amount of time. Is this the expected behavior? Is there a way to move the file without having to re-download and re-upload it?

Run the command 'rclone version' and share the full output of the command.

Which cloud storage system are you using? (eg Google Drive)

Box

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone moveto "BoxChunker:exp/The Big File/The Big File 4K.mkv"  "BoxChunker:exp"

The rclone config contents with secrets removed.

[Box]
type = box
token = xxxxxxxxxx

[BoxChunker]
type = chunker
remote = BoxCrypt:
chunk_size = 4.785Gi
hash_type = sha1quick
name_format = *.rclone.###

[BoxCrypt]
type = crypt
remote = Box:
password = xxxxxxxxx
password2 = xxxxxxxxx
filename_encoding = base32768

A log from the command with the -vv flag

2023/04/05 11:23:37 DEBUG : rclone: Version "v1.62.2" starting with parameters ["rclone" "moveto" "BoxChunker:exp/The Big File/The Big File 4K.mkv" "BoxChunker:exp" "-vv"]
2023/04/05 11:23:37 DEBUG : Creating backend with remote "BoxChunker:exp/The Big File/The Big File 4K.mkv"
2023/04/05 11:23:37 DEBUG : Using config file from "/root/.rclone.conf"
2023/04/05 11:23:37 DEBUG : Creating backend with remote "BoxCrypt:exp/The Big File/The Big File 4K.mkv"
2023/04/05 11:23:37 DEBUG : Creating backend with remote "Box:㷠玒鎛媝鄳鋙⪊告仟/埒复窈ꈎ墦肬啖␆䈿/暪砼躥踧曧晨兦䳠找鴛酷門犧俊⡈ᡟ饁ɟ"
2023/04/05 11:23:39 DEBUG : fs cache: adding new entry for parent of "Box:㷠玒鎛媝鄳鋙⪊告仟/埒复窈ꈎ墦肬啖␆䈿/暪砼躥踧曧晨兦䳠找鴛酷門犧俊⡈ᡟ饁ɟ", "Box:㷠玒鎛媝鄳鋙⪊告仟/埒复窈ꈎ墦肬啖␆䈿"
2023/04/05 11:23:39 DEBUG : Reset feature "ListR"
2023/04/05 11:23:39 DEBUG : Creating backend with remote "BoxChunker:"
2023/04/05 11:23:39 DEBUG : Creating backend with remote "BoxCrypt:"
2023/04/05 11:23:39 DEBUG : Creating backend with remote "Box:"
2023/04/05 11:23:39 DEBUG : Reset feature "ListR"
2023/04/05 11:23:40 DEBUG : The Big File 4K.mkv: Need to transfer - File not found at Destination
2023/04/05 11:23:41 DEBUG : The Big File 4K.mkv: Can't move - required hash not found
2023/04/05 11:23:41 DEBUG : The Big File 4K.mkv: Can't move, switching to copy
2023/04/05 11:23:41 DEBUG : The Big File 4K.mkv: Can't copy - required hash not found
2023/04/05 11:23:43 DEBUG : ᰅ膱佉䅺㡸渀圏肫剓㨍鸵謫掍ᔩ鼆醘罣ʟ: Multipart upload session started for 77 parts of size 64Mi
2023/04/05 11:23:47 DEBUG : ᰅ膱佉䅺㡸渀圏肫剓㨍鸵謫掍ᔩ鼆醘罣ʟ: Uploading part 1/77 offset 0/4.786Gi part size 64Mi
2023/04/05 11:23:52 DEBUG : ᰅ膱佉䅺㡸渀圏肫剓㨍鸵謫掍ᔩ鼆醘罣ʟ: Uploading part 2/77 offset 64Mi/4.786Gi part size 64Mi
2023/04/05 11:23:58 DEBUG : ᰅ膱佉䅺㡸渀圏肫剓㨍鸵謫掍ᔩ鼆醘罣ʟ: Uploading part 3/77 offset 128Mi/4.786Gi part size 64Mi
2023/04/05 11:24:03 DEBUG : ᰅ膱佉䅺㡸渀圏肫剓㨍鸵謫掍ᔩ鼆醘罣ʟ: Uploading part 4/77 offset 192Mi/4.786Gi part size 64Mi
2023/04/05 11:24:07 DEBUG : ᰅ膱佉䅺㡸渀圏肫剓㨍鸵謫掍ᔩ鼆醘罣ʟ: Uploading part 5/77 offset 256Mi/4.786Gi part size 64Mi

[ncw (Nick Craig-Wood)]

It's complaining about hashes...

This would probably work if you swapped the order from chunker -> crypt -> Box to crypt -> chunker -> Box and use the MD5/md5quick hash type.

I'm not sure why its complaining about hashes though - let me check the source...

If you set hash_type = none in the chunker then it should work according to the source.

I still don't really understand why the code is like that though!

It is documented here: Chunker

Also, chunker will reject a server-side copy or move operation if source and destination hashsum types are different resulting in the extra network bandwidth, too.