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

Groups > linux.debian.user > #196148 > unrolled thread

rsync error -- "Protocol incompatibility" Why?

Back to article view | Back to linux.debian.user

Contents

  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

#196148 — rsync error -- "Protocol incompatibility" Why?

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)

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:~# 


The rsync man page identifies error as "Protocol incompatibility".
Under the heading "Diagnostics" speaks of problems when using ssh to 
communicate with another machine.
It later says:

> If you are having trouble debugging filter patterns, then try specifying
> the -vv option. At this level of verbosity rsync will show why each individual
> file is included or excluded. 

I reran with -vv and received:

> root@debian-jan13:~# 
> root@debian-jan13:~# rsync -vv  --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)
> delta-transmission disabled for local transfer or --whole-file
> total: matches=0  hash_hits=0  false_alarms=0 data=0
> 
> rsync[1291] (sender) heap statistics:
>   arena:         299008   (bytes from sbrk)
>   ordblks:            2   (chunks not in use)
>   smblks:             2
>   hblks:              0   (chunks from mmap)
>   hblkhd:             0   (bytes from mmap)
>   allmem:        299008   (bytes from sbrk + mmap)
>   usmblks:            0
>   fsmblks:          128
>   uordblks:      168136   (bytes used)
>   fordblks:      130872   (bytes free)
>   keepcost:      130640   (bytes in releasable chunk)
> 
> rsync[1293] (server receiver) heap statistics:
>   arena:         135168   (bytes from sbrk)
>   ordblks:            1   (chunks not in use)
>   smblks:             2
>   hblks:              0   (chunks from mmap)
>   hblkhd:             0   (bytes from mmap)
>   allmem:        135168   (bytes from sbrk + mmap)
>   usmblks:            0
>   fsmblks:          128
>   uordblks:      134160   (bytes used)
>   fordblks:        1008   (bytes free)
>   keepcost:         880   (bytes in releasable chunk)
> 
> rsync[1292] (server generator) heap statistics:
>   arena:         135168   (bytes from sbrk)
>   ordblks:            1   (chunks not in use)
>   smblks:             2
>   hblks:              0   (chunks from mmap)
>   hblkhd:             0   (bytes from mmap)
>   allmem:        135168   (bytes from sbrk + mmap)
>   usmblks:            0
>   fsmblks:          128
>   uordblks:      134160   (bytes used)
>   fordblks:        1008   (bytes free)
>   keepcost:         880   (bytes in releasable chunk)

HELP please.
TIA

[toc] | [next] | [standalone]

#196149

On 05/28/2018 09:07 PM, Richard Owlett 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)
> 
> 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:~# 

Are you sure it's not a typo? I can't see "/media/root/drescued_commo/",
only "/media/root/gddrescued_commo"...

[toc] | [prev] | [next] | [standalone]

#196152

On 05/28/2018 07:15 AM, likcoras wrote:
> On 05/28/2018 09:07 PM, Richard Owlett 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)
>>
>> 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:~#
> 
> Are you sure it's not a typo? I can't see "/media/root/drescued_commo/",
> only "/media/root/gddrescued_commo"...
> 
> 

*DUH* <slaps head and gets second cup of coffee>
Thanks

[toc] | [prev] | [next] | [standalone]

#196150

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?

[toc] | [prev] | [next] | [standalone]

#196153

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

[toc] | [prev] | [next] | [standalone]

#196154

On 28 May 2018 at 22:47, Richard Owlett <rowlett@cloud85.net> wrote:
>
> 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".

man rsync says:
"EXIT VALUES
       0      Success
       1      Syntax or usage error
       2      Protocol incompatibility
[etc]
"

An *exit value* (aka exit status) is an entirely
different concept to an "error number".

Exit status is partially explained here:
http://mywiki.wooledge.org/BashGuide/TestsAndConditionals?highlight=%28exit%29%7C%28status%29#Exit_Status

The exit status = 2 mentioned in the man page has nothing
to do with the 2 in the error message
"rsync: change_dir "/media/root/drescued_commo" failed: No such file
or directory (2)"

The 2 in that message is a reference to errors reported by the standard
library of the C programming language, as explained here:
https://www.ibm.com/developerworks/aix/library/au-errnovariable/index.html

[toc] | [prev] | [next] | [standalone]

#196156

