I am running rsync 3.0.7 and I think I have hit the following bug from 3.0.1: NEWS for rsync 3.0.1 (3 Apr 2008) Protocol: 30 (unchanged) Changes since 3.0.0: Fixed a bug in the handling of xattr values that could cause rsync to not think that a file's extended attributes are up-to-date. However because I am running rsync over a lustre file system, I am not sure if this is the same bug. How could I test this?? Please see below the symptom : * [root at solardm3 tsantos]# rsync -aviHX source/ destin/* sending incremental file list .d..t...... ./ >f+++++++++ file2 >f+++++++++ file3 >f+++++++++ file4 >f+++++++++ file5 >f+++++++++ filelistcd >f+++++++++ hardlink cL+++++++++ link -> file1 >f+++++++++ todayfile cd+++++++++ dir/ cd+++++++++ dir1/ cd+++++++++ dir2/ hf+++++++++ file1 => hardlink sent 2217 bytes received 204 bytes 4842.00 bytes/sec total size is 75 speedup is 0.03 *[root at solardm3 tsantos]# rsync -aviHX source/ destin/* sending incremental file list .f........x file1 .f........x file2 .f........x file3 .f........x file4 .f........x file5 .f........x filelistcd hf........x hardlink .f........x todayfile sent 1863 bytes received 62 bytes 3850.00 bytes/sec total size is 75 speedup is 0.04 *[root at solardm3 tsantos]# rsync -aviHX source/ destin/* sending incremental file list .f........x file1 .f........x file2 .f........x file3 .f........x file4 .f........x file5 .f........x filelistcd hf........x hardlink .f........x todayfile sent 1863 bytes received 62 bytes 3850.00 bytes/sec total size is 75 speedup is 0.04 Thanks in advance Tarso -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20100413/c64e28c4/attachment.html>
On Mon, Apr 12, 2010 at 7:51 AM, Tarso dos Santos < tarso.dos.santos at oracle.com> wrote:> I am running rsync 3.0.7 and I think I have hit the following bug from > 3.0.1: > > NEWS for rsync 3.0.1 (3 Apr 2008) Protocol: 30 (unchanged) Changes since > 3.0.0: > Fixed a bug in the handling of xattr values that could cause rsync to not > think that a file's extended attributes are up-to-date. >What you should do is to dump the xattrs of a file in its source version and its dest version and see where they differ. I'd imagine that rsync is trying to set an xattr and it is getting tweaked somehow by the filesystem so that it doesn't get reported back to rsync has having the right value. You can then try setting a value on the destination file manually and see if that hypothesis is right or not. If you think that rsync is doing the wrong thing, figuring out exactly what xargs are tripping up rsync should help. ..wayne.. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20100502/38271a51/attachment.html>