`rclone copy t:\ --include=filename` does NOT work, but `rclone copy t:\filename` works

Help and Support
3

never. in fact, the source is write-protected, i cannot edit it, cannot delete it
image

well, the source dir is a vss snapshot ;wink

  • happens to many dozens, hundreds of files. easily reproduced.
    i tested this over a couple of days, different vss snapshots, different dirs, different rclone flags, etc..
  • not just me, happens to others fellow rcloners as posted about in the forum.
  • fastcopy, fc, fchash, 7zip, certutil, double commander, windows explorer, dos cmd, powershell, all, always copies the files and return the correct md5 hash.

this does NOT affect md5sum in the same way, i tested three ways and get correct md5 hash.

rclone md5sum t:\filename
rclone md5sum t:\ 
rclone md5sum t:\ --include=filename

so far, only issue, rclone copy, when the source is a dir
--include=filename has nothing to do with it. i did that to keep the log short.
so both of these will generate the same exact error(s).

rclone copy t:\
rclone copy t:\ --include=filename

i am no expert at the source code but i did notice that rclone copy behave differently, if the source is a dir or filename, maybe some plumbing with sync.CopyDir

https://github.com/rclone/rclone/blob/f56ea2bee2e7552e273ff679c6f0eb429a0969d3/cmd/copy/copy.go#L94

if srcFileName == "" {
		return sync.CopyDir(context.Background(), fdst, fsrc, createEmptySrcDirs)
	}
	return operations.CopyFile(context.Background(), fdst, fsrc, srcFileName, srcFileName)

or maybe this