[prev in list] [next in list] [prev in thread] [next in thread]
List: freebsd-ports
Subject: Re: rsync 3.1.1 zlib might not work
From: Emanuel Haupt <ehaupt () FreeBSD ! org>
Date: 2014-06-30 7:51:16
Message-ID: 20140630095116.2900595e7c7667cc6c8af370 () FreeBSD ! org
[Download RAW message or body]
Dewayne Geraghty <dewayne.geraghty@heuristicsystems.com.au> wrote:
> Emanuel,
> Thanks for bringing to our attention, I transmit ~900MB of backups
> over the WAN rather than the uncompressed 9G database. You've saved
> a client excess use charges.
>
> I tested using highly compressible data (mostly nulls) and it seems to
> work as expected.
>
> Without -z or -zz: Sent 593 bytes speadup 0.82
> With -z : Sent 593 bytes speadup 0.82 (Unexpected. Should be in
> ports/UPDATING)
> With -zz: sent 85 bytes speedup is 4.27 (Expected)
>
> Detail
> # rm ./b && printf "%512c"a > a && rsync -av ./a ./b
> sending incremental file list
> a
>
> sent 593 bytes received 35 bytes 1,256.00 bytes/sec
> total size is 512 speedup is 0.82
>
> # rm ./b && printf "%512c"a > a && rsync -avz ./a ./b
> This rsync lacks old-style --compress due to its external zlib. Try
> -zz. Continuing without compression.
>
> sending incremental file list
> a
>
> sent 593 bytes received 35 bytes 1,256.00 bytes/sec
> total size is 512 speedup is 0.82
>
> # rm ./b && printf "%512c"a > a && rsync -avzz ./a ./b
> sending incremental file list
> a
>
> sent 85 bytes received 35 bytes 240.00 bytes/sec
> total size is 512 speedup is 4.27
>
> # ldd `which rsync`
> /usr/local/bin/rsync:
> libz.so.6 => /lib/libz.so.6 (0x800873000)
> libc.so.7 => /lib/libc.so.7 (0x800a87000)
>
> Perhaps ports/UPDATING should alert users to the new requirement to
> use -zz (not in man page) instead of -z or --compress?
Indeed there seems to be some sort of confusion on how to use -z vs.
-zz. However there -zz mentioned in the manpage of 3.1.1:
-z, --compress
With this option, rsync compresses the file data as it is sent
to the destination machine, which reduces the amount of data
being transmitted -- something that is useful over a slow con-
nection.
Note that this option typically achieves better compression
ratios than can be achieved by using a compressing remote shell
or a compressing transport because it takes advantage of the
implicit information in the matching data blocks that are not
explicitly sent over the connection. This matching-data com-
pression comes at a cost of CPU, though, and can be disabled by
repeating the -z option, but only if both sides are at least
version 3.1.1.
Note that if your version of rsync was compiled with an external
zlib (instead of the zlib that comes packaged with rsync) then
it will not support the old-style compression, only the
new-style (repeated-option) compression. In the future this
new-style compression will likely become the default.
The client rsync requests new-style compression on the server
via the --new-compress option, so if you see that option
rejected it means that the server is not new enough to support
-zz. Rsync also accepts the --old-compress option for a future
time when new-style compression becomes the default.
See the --skip-compress option for the default list of file suf-
fixes that will not be compressed.
This is currently being tracked under:
https://bugzilla.samba.org/show_bug.cgi?id=10677
I'm considering an UPDATED entry after some other issues with the port have
been resolved.
Emanuel
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic