On Mon, Mar 04, 2013 at 07:06:05AM -0700, Joeri Vanthienen wrote: > Some more maybe usefull information. After reboot, the btrfs raid10 > filesystem is unmountable. > I'm now running the test without enhanceIO from IO. > > linux-testsan:~ #btrfs device scan --all-devices > [ 881.520686] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid > 2 transid 10 /dev/sdd > [ 881.522907] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid > 1 transid 14 /dev/sdc > [ 901.949559] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid > 4 transid 14 /dev/sdf > [ 901.949962] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid > 3 transid 14 /dev/sde > [ 901.950367] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid > 2 transid 10 /dev/sdd > [ 901.952572] device fsid 21b0cd45-019d-4e83-bf2f-053eaaf8b380 devid > 1 transid 14 /dev/sdc > linux-testsan:~ # btrfsck /dev/sde > Check tree block failed, want=858902528, have=858836992 This is telling us the device returned the wrong block. It could be because the device really read from the wrong place, or perhaps it is because the correct block was never written. Please let us know if you're still seeing this without enhanceIO involved. I haven't tried enhanceIO yet, so I'm not sure how well it supports btrfs. -chris -- 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
