Filipe David Manana posted on Fri, 22 Aug 2014 10:58:33 +0100 as excerpted:
> On Fri, Aug 22, 2014 at 8:35 AM, Duncan <1i5t5.dun...@cox.net> wrote: >> Konstantinos Skarlatos posted on Fri, 22 Aug 2014 09:56:55 +0300 as >> excerpted: >> >>> I would stay with rsync for a while, because there is always the >>> possibility of a bug [...] (Or maybe I am too paranoid[)] >> >> I believe in this case you /are/ "being too paranoid." >> >> Both btrfs send and receive only deal with data/metadata they know how >> to deal with. If it's corrupt in some way or if they don't understand >> it, they don't send/write it, they fail. > > Most of the time yes, however we have at least 1 know bug that affects > 3.14.x only where send silently corrupts file data (replaces valid data > with zeroes) at the destination: > > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/ commit/?id=766b5e5ae78dd04a93a275690a49e23d7dcb1f39 > > The fix landed in 3.15, but wasn't backported to 3.14.x yet (adding > Chris to cc). > > >> IOW, if it works without error it's as guaranteed to be golden as these >> things get. Well, I /did/ say "as golden as these things get". With even long stable subsystems such as mdraid having occasional data-risking bugs, and with btrfs in general not yet fully stable/mature... But point taken. That bug flew under my radar. Thanks for mentioning it. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
