[Bug 6746] file from link-dest-source is copies and not linked for identical files

samba-bugs at samba.org samba-bugs at samba.org
Fri Apr 1 12:54:06 MDT 2011


--- Comment #7 from ED Fochler <samba at liquidbinary.com> 2011-04-01 18:54:05 UTC ---
(In reply to comment #6)
I apologize for talking to myself on-list, but I've become enlightened about my

Alphabetical order matters.  If A has already been copied and B is a new
hardlink, then all will work as expected.

if B has already been copied, and A is the new hardlink, rsync v3 doesn't know
it's an inode match until later in the transfer.

In my case a new file A was copied over and then B was hardlinked to it.  For
all files in the current transfer, the linking worked, but the transfer was not
necessary as the file already existed in the destination, just later in

I would say that using -P for snapshots implies --protocol=29 for the current

I don't know if my problem is related to the link-dest bug that Dieter
originally described, but is the same as Theo's problem.

Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the rsync mailing list