On 05/28/2018 08:08 AM, David wrote:
> On 28 May 2018 at 22:47, Richard Owlett <rowlett@cloud85.net> wrote:
>>
>> 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".
> 
> man rsync says:
> "EXIT VALUES
>         0      Success
>         1      Syntax or usage error
>         2      Protocol incompatibility
> [etc]
> "
> 
> An *exit value* (aka exit status) is an entirely
> different concept to an "error number".
> 
> Exit status is partially explained here:
> http://mywiki.wooledge.org/BashGuide/TestsAndConditionals?highlight=%28exit%29%7C%28status%29#Exit_Status
> 
> The exit status = 2 mentioned in the man page has nothing
> to do with the 2 in the error message
> "rsync: change_dir "/media/root/drescued_commo" failed: No such file
> or directory (2)"
> 
> The 2 in that message is a reference to errors reported by the standard
> library of the C programming language, as explained here:
> https://www.ibm.com/developerworks/aix/library/au-errnovariable/index.html
> 
> 

Thank you. One of those things a non-programmer has to crash into.
My formal programming background is CORC, CUPL, and a dash of FORTRAN 
(of a similar vintage).

[toc] | [prev] | [next] | [standalone]

#196157

[Multipart message — attachments visible in raw view] — view raw

On 2018-05-28 at 09:08, David wrote:

> On 28 May 2018 at 22:47, Richard Owlett <rowlett@cloud85.net> wrote:
>
>> 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".
> 
> man rsync says:
> "EXIT VALUES
>        0      Success
>        1      Syntax or usage error
>        2      Protocol incompatibility
> [etc]
> "
> 
> An *exit value* (aka exit status) is an entirely
> different concept to an "error number".
> 
> Exit status is partially explained here:
> http://mywiki.wooledge.org/BashGuide/TestsAndConditionals?highlight=%28exit%29%7C%28status%29#Exit_Status
> 
> The exit status = 2 mentioned in the man page has nothing
> to do with the 2 in the error message
> "rsync: change_dir "/media/root/drescued_commo" failed: No such file
> or directory (2)"
> 
> The 2 in that message is a reference to errors reported by the standard
> library of the C programming language, as explained here:
> https://www.ibm.com/developerworks/aix/library/au-errnovariable/index.html

For additional reference, when I reproduced the error locally, the exit
code (as reported by 'echo $?', run immediately after the rsync command)
was 23.

The rsync man page documents exit value 23 as being "Partial transfer
due to error", which is perfectly consistent with the behavior at hand.

(In my case the "partial" transfer consisted of transferring zero files,
out of a total of one file requested, but the principle is the same.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#196155

Richard Owlett wrote:
> On 05/28/2018 07:15 AM, David wrote:
>> On 28 May 2018 at 22:07, Richard Owlett <rowlett@cloud85.net> wrote:
>> 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?

Depends on "what part" was throwing the error -- e.g. if it was ssh or
something telling rsync "no can do", then it'd be a different error.


-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

[toc] | [prev] | [next] | [standalone]

#196159 — Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

Question 1
I tried to backup another partition.
The command I *THOUGHT* I gave was:

> rsync --verbose  --progress --stats --recursive --times --perms --links \ 
> /media/richard/jessie8-6-sda6/  /media/richard/backups/jessie8-6-sda6/

I got a similar error message to last time (i.e. 'file not found').
The problem was a non-printing character (space?) after the first line).
Is there a graphical editor which would high-lite that "something" is there?

