Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #196153

Re: rsync error -- "Protocol incompatibility" Why?

Show all headers | View raw

On 05/28/2018 07:15 AM, David wrote:
> On 28 May 2018 at 22:07, Richard Owlett <rowlett@cloud85.net> wrote:
>> I had used rsync to back up a different partition with no problems.
>>
>> I used that command as a model to attempt to backup another partition.
>>
>>> root@debian-jan13:~# root@debian-jan13:~# rsync --verbose  --progress
>>> --stats --recursive --times --perms --links /media/root/drescued_commo/
>>> /media/root/backups/drescued_commo/
>>> sending incremental file list
>>> rsync: change_dir "/media/root/drescued_commo" failed: No such file or
>>> directory (2)
> 
> In the above command you have "drescued_commo".
> 
>> I then checked for existence of source:
>>
>>> root@debian-jan13:~# ls /media/root
>>> 17oct2017   debian64          rco             sda14.bak
>>> backups     gddrescued_commo  rco1            sd-card
>>> common      good-fvwm         recover-common  stretch-2nd
>>> common-bak  jessie8-6-sda6    sci-fi-dvds     tomboy-testing
>>> root@debian-jan13:~#
> 
> In the above output you have "gddrescued_commo" which
> is not the same as "drescued_commo".
> 
> Which would explain why rsync says:
> "rsync: change_dir "/media/root/drescued_commo" failed: No such file
> or directory (2)"
> 
> Does that help?
> 


*DUH* <slaps head and drinks second cup of coffee>

But that raises another question.
Why does error message identify a protocol problem after having 
correctly identified the problem as "No such file or directory".

Wouldn't "Error 3 --  Errors selecting input/output files, dirs"
be less misleading?

Thanks

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

rsync error -- "Protocol incompatibility" Why? Richard Owlett <rowlett@cloud85.net> - 2018-05-28 14:10 +0200
  Re: rsync error -- "Protocol incompatibility" Why? likcoras <likcoras@riseup.net> - 2018-05-28 14:20 +0200
    Re: rsync error -- "Protocol incompatibility" Why? Richard Owlett <rowlett@cloud85.net> - 2018-05-28 14:40 +0200
  Re: rsync error -- "Protocol incompatibility" Why? David <bouncingcats@gmail.com> - 2018-05-28 14:20 +0200
    Re: rsync error -- "Protocol incompatibility" Why? Richard Owlett <rowlett@cloud85.net> - 2018-05-28 14:50 +0200
      Re: rsync error -- "Protocol incompatibility" Why? David <bouncingcats@gmail.com> - 2018-05-28 15:10 +0200
        Re: rsync error -- "Protocol incompatibility" Why? Richard Owlett <rowlett@cloud85.net> - 2018-05-28 15:40 +0200
        Re: rsync error -- "Protocol incompatibility" Why? The Wanderer <wanderer@fastmail.fm> - 2018-05-28 16:10 +0200
      Re: rsync error -- "Protocol incompatibility" Why? Dan Purgert <dan@djph.net> - 2018-05-28 15:30 +0200
  Seeing with comprehension - was [ rsync error -- "Protocol  incompatibility" Why?] Richard Owlett <rowlett@cloud85.net> - 2018-05-28 18:00 +0200
    Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?] Gene Heskett <gheskett@shentel.net> - 2018-05-28 18:00 +0200
      Re: Seeing with comprehension - was [ rsync error -- "Protocol  incompatibility" Why?] Richard Owlett <rowlett@cloud85.net> - 2018-05-28 18:20 +0200
        Re: Seeing with comprehension - was [ rsync error -- "Protocol  incompatibility" Why?] Richard Owlett <rowlett@cloud85.net> - 2018-05-28 18:30 +0200
    Re: Seeing with comprehension - was [ rsync error -- "Protocol  incompatibility" Why?] <tomas@tuxteam.de> - 2018-05-28 18:10 +0200
    Re: Seeing with comprehension - was [ rsync error -- "Protocol   incompatibility" Why?] Dan Purgert <dan@djph.net> - 2018-05-28 20:10 +0200
      Re: Seeing with comprehension - was [ rsync error -- "Protocol  incompatibility" Why?] Richard Owlett <rowlett@cloud85.net> - 2018-05-28 21:10 +0200

csiph-web