Moving file to chunker backend *sometimes* creates empty metadata file

Problem: Moving file to chunker backend sometimes creates empty metadata file.

RClone Version

rclone v1.65.0
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 5.15.0-91-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.21.4
- go/linking: static
- go/tags: none

RClone Backend: chunker

RClone Command

rclone move a.dir b.dir --progress

RClone Config

No Config Needed


Very very long log with no errors when moving approx. 500 huge files to chunker. Just 11 files had a 0 size metadata file. (Will try again with those specific files.)


For some files (I am not sure what makes them special), Rclone will generate a 0 size metadata file. This metadata file has proper naming but no contents.

Also, I dont know if this is a bug or it is intended to perform this way. I haven't found any way this vould be an hinderance to the way chunker works.

Expected Outcome:

RClone creates a non-zero sized (containing size, checksum, no. of chunks, etc.) metadata file for each file that is chunked through chunker backend.

@ncw Can you verify that this is a bug before I try to reproduce it.

Empty metadata files sounds like a bug to me.

Most likely caused if the destination got full - that would be my guess.