On 03/10/2013 10:45 PM, Harald Glatt wrote: > I've noticed through my own tests that on a single device I can > corrupt around 5% of the data completely before btrfs fails. Up to > that point both filesystem as well as data integrity stays at 100%. > However the default layout for one disk seems to be having the data > once, the metadata DUP and the system DUP too.
How make you the corruption ? Does btrfs return wrong data ? How is calculated the 5% ? > Having these 5% isn't > mentioned anywhere... Is this a value that could maybe be manipulated > and could it be introduced into a naming scheme like this? Also where > do the 5% redundancy come from? On a single device, the metadata are DUPlicated but the data have only 1 copy. This means that if you corrupt the 1 copy of the metadata, btrfs survives using the other copy. Instead if you corrupt the data btrfs return an error. > -- > 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 > -- gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5 -- 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
