From: Eric Sandeen <sandeen@sandeen.net>
To: Jesse Stroik <jstroik@ssec.wisc.edu>
Cc: xfs@oss.sgi.com
Subject: Re: Seg fault during xfs repair (segmentation fault / segv)
Date: Wed, 01 Jul 2009 15:34:02 -0500 [thread overview]
Message-ID: <4A4BC83A.3080401@sandeen.net> (raw)
In-Reply-To: <4A4BBECC.8000308@sandeen.net>
Eric Sandeen wrote:
> Ok, from a metadump image Jesse provided (thanks!) it's dying in here:
>
> bno = be32_to_cpu(agfl->agfl_bno[i]);
> printf("agfl at %p i is %d agfl_bno[i] %u bno is %u\n",
> agfl, i, agfl->agfl_bno[i], bno);
> if (verify_agbno(mp, be32_to_cpu(agf->agf_seqno), bno))
> set_agbno_state(mp, be32_to_cpu(agf->agf_seqno),
> bno, XR_E_FREE);
>
> agfl_bno looks corrupt, and bno is coming out to be huge.
>
> set_agbno_state() does:
>
> *(ba_bmap[(agno)] + (ag_blockno)/XR_BB_NUM) = ....
>
> where ag_blockno is that bno above; this wanders us off into bad memory
> and boom. I'll see what we can do to fix it up.
Ok patch sent, but now I hit:
junking entry "soh " in directory inode 128
entry ".nsr" in shortform directory 128 references invalid inode 210397
junking entry ".nsr" in directory inode 128
bogus .. inode number (128) in directory inode 128, clearing inode number
xfs_repair: dir2.c:2123: process_dir2: Assertion `(ino !=
mp->m_sb.sb_rootino && ino != *parent) || (ino == mp->m_sb.sb_rootino &&
(ino == *parent || need_root_dotdot == 1))' failed.
Aborted
that's one crunchy filesystem you've got there; what happened to it?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-01 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 18:29 Seg fault during xfs repair (segmentation fault / segv) Jesse Stroik
2009-06-30 18:41 ` Eric Sandeen
2009-06-30 21:01 ` Jesse Stroik
2009-06-30 21:11 ` Eric Sandeen
2009-07-01 19:53 ` Eric Sandeen
2009-07-01 20:34 ` Eric Sandeen [this message]
2009-07-01 20:51 ` Jesse Stroik
2009-07-01 20:52 ` Eric Sandeen
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=4A4BC83A.3080401@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jstroik@ssec.wisc.edu \
--cc=xfs@oss.sgi.com \
/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