Question 2.
When it ran I happened to be sitting by the display and noticed things 
of the form:
> 
> var/log/lightdm/x-2.log.old
>             963 100%    2.32kB/s    0:00:00 (xfr#88022, to-chk=21/128033)
> var/log/speech-dispatcher/
> var/mail/
> var/opt/
> var/spool/
> var/spool/mail -> ../mail
> var/spool/anacron/
> var/spool/anacron/cron.daily
>               9 100%    0.02kB/s    0:00:00 (xfr#88023, to-chk=14/128033)

Do the lines not followed by statistics just mean "0 length files" or 
"it's just a link"?

At the end it said:

> 
* Number of files: 128,033 (reg: 88,026, dir: 7,503, link: 32,466, dev: 
37, special: 1)*
*  Number of created files: 127,995 (reg: 88,026, dir: 7,503, link: 
32,466)*> Number of deleted files: 0
> Number of regular files transferred: 88,026
> Total file size: 2,837,281,458 bytes
> Total transferred file size: 2,836,525,656 bytes
> Literal data: 2,836,525,656 bytes
> Matched data: 0 bytes
> File list size: 4,717,282
> File list generation time: 0.001 seconds
> File list transfer time: 0.000 seconds
> Total bytes sent: 2,845,135,440
> Total bytes received: 1,819,035
> 
* sent 2,845,135,440 bytes  received 1,819,035 bytes  2,837,024.89 
bytes/sec *
> total size is 2,837,281,458  speedup is 1.00
> root@debian-jan13:~# 
> 

The high-lited lines caught my attention.
I take the first two seem just to report that rsync is copying 
intelligently.

I don't understand what the third is telling me when there is a 
difference between bytes sent and received. I assume it is benign as the 
was no error reported.

TIA

[toc] | [prev] | [next] | [standalone]

#196160 — Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

On Monday 28 May 2018 11:53:26 Richard Owlett wrote:

> Question 1
> I tried to backup another partition.
>
> The command I *THOUGHT* I gave was:
> > rsync --verbose  --progress --stats --recursive --times --perms
> > --links \ /media/richard/jessie8-6-sda6/ 
> > /media/richard/backups/jessie8-6-sda6/
>
> I got a similar error message to last time (i.e. 'file not found').
> The problem was a non-printing character (space?) after the first
> line). Is there a graphical editor which would high-lite that
> "something" is there?
>
geany has quite a menu of things to enable visibility of inkless 
characters.

> Question 2.
> When it ran I happened to be sitting by the display and noticed things
>
> of the form:
> > var/log/lightdm/x-2.log.old
> >             963 100%    2.32kB/s    0:00:00 (xfr#88022,
> > to-chk=21/128033) var/log/speech-dispatcher/
> > var/mail/
> > var/opt/
> > var/spool/
> > var/spool/mail -> ../mail
> > var/spool/anacron/
> > var/spool/anacron/cron.daily
> >               9 100%    0.02kB/s    0:00:00 (xfr#88023,
> > to-chk=14/128033)
>
> Do the lines not followed by statistics just mean "0 length files" or
> "it's just a link"?
>
> At the end it said:
>
>
> * Number of files: 128,033 (reg: 88,026, dir: 7,503, link: 32,466,
> dev: 37, special: 1)*
> *  Number of created files: 127,995 (reg: 88,026, dir: 7,503, link:
> 32,466)*> Number of deleted files: 0
>
> > Number of regular files transferred: 88,026
> > Total file size: 2,837,281,458 bytes
> > Total transferred file size: 2,836,525,656 bytes
> > Literal data: 2,836,525,656 bytes
> > Matched data: 0 bytes
> > File list size: 4,717,282
> > File list generation time: 0.001 seconds
> > File list transfer time: 0.000 seconds
> > Total bytes sent: 2,845,135,440
> > Total bytes received: 1,819,035
>
> * sent 2,845,135,440 bytes  received 1,819,035 bytes  2,837,024.89
> bytes/sec *
>
> > total size is 2,837,281,458  speedup is 1.00
> > root@debian-jan13:~#
>
> The high-lited lines caught my attention.
> I take the first two seem just to report that rsync is copying
> intelligently.
>
> I don't understand what the third is telling me when there is a
> difference between bytes sent and received. I assume it is benign as
> the was no error reported.
>
> TIA



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#196162 — Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

On 05/28/2018 10:58 AM, Gene Heskett wrote:
> On Monday 28 May 2018 11:53:26 Richard Owlett wrote:
> 
>> Question 1
>> I tried to backup another partition.
>>
>> The command I *THOUGHT* I gave was:
>>> rsync --verbose  --progress --stats --recursive --times --perms
>>> --links \ /media/richard/jessie8-6-sda6/
>>> /media/richard/backups/jessie8-6-sda6/
>>
>> I got a similar error message to last time (i.e. 'file not found').
>> The problem was a non-printing character (space?) after the first
>> line). Is there a graphical editor which would high-lite that
>> "something" is there?
>>
> geany has quite a menu of things to enable visibility of inkless
> characters.
> 

[https://www.geany.org/manual/current/index.html#id116] seems to agree 
with you. I'll try it this afternoon.
Thanks.

[toc] | [prev] | [next] | [standalone]

#196164 — Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

On 05/28/2018 11:18 AM, Richard Owlett wrote:
> On 05/28/2018 10:58 AM, Gene Heskett wrote:
>> On Monday 28 May 2018 11:53:26 Richard Owlett wrote:
>>
>>> Question 1
>>> I tried to backup another partition.
>>>
>>> The command I *THOUGHT* I gave was:
>>>> rsync --verbose  --progress --stats --recursive --times --perms
>>>> --links \ /media/richard/jessie8-6-sda6/
>>>> /media/richard/backups/jessie8-6-sda6/
>>>
>>> I got a similar error message to last time (i.e. 'file not found').
>>> The problem was a non-printing character (space?) after the first
>>> line). Is there a graphical editor which would high-lite that
>>> "something" is there?
>>>
>> geany has quite a menu of things to enable visibility of inkless
>> characters.
>>
> 
> [https://www.geany.org/manual/current/index.html#id116] seems to agree 
> with you. I'll try it this afternoon.
> Thanks.
> 

Works a charm. Didn't have to read manual <grin>

[toc] | [prev] | [next] | [standalone]

#196161 — Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, May 28, 2018 at 10:53:26AM -0500, Richard Owlett wrote:
> Question 1

[...]

> Is there a graphical editor which would high-lite that "something" is there?

Emacs, whitespace mode. It'll show you trailing space, tabs, overlong
lines... you name it.

I'll pass on the other questions (gotta run!)

Cheers
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlsMKJIACgkQBcgs9XrR2kanSgCfVZ7IZkYdau/SmnvswYwvDIhS
0eUAn05zESnApbP/FLXenRaRrfVoe11r
=OIWW
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#196167 — Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

Richard Owlett wrote:
> Question 1
> [...]
> Question 2.
> When it ran I happened to be sitting by the display and noticed things 
> of the form:
>> 
>> var/log/lightdm/x-2.log.old
>>             963 100%    2.32kB/s    0:00:00 (xfr#88022, to-chk=21/128033)
>> var/log/speech-dispatcher/
>> var/mail/
>> var/opt/
>> var/spool/
>> var/spool/mail -> ../mail
>> var/spool/anacron/
>> var/spool/anacron/cron.daily
>>               9 100%    0.02kB/s    0:00:00 (xfr#88023, to-chk=14/128033)
>
> Do the lines not followed by statistics just mean "0 length files" or 
> "it's just a link"?

You mean like "var/mail/" having nothing, and
"var/spool/anacron/cron.daily" having 9 100% [...]

The former is a directory (and unchanged).  The latter is a file that
(appears to have) had a 9 byte update.

>
> At the end it said:
>
>> 
> * Number of files: 128,033 (reg: 88,026, dir: 7,503, link: 32,466, dev: 
> 37, special: 1)*
> *  Number of created files: 127,995 (reg: 88,026, dir: 7,503, link: 
> 32,466)*> Number of deleted files: 0
> [...]
> * sent 2,845,135,440 bytes  received 1,819,035 bytes  2,837,024.89 
> bytes/sec *
>
> The high-lited lines caught my attention.
> I take the first two seem just to report that rsync is copying 
> intelligently.

Yep, pretty much it's:

Line 1 -> 128,033 files on the side initiating the sync
Line 2 -> 127,995 files needed to be created / updated

> I don't understand what the third is telling me when there is a 
> difference between bytes sent and received. I assume it is benign as the 
> was no error reported.

IIRC it's bytes we sent to the other end, and bytes the other end sent
back to us (ACKs, other stuff).  I've got a big guide on rsync around
here somewhere, will send a link if I dig it up.


-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

[toc] | [prev] | [next] | [standalone]

#196169 — Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]

On 05/28/2018 12:57 PM, Dan Purgert wrote:
> Richard Owlett wrote:
>> Question 1
>> [...]
>> Question 2.
>> When it ran I happened to be sitting by the display and noticed things
>> of the form:
>>>
>>> var/log/lightdm/x-2.log.old
>>>              963 100%    2.32kB/s    0:00:00 (xfr#88022, to-chk=21/128033)
>>> var/log/speech-dispatcher/
>>> var/mail/
>>> var/opt/
>>> var/spool/
>>> var/spool/mail -> ../mail
>>> var/spool/anacron/
>>> var/spool/anacron/cron.daily
>>>                9 100%    0.02kB/s    0:00:00 (xfr#88023, to-chk=14/128033)
>>
>> Do the lines not followed by statistics just mean "0 length files" or
>> "it's just a link"?
> 
> You mean like "var/mail/" having nothing, and
> "var/spool/anacron/cron.daily" having 9 100% [...]
> 
> The former is a directory (and unchanged).  The latter is a file that
> (appears to have) had a 9 byte update.
> 
>>
>> At the end it said:
>>
>>>
>> * Number of files: 128,033 (reg: 88,026, dir: 7,503, link: 32,466, dev:
>> 37, special: 1)*
>> *  Number of created files: 127,995 (reg: 88,026, dir: 7,503, link:
>> 32,466)*> Number of deleted files: 0
>> [...]
>> * sent 2,845,135,440 bytes  received 1,819,035 bytes  2,837,024.89
>> bytes/sec *
>>
>> The high-lited lines caught my attention.
>> I take the first two seem just to report that rsync is copying
>> intelligently.
> 
> Yep, pretty much it's:
> 
> Line 1 -> 128,033 files on the side initiating the sync
> Line 2 -> 127,995 files needed to be created / updated
> 
>> I don't understand what the third is telling me when there is a
>> difference between bytes sent and received. I assume it is benign as the
>> was no error reported.
> 
> IIRC it's bytes we sent to the other end, and bytes the other end sent
> back to us (ACKs, other stuff).  I've got a big guide on rsync around
> here somewhere, will send a link if I dig it up.
> 
> 

I suspected as much.
Links enthusiastically recieved :}

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web