On 11 Jul 2010, at 17:43, Chris Mason wrote: > Was this after a fresh mkfs? Clearly things are very corrupt on this > original drive. It would be a good test case for Yan Zhengs new fsck > code, but first I'd like to figure out if you're still seeing the old > corruption of if you've started over. nope, same disk as before when the btrfsck exited with: btrfsck: disk-io.c:410: find_and_setup_root: Assertion `!(ret)' failed. the strange thing was that i'm pretty sure that btrfs crashed the system a couple of times (hung). after reboot the mounted drive would basically churn away for hours and spit out lots of the parent transid messages. but after a while it stops and everything seems fine again. i don't mind losing files on the disk array, but it would be nice if it could tell me the actual filenames which are corrupt. Yee.-- 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
