total is non‐zero). For example: "(reg:
5, dir: 3, link: 2, dev: 1, special: 1)" lists the totals
for regular files, directories, symlinks, devices, and
special files. If any of value is 0, it is completely
omitted from the list.
o Number of created files is the count of how many "files"
(generic sense) were created (as opposed to updated). The
total count will be followed by a list of counts by file‐
type (if the total is non‐zero).
o Number of deleted files is the count of how many "files"
(generic sense) were deleted. The total count will be
followed by a list of counts by filetype (if the total is
non‐zero). Note that this line is only output if dele‐
tions are in effect, and only if protocol 31 is being used
(the default for rsync 3.1.x).
o Number of regular files transferred is the count of normal
files that were updated via rsync’s delta‐transfer algo‐
rithm, which does not include dirs, symlinks, etc. Note
that rsync 3.1.0 added the word "regular" into this head‐
ing.
o Total file size is the total sum of all file sizes in the
transfer. This does not count any size for directories or
special files, but does include the size of symlinks.
o Total transferred file size is the total sum of all files
sizes for just the transferred files.
o Literal data is how much unmatched file‐update data we had
to send to the receiver for it to recreate the updated
files.
o Matched data is how much data the receiver got locally
when recreating the updated files.
o File list size is how big the file‐list data was when the
sender sent it to the receiver. This is smaller than the
in‐memory size for the file list due to some compressing
of duplicated data when rsync sends the list.
o File list generation time is the number of seconds that
the sender spent creating the file list. This requires a
modern rsync on the sending side for this to be present.
o File list transfer time is the number of seconds that the
sender spent sending the file list to the receiver.
o Total bytes sent is the count of all the bytes that rsync
sent from the client side to the server side.
o Total bytes received is the count of all non‐message bytes
that rsync received by the client side from the server
side. "Non‐message" bytes means that we don’t count the
bytes for a verbose message that the server sent to us,
which makes the stats more consistent.
--8‐bit‐output, -8
This tells rsync to leave all high‐bit characters unescaped in
the output instead of trying to test them to see if they’re valid
in the current locale and escaping the invalid ones. All control
characters (but never tabs) are always escaped, regardless of
this option’s setting.
The escape idiom that started in 2.6.7 is to output a literal
backslash (\) and a hash (#), followed by exactly 3 octal digits.
For example, a newline would output as "\#012". A literal back‐
slash that