On Wed, Oct 07, 2009 at 03:51:46PM +0200, Diego Calleja wrote: > On Wednesday 07 October 2009 05:17:54 Chris Mason escribió: > > > Thanks, I'll try to reproduce. Which raid level did you use for data? > > If not raid1, could you try with raid1? ;) > > I'm not sure, since the utils won't tell. I mkfs'ed and mounted one of the > 3.5GB > files with no special options, and copied some files on it. I mkfs'ed the > second > file, put it in a loop device, and added it to the pool with btrfs-vol -a. > Then > I run btrfs-vol -b and I copied more files and rebalanced several times. > > Then I zeroed one of the files used as disks, and tried to read the files in > the volume (unsucessfully). Then I rebalanced, and I hit the oops. It seems to > be very reproducible.
Ok, in this case you ended up with raid0 on the data. If you: mkfs.btrfs -d raid1 /dev/loop0 /dev/loop1 you'll get data raid1. -chris -- 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
