From: Andrew Schretter <schrett@math.duke.edu>
To: linux-btrfs@vger.kernel.org
Subject: btrfsck segmentation fault
Date: Fri, 07 Jan 2011 16:15:44 -0500 [thread overview]
Message-ID: <4D278280.4060907@math.duke.edu> (raw)
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.
Running btrfsck with gdb returns :
#0 find_first_block_group (root=0x8067178, path=0x80677f8, key=0xbffff24b) at extent-tree.c:3028
#1 0x08055603 in btrfs_read_block_groups (root=0x8067178) at extent-tree.c:3072
#2 0x08053009 in open_ctree_fd (fp=7, path=0xbffff63a "/dev/sdb", sb_bytenr=<value optimized out>, writes=0) at disk-io.c:760
#3 0x080530e8 in open_ctree (filename=0xbffff63a "/dev/sdb", sb_bytenr=0, writes=0) at disk-io.c:587
#4 0x0804d3fc in main (ac=<value optimized out>, av=Cannot access memory at address 0x4
In any event, recovering the data would be nice and any ideas to do so would be appreciated.
--
Andrew Schretter
Systems Programmer, Duke University
Dept. of Mathematics (919) 660-2866
next reply other threads:[~2011-01-07 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 21:15 Andrew Schretter [this message]
2011-01-07 22:29 ` btrfsck segmentation fault cwillu
2011-01-08 11:42 ` Fajar A. Nugraha
2011-01-09 1:11 ` Justin Chudgar
-- strict thread matches above, loose matches on Subject: below --
2010-01-17 1:27 André Goddard Rosa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D278280.4060907@math.duke.edu \
--to=schrett@math.duke.edu \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).