I'm including this only to show the results when I "reclone copy" the same file:
2020/06/15 13:52:41 DEBUG : rclone: Version "v1.51.0" starting with parameters ["rclone.exe" "--config" "rclone.conf" "copy" "2019:2019\VIOL_IMAGES\LONG_TERM\201901\20190108\030707_\030707_201901081651090033258_0.jpg" "D:\SWIFTSTACK\TEST" "--log-level" "DEBUG" "--log-file" "cp.singlefile.txt"]
2020/06/15 13:52:41 DEBUG : Using config file from "C:\rclone\rclone.conf"
2020/06/15 13:52:41 DEBUG : 030707_201901081651090033258_0.jpg: Need to transfer - File not found at Destination
2020/06/15 13:52:41 DEBUG : 030707_201901081651090033258_0.jpg: MD5 = 499881b39327285147aead8acd432676 OK
2020/06/15 13:52:41 INFO : 030707_201901081651090033258_0.jpg: Copied (new)
2020/06/15 13:52:41 INFO :
Transferred: 2.791k / 2.791 kBytes, 100%, 65.477 kBytes/s, ETA 0s
Transferred: 1 / 1, 100%
Elapsed time: 0.0s
i also intentionally mis-keyed the file name and it immediately came back and said it could't find the file so I guess it is finding the file correctly.
I think I've figure out the issue. Even though the tool will take the backslashes from the command line, you have to convert to all forward slashes when you use the --file-from option. I have had success converting all of the slashes and getting it to run and use the --file-from file. I'm still dealing with it being extremely slow but will work through that trying the different parameters.
I wonder if @ncw or @calisro might be able to chime in ? I'm definitely not a Windows guy but I would think if you are on Windows, that should not be the case.
Maybe @asdffdsa could check also? You have me curious now!
I agree. The server that I'm running rclone from is Windows. The backend is SwiftStack on Linux. Converting to the forward slash did solve the issue but it's not working as fast I would have hoped. I have a rather large number of individual files (MM) that I need to download and was hoping this would be an efficient way of getting them. I actually do better by reading the file name from a text file in one script, and the calling another script to run the rclone copy, while the other is keeping track of the number of instances I've called that runs the rclone (i.e. imitating the --transfers 100 parm).
I don't want to diverge to the next issue on this thread but would welcome any suggestions.