Hi,
it seems that one already has been fixed in 3.1.0, see
https://bugzilla.samba.org/show_bug.cgi?id=9789
and
https://git.samba.org/?p=rsync.git;a=commit;h=2dc2070992c00ea6625031813f2b6c886ddc3ade
you are still using 2.6.9 ? that`s rather old (~ 8yrs?) and may have bugs and
security issues
https://bugzilla.samba.org/show_bug.cgi?id=10941
--- Comment #2 from roland devz...@web.de ---
i think this is a very special use case and adding that as a feature would make
no sense, imho, as rsync shouldn`t be turned into a jack of all trades tool.
what about specifically syncing those files
https://bugzilla.samba.org/show_bug.cgi?id=10756
--- Comment #2 from roland devz...@web.de ---
please provide some more information like type of filesystem , details of your
snapshot-script etc
your rsync commandline looks weird, as there is ), inside.
--
You are receiving this mail because:
https://bugzilla.samba.org/show_bug.cgi?id=10925
--- Comment #1 from roland devz...@web.de ---
interesting find, if btrfs has xattr races, but the question is how to produce
an appropriate repro case.
on a tiny btrfs here on my debian wheezy system, i did some massive parallel
run of
setfattr
https://bugzilla.samba.org/show_bug.cgi?id=10925
--- Comment #2 from roland devz...@web.de ---
it has been resolved already - two days after this report !!!
http://marc.info/?l=linux-btrfsm=141552257121836w=2
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Thanks your reply, after test again, both Fixes bug 9789 and rsync 3.1.0
doesn't resolve this bug.
when the test script was called as background, I still saw rsync hanged
since tdiff variable is used.
could you please try it again?
while [ 1 ]
do
date -s 2012-10-30 06:28:04
date -s
