On Sat, Dec 28, 2013 at 1:01 PM, Emil Karlson <jekarlson@xxxxxxxxx> wrote: > There are also silent content missmatches on some subset of files that > are not linearly written (vm images, databases and such). > > https://bugzilla.kernel.org/show_bug.cgi?id=66941 Can anyone elaborate on this? Emil, your bug report mentions the subvolume journal is different, and not anything about silent content differences on file data (images, databases, etc.) as you mention above. How are they related? Also, how is the journal different on the receive-side? Is it "just" a size/allocation issue, as David commented on the bug report; or is the content actually different? For example, can it still be used to recover the filesystem post-crash? What does "fixed in V2" mean: BTRFSv2 ? Backup by snapshot+send/receive is my primary BTRFS use-case, so I'm curious about details/pitfalls. Regards, Richard > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
