https://bugzilla.samba.org/show_bug.cgi?id=1678

           Summary: --link-dest doesn't create hard links on remote system.
           Product: rsync
           Version: 2.6.3
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P3
         Component: core
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
         QAContact: [EMAIL PROTECTED]


The following ought to work, and doesn't.

1) On computer "espresso":

rsync -av -e ssh --delete --modify-window=60 --link-dest=../backup.1
home/rjn/bin [EMAIL PROTECTED]:backup/backup.0

2) On computer "pistachio":

mv backup/backup.0 backup/backup.1

3) repeat (1)


This ought to result in 2 directories on pistachio, each of whose files share
inodes. (i.e. backup.0/bin/foo and backup.1/bin/foo are hard links to each
other). However, they are *not* hard links, but copies!


Some diagnostics:

(i)The above does work  correctly using a different source machine, mocha, (and
in fact several others which I have tried).

(ii)It works OK when the backup is on the same machine (i.e. both on espresso)

(iii)I've tried with very large values of --modify-window, and it makes no
difference. The files in /home/rjn/bin are not being changed at all between
steps 1 and 3

(iv) Rsync versions:
espresso: rsync  version 2.6.3pre1  protocol version 28  (Mandrake 10.1 Beta 2)
mocha: rsync  version 2.6.2  protocol version 28


I apologise if this isn't a bug at all, but results from my own error, however
I've spent several hours testing this to no avail! It does seem to only occur
with machines where the source machine is running a version > 2.6.2. 

Thanks for your help - Richard

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Reply via email to