On Sat, Jan 8, 2011 at 5:29 AM, cwillu <cwi...@cwillu.com> wrote: > On Fri, Jan 7, 2011 at 3:15 PM, Andrew Schretter <schr...@math.duke.edu> > wrote: >> I have a 10TB btrfs filesystem over iSCSI that is currently unmountable. I'm >> currently running Fedora 13 with a recent Fedora 14 kernel >> (2.6.35.9-64.fc14.i686.PAE) >> and the system hung with messages like : >> >> parent transid verify failed on 5937615339520 wanted 48547 found 48542 >> >> I've rebooted and and am attempting to recover with btrfsck from the >> btrfs-progs-unstable >> git tree, but it is segfaulting after finding a superblock and listing out 3 >> of the >> "parent transid" messages. Anyone have any ideas? >> >> I tried btrfsck /dev/sdb, btrfsck -s 1 /dev/sdb, and btrfsck -s 2 /dev/sdb >> with the >> same result for each. The btrfsck binary I compiled does work on a small >> (800MB) test >> btrfs file system. I suspect it may be due to the size of the filesystem I >> am trying >> to repair. > > Segfaulting is what the current btrfsck does when it finds a problem; > it doesn't try to fix anything yet.
Is there something we can do to fix this particular problem (e.g. editing the metadata manually to use older transaction group), or is this one of those forhet-in-you're-screwed kind of thing? -- Fajar -- 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
