https://bugzilla.samba.org/show_bug.cgi?id=10925
--- Comment #3 from Alexandre Oliva <ol...@gnu.org> --- Yeah, the btrfs bug is now fixed, so now the rsync --read-batch misbehavior changed from bad error reports to silent waste of cpu cycles: it doesn't make sense for rsync to test and set xattrs concurrently on the same files: it should either test them in the scanner process BEFORE telling the changer process whether xattr changes need to be applied in the first place, OR it should check them AFTER the changer has made the changes. As it stands, the check is wasteful: it is either ignored altogether, or it may see xattrs before they are changed and conclude the changes have to be made again. Either way, we waste cpu cycles, syscalls, and even disk space, if we modify a copy-on-write snapshot overwriting xattrs with the values they already have, unnecessarily touching inodes' ctimes in the process. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
