---------- Forwarded message ---------- From: Imran Geriskovan <imran.geriskovan@xxxxxxxxx> Date: Wed, 11 Dec 2013 02:14:25 +0200 Subject: Re: Feature Req: "mkfs.btrfs -d dup" option on single device To: Chris Murphy <lists@xxxxxxxxxxxxxxxxx> > Current btrfs-progs is v3.12. 0.19 is a bit old. But yes, looks like the > wiki also needs updating. > Anyway I just tried it on an 8GB stick and it works, but -M (mixed > data+metadata) is required, which documentation also says incurs a > performance hit, although I'm uncertain of the significance. btrfs-tools 0.19+20130705 is the most recent one on Debian's leading edge Sid/Unstable. Given the state of the docs probably very few or no people ever used '-d dup'. As being the lead developer, is it possible for you to provide some insights for the reliability of this option? Can '-M' requirement be an indication of code which has not been ironed out, or is it simply a constraint of the internal machinery? How well does the main idea of "Guaranteed Data Integrity for extra reliability" and the option "-d dup" in its current state match? Regards, Imran -- 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
