Why is my rsync transfer slow?

Kevin Korb kmk at sanitarium.net
Sat Jan 23 20:16:08 UTC 2016

Hash: SHA1

As long as it still sees both links it is fine.

Essentially, the way it works is that whenever rsync -H (on the
source) sees a file with a link count >1 it remembers the
inode#>filename pair.  If it finds another instance of that inode it
then links to the same file on the target.  So, if you abort after it
copies one but before it links the other it will still handle it
correctly on the next run.

It just won't handle it if you rsync tree #1 then rsync tree #2.  It
won't see a hard link that is common to both since it wasn't analyzing
them together.

On 01/23/2016 03:04 PM, dbonde+forum+rsync.lists.samba.org at gmail.com
> On 2016-01-23 17:50, Kevin Korb wrote:
>> It will, assuming it sees both links in the same rsync run.
> How does one handle interrupted transfers if one wants to preserve
> hard links? Would --partial and --append-verify work?

- -- 
	Kevin Korb			Phone:    (407) 252-6853
	Systems Administrator		Internet:
	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
	Orlando, Florida		kmk at sanitarium.net (personal)
	Web page:			http://www.sanitarium.net/
	PGP public key available on web site.
Version: GnuPG v2


More information about the rsync mailing list