rsync files-from unable to handle filename with subfolder?

Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I need to sync remotes files to local with the following command:
rsync -schavzP --stats --files-from=./filelist.txt -e "ssh -p 22" remoteuser@1.2.3.4:/home/somewhere/ .
While filelist.txt contains several subfolder filenames:
subfolder/746fbd52ec4441b88f62ead5beb8e57e
subfolder/test
The command gives the following error:
rsync: link_stat "/home/somewhere/subfolder/746fbd52ec4441b88f62ead5beb8e57e" failed: No such file or directory
If I issue rsync without files-from, and give the remote filename directly in command line, it works.
Appreciate if someone could lend me a hand. Thank you.
rsync
add a comment |Â
up vote
0
down vote
favorite
I need to sync remotes files to local with the following command:
rsync -schavzP --stats --files-from=./filelist.txt -e "ssh -p 22" remoteuser@1.2.3.4:/home/somewhere/ .
While filelist.txt contains several subfolder filenames:
subfolder/746fbd52ec4441b88f62ead5beb8e57e
subfolder/test
The command gives the following error:
rsync: link_stat "/home/somewhere/subfolder/746fbd52ec4441b88f62ead5beb8e57e" failed: No such file or directory
If I issue rsync without files-from, and give the remote filename directly in command line, it works.
Appreciate if someone could lend me a hand. Thank you.
rsync
2
You did verify that the file does exist?
â RalfFriedl
Aug 28 at 16:40
Yes definitely. I can rsync the file by command line
â Kenny Tse
Aug 29 at 1:47
Show the output fromls -l /home/somewhere/subfolder/746fbd52ec4441b88f62ead5beb8e57e, copy the path exactly from the error message rsync gives. Run `strace -f -e file rsync ..." and show the line that refers to this file. Append the information to the question, not as a comment.
â RalfFriedl
Aug 29 at 5:22
@RalfFriedl It lists the file is there. Nothing special. Thank you for your input. I found the real cause finally.
â Kenny Tse
Aug 29 at 7:21
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I need to sync remotes files to local with the following command:
rsync -schavzP --stats --files-from=./filelist.txt -e "ssh -p 22" remoteuser@1.2.3.4:/home/somewhere/ .
While filelist.txt contains several subfolder filenames:
subfolder/746fbd52ec4441b88f62ead5beb8e57e
subfolder/test
The command gives the following error:
rsync: link_stat "/home/somewhere/subfolder/746fbd52ec4441b88f62ead5beb8e57e" failed: No such file or directory
If I issue rsync without files-from, and give the remote filename directly in command line, it works.
Appreciate if someone could lend me a hand. Thank you.
rsync
I need to sync remotes files to local with the following command:
rsync -schavzP --stats --files-from=./filelist.txt -e "ssh -p 22" remoteuser@1.2.3.4:/home/somewhere/ .
While filelist.txt contains several subfolder filenames:
subfolder/746fbd52ec4441b88f62ead5beb8e57e
subfolder/test
The command gives the following error:
rsync: link_stat "/home/somewhere/subfolder/746fbd52ec4441b88f62ead5beb8e57e" failed: No such file or directory
If I issue rsync without files-from, and give the remote filename directly in command line, it works.
Appreciate if someone could lend me a hand. Thank you.
rsync
rsync
edited Aug 28 at 16:42
asked Aug 28 at 15:22
Kenny Tse
112
112
2
You did verify that the file does exist?
â RalfFriedl
Aug 28 at 16:40
Yes definitely. I can rsync the file by command line
â Kenny Tse
Aug 29 at 1:47
Show the output fromls -l /home/somewhere/subfolder/746fbd52ec4441b88f62ead5beb8e57e, copy the path exactly from the error message rsync gives. Run `strace -f -e file rsync ..." and show the line that refers to this file. Append the information to the question, not as a comment.
â RalfFriedl
Aug 29 at 5:22
@RalfFriedl It lists the file is there. Nothing special. Thank you for your input. I found the real cause finally.
â Kenny Tse
Aug 29 at 7:21
add a comment |Â
2
You did verify that the file does exist?
â RalfFriedl
Aug 28 at 16:40
Yes definitely. I can rsync the file by command line
â Kenny Tse
Aug 29 at 1:47
Show the output fromls -l /home/somewhere/subfolder/746fbd52ec4441b88f62ead5beb8e57e, copy the path exactly from the error message rsync gives. Run `strace -f -e file rsync ..." and show the line that refers to this file. Append the information to the question, not as a comment.
â RalfFriedl
Aug 29 at 5:22
@RalfFriedl It lists the file is there. Nothing special. Thank you for your input. I found the real cause finally.
â Kenny Tse
Aug 29 at 7:21
2
2
You did verify that the file does exist?
â RalfFriedl
Aug 28 at 16:40
You did verify that the file does exist?
â RalfFriedl
Aug 28 at 16:40
Yes definitely. I can rsync the file by command line
â Kenny Tse
Aug 29 at 1:47
Yes definitely. I can rsync the file by command line
â Kenny Tse
Aug 29 at 1:47
Show the output from
ls -l /home/somewhere/subfolder/746fbd52ec4441b88f62ead5beb8e57e, copy the path exactly from the error message rsync gives. Run `strace -f -e file rsync ..." and show the line that refers to this file. Append the information to the question, not as a comment.â RalfFriedl
Aug 29 at 5:22
Show the output from
ls -l /home/somewhere/subfolder/746fbd52ec4441b88f62ead5beb8e57e, copy the path exactly from the error message rsync gives. Run `strace -f -e file rsync ..." and show the line that refers to this file. Append the information to the question, not as a comment.â RalfFriedl
Aug 29 at 5:22
@RalfFriedl It lists the file is there. Nothing special. Thank you for your input. I found the real cause finally.
â Kenny Tse
Aug 29 at 7:21
@RalfFriedl It lists the file is there. Nothing special. Thank you for your input. I found the real cause finally.
â Kenny Tse
Aug 29 at 7:21
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
As usual it turns out the real cause is not what I think it was.
The "filelist.txt" was an UTF8 textfile which has BOM codes at the beginning of the file as hidden codes. Even "vi", "vim", "nano" are not able to show them.
Removed all those hidden codes and the above rsync codes inside bash script should work.
Sorry for the chaos.
Would you please add into your answer how did you delete that BOM characters bytes ?
â Ã±ÃÂsýù÷
Aug 29 at 10:32
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
As usual it turns out the real cause is not what I think it was.
The "filelist.txt" was an UTF8 textfile which has BOM codes at the beginning of the file as hidden codes. Even "vi", "vim", "nano" are not able to show them.
Removed all those hidden codes and the above rsync codes inside bash script should work.
Sorry for the chaos.
Would you please add into your answer how did you delete that BOM characters bytes ?
â Ã±ÃÂsýù÷
Aug 29 at 10:32
add a comment |Â
up vote
1
down vote
As usual it turns out the real cause is not what I think it was.
The "filelist.txt" was an UTF8 textfile which has BOM codes at the beginning of the file as hidden codes. Even "vi", "vim", "nano" are not able to show them.
Removed all those hidden codes and the above rsync codes inside bash script should work.
Sorry for the chaos.
Would you please add into your answer how did you delete that BOM characters bytes ?
â Ã±ÃÂsýù÷
Aug 29 at 10:32
add a comment |Â
up vote
1
down vote
up vote
1
down vote
As usual it turns out the real cause is not what I think it was.
The "filelist.txt" was an UTF8 textfile which has BOM codes at the beginning of the file as hidden codes. Even "vi", "vim", "nano" are not able to show them.
Removed all those hidden codes and the above rsync codes inside bash script should work.
Sorry for the chaos.
As usual it turns out the real cause is not what I think it was.
The "filelist.txt" was an UTF8 textfile which has BOM codes at the beginning of the file as hidden codes. Even "vi", "vim", "nano" are not able to show them.
Removed all those hidden codes and the above rsync codes inside bash script should work.
Sorry for the chaos.
answered Aug 29 at 7:24
Kenny Tse
112
112
Would you please add into your answer how did you delete that BOM characters bytes ?
â Ã±ÃÂsýù÷
Aug 29 at 10:32
add a comment |Â
Would you please add into your answer how did you delete that BOM characters bytes ?
â Ã±ÃÂsýù÷
Aug 29 at 10:32
Would you please add into your answer how did you delete that BOM characters bytes ?
â Ã±ÃÂsýù÷
Aug 29 at 10:32
Would you please add into your answer how did you delete that BOM characters bytes ?
â Ã±ÃÂsýù÷
Aug 29 at 10:32
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f465329%2frsync-files-from-unable-to-handle-filename-with-subfolder%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
2
You did verify that the file does exist?
â RalfFriedl
Aug 28 at 16:40
Yes definitely. I can rsync the file by command line
â Kenny Tse
Aug 29 at 1:47
Show the output from
ls -l /home/somewhere/subfolder/746fbd52ec4441b88f62ead5beb8e57e, copy the path exactly from the error message rsync gives. Run `strace -f -e file rsync ..." and show the line that refers to this file. Append the information to the question, not as a comment.â RalfFriedl
Aug 29 at 5:22
@RalfFriedl It lists the file is there. Nothing special. Thank you for your input. I found the real cause finally.
â Kenny Tse
Aug 29 at 7:21