-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, in the case of using v3 with --link-dest and not --checksum most
of the initial activity on the sender would be doing calls to stat()
to index what is there.
The receiving side would be doing 2x the stat() calls (you have 2
- --link-dest dirs for
On 11/13/2013 12:03:21 PM, Kevin Korb wrote:
OK, in the case of using v3 with --link-dest and not --checksum most
of the initial activity on the sender would be doing calls to stat()
to index what is there.
The receiving side would be doing 2x the stat() calls (you have 2
--link-dest dirs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To an extent it is serially. The sender tells the receiver what it
needs to stat(). However, thanks to incremental indexing it will
parallelize but the receiver will not go beyond what the receiver has
sent.
Read the --recursive section of the man
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there a hard links limit? I have been in the 70-80 million range
on ext4 without a problem (other than performance which is why I
switched to ZFS for that use case).
On 11/13/13 13:59, Karl O. Pinc wrote:
On 11/13/2013 12:03:21 PM, Kevin Korb
necessarily 11/13/2013 01:04:29 PM, Kevin Korb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there a hard links limit? I have been in the 70-80 million range
on ext4 without a problem (other than performance which is why I
switched to ZFS for that use case).
It's a per-file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I wasn't saying I had millions of links of the same file. It was
hundreds of link-dest backups some of which contained a few but not
all that many links. I wasn't doing a link-dest backup of something
link heavy.
On 11/13/13 15:01, Karl O. Pinc
