Closed
Description
rclone copy -v --log-file=logfile.txt "F:" "remote:Windows Fat"
doesn't work at all, error makes no sense and for some reason rclone creates new folders inside it's own folder named Fat and Fat_
yet somehow
rclone copy -v --log-file=logfile.txt "F:\4" "remote:Windows Fat\4"
worked perfectly! but... ideally I'd like to backup this entire drive all at once and I have no idea why I can't
I very clumsily moved every single file from the F drive into a subfolder of F:\ called F and then the transfer copy command worked
I tried this in 1.27 and 1.29
oh in case it wasn't clear "Fat" is what I named the drive because it's in fat32 because I used it a long time ago. I'm not sure if that matters.
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
ncw commentedon Apr 30, 2016
After a quick look this does look like a bug. Rclone is treating "remote:Windows Fat" as a local directory rather than a remote. Will investigate further!
left1000 commentedon Apr 30, 2016
is it because I started with a root drive? or because of fat32? or windows keyword? either way it's baffling how simple the workaround is...
ncw commentedon Apr 30, 2016
I'm away from my computer at the moment - I'll check the source when I get back and all will become clear!
klauspost commentedon May 1, 2016
Use
F:\(no quotes).However, there is something weird in the args parsing.
"f:\"is not the same asf:\. Something is doing some escape-stuff. Windows explicitly claims not to do escape processing on\, so it may be some quirk with the flag parser.ncw commentedon May 2, 2016
I think you must have written this originally
In the pastebin the first line is
indicating that Windows thought rclone was being run with two arguments
F:\" remote:WindowsFatSo I think this is caused by oddities in the windows command line parser as Klaus suggested, so
Should fix it
This is caused ultimately by CommandLineToArgvW which states:
CommandLineToArgvW has a special interpretation of backslash characters when they are followed by a quotation mark character ("), as follows:
The original command line had a mis-matched quote
"so it would have been nice if it had given an error.[-]I'm sorry this is a basic question but what am I doing wrong here?[/-][+]Windows command line arguments - problems with " and \[/+]left1000 commentedon May 6, 2016
thanks guys, that answers that, sorry for such a silly question! I'll remember this for the future.
ncw commentedon May 6, 2016
@left1000 I don't think this is a silly question at all - it exposes a bit of windows oddness. I should probably put this either in the docs somewhere!
ncw commentedon May 6, 2016
I've made another issue to write some more docs on the windows shell here #473
I'll close this ticket now as I think we've got to the bottom of it.