Sigh... failed to reply all... On Mon, Mar 18, 2013 at 11:52 AM, Michael Johnson - MJ <mj@xxxxxxxxx> wrote: > Hi Jan, > > In that configuration, you should assume that a single disk failure > will cause complete data loss. While some data may be recoverable, I > don't believe btrfs gives you any guarantees in that regard. > > But, I have a suggestion for you that may be suitable for what you want. > > * Create 3 individual btrfs file systems, one on each disk. > > * Use 'aufs' to present these filesystems as if they were a single file system. > > I use a setup like this for data I don't consider important, but would > rather not lose it all. This ensures that individual files are always > completely contained on a single disk. It also has the additional > advantage of preventing filesystem corruption from causing total data > loss. > > > On Mon, Mar 18, 2013 at 11:32 AM, Jan Beranek <jan233321@xxxxxxxxx> wrote: >> Hi all, >> I'm preparing a strorage pool for large data with quite low importance >> - there will be at least 3 hdd in "-d single" and "-m raid1" >> configuration. >> >> mkfs.btrfs -d single -m raid1 /dev/sda /dev/sdb /dec/sdc >> >> What happen if one hdd fails? Do I lost everything from all three >> discs or only data from one disc? (if from only one disc, then is it >> acceptable otherwise not...) >> >> I read all documentation and a lot of discussions on the web and >> answer is not clear at all... >> >> Kind Regards >> >> Jan. >> -- >> 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 > > > > -- > Michael Johnson - MJ -- Michael Johnson - MJ -- 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
