From man rsyncd.conf
max connections
This parameter allows you to specify the maximum number of
simultaneous connections you will allow. Any clients connecting
when the maximum has been reached will receive a message telling
them to
Hi,
I'm using rsync with --link-dest to do backups.
I don't have any sparse files, but someday I might.
Should I be using --sparse?
I notice that -S is not implied by -a. This makes
me suspicious that --sparse is not (yet?) suitable
for general purpose use. There also seem to be
outstanding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sparse doesn't work on some filesystems (explained in man rsync).
Other than that it is fine. Any file that has a big chunk of null
characters will be written sparsely and take up less space.
Note that you can't always use it when restoring. Do not
Please let me know
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Essentially, a sparse file is a file that is stored sparsely meaning
that any long string of nulls that happens to be on a filesystem block
will not actually be allocated by the filesystem so you don't have to
store that block of nothing. When you
On 06/09/12 04:31, Kevin Korb wrote:
Also, this is during a restore that I am talking about. I don't see a
problem with using --sparse on everything during the backup.
Conversely, is there any problem with NOT using sparse on sparse files?
i.e. I know it will use more space - but will a sparse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nope, it will just eat space storing nothings rather than generating
the nothings when you read the file.
Note that when you copy a sparse file sparsely it doesn't necessarily
sparse the same blocks so the files still might not be the same size.
On
