[Bug 1678] --link-dest doesn't create hard links on remote system.

[samba-bugs at samba.org]

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





------- Additional Comments From rsync at richardneill.org  2004-09-07 13:59 -------
Thanks for your reply. I've narrowed it down to being caused by -o. Here are the
steps I performed, exactly as they were done, so you can check my diagnosis.
I've used absolute paths as requested.

(I've had to use slightly different machines to do the tests this time:

Rsync versions:
  mocha    rsync  version 2.6.3pre1  protocol version 28
  romance  rsync  version 2.6.0  protocol version 27
  apircam  rsync  version 2.5.7  protocol version 26

---------------------------------------------------------------

[A] This way, (apircam->romance) works as expected:

1)on romance:

   rm -rf /home/rjn/test
   mkdir /home/rjn/test
   
2)on apircam:

   rm -rf /home/rjn/test/source
   mkdir  -p /home/rjn/test/source
   touch  /home/rjn/test/source/file1
   touch  /home/rjn/test/source/file2
 
   rsync -av -e ssh  --link-dest=/home/rjn/test/backup.1 /home/rjn/test/source
rjn at romance.al.cl.cam.ac.uk:test/backup.0


3) on romance:

   ls -i /home/rjn/test/backup.[01]/source/file1
       66 /home/rjn/test/backup.0/source/file1

   mv /home/rjn/test/backup.0  /home/rjn/test/backup.1


4)on apircam:
    
    rsync -av -e ssh  --link-dest=/home/rjn/test/backup.1 /home/rjn/test/source
rjn at romance.al.cl.cam.ac.uk:test/backup.0

5)on romance 

    ls -i /home/rjn/test/backup.[01]/source/file1
       66 /home/rjn/test/backup.0/source/file1  
       66 /home/rjn/test/backup.1/source/file1

6)Success! We have the same inode numbers!

---------------------------------------------------------------

[B] This way, (mocha->romance) fails:

1)on romance:

   rm -rf /home/rjn/test
   mkdir /home/rjn/test
   
2)on mocha:

   rm -rf /home/rjn/test/source
   mkdir -p /home/rjn/test/source
   touch  /home/rjn/test/source/file1
   touch  /home/rjn/test/source/file2
 
   rsync -av -e ssh  --link-dest=/home/rjn/test/backup.1 /home/rjn/test/source
rjn at romance.al.cl.cam.ac.uk:test/backup.0


3)on romance:

    ls -i /home/rjn/test/backup.[01]/source/file1
        66 /home/rjn/test/backup.0/source/file1

    mv /home/rjn/test/backup.0  /home/rjn/test/backup.1


4)on mocha:

   rsync -av -e ssh  --link-dest=/home/rjn/test/backup.1 /home/rjn/test/source
rjn at romance.al.cl.cam.ac.uk:test/backup.0

5)on romance 

   ls -i /home/rjn/test/backup.[01]/source/file1
       70 /home/rjn/test/backup.0/source/file1 
       66 /home/rjn/test/backup.1/source/file1

6)Failure! Inode numbers are different.

---------------------------------------------------------------

Further diagnostics:

1) using -r instead of -a causes [A] to fail as well.

2) using -rlptD instead of -a causes [B] to work.

3) [B] still works if -g is added (i.e. -rlptD)

4) [B] fails with -rlptDo, or -a

5) Here is a stat at the end of step B5:

  File: `/home/rjn/test/backup.0/source/file1'
  Size: 0               Blocks: 0          IO Block: 131072 regular empty file
Device: 2209h/8713d     Inode: 70          Links: 1
Access: (0644/-rw-r--r--)  Uid: (  501/     rjn)   Gid: (  501/     rjn)
Access: 2004-09-07 21:41:22.000000000 +0100
Modify: 2004-09-07 21:13:42.000000000 +0100
Change: 2004-09-07 21:41:22.000000000 +0100

  File: `/home/rjn/test/backup.1/source/file1'
  Size: 0               Blocks: 0          IO Block: 131072 regular empty file
Device: 2209h/8713d     Inode: 66          Links: 1
Access: (0644/-rw-r--r--)  Uid: (  501/     rjn)   Gid: (  501/     rjn)
Access: 2004-09-07 21:41:10.000000000 +0100
Modify: 2004-09-07 21:13:42.000000000 +0100
Change: 2004-09-07 21:41:22.000000000 +0100


6) On all systems, rjn is a regular user, not root. 

7) More details of the computers:

apircam: Mandrake 9.2, kernel 2.4.22-10mdk, ReiserFS
mocha: Mandrake cooker (10.1), kernel 2.6.3-9mdk-p3-smp-64GB, ReiserFS
romance: Mandrake 10, kernel 2.6.3-15mdk-p3-smp-64GB, ReiserFS
  

-- 
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.