From: Eric Sandeen <sandeen@sandeen.net>
To: Richard Kolkovich <richard@intrameta.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Segmentation fault during xfs_repair
Date: Fri, 05 Jun 2009 22:25:21 -0500 [thread overview]
Message-ID: <4A29E1A1.1010202@sandeen.net> (raw)
In-Reply-To: <20090606031445.GB39825@magus.portal.sigil.org>
Richard Kolkovich wrote:
> On Fri, Jun 05, 2009 at 10:45:37PM -0400, Eric Sandeen wrote:
>> Richard Kolkovich wrote:
>>> We have a corrupted XFS partition on a storage server.
>>> Attempting to run xfs_repair the first time yielded the message
>>> about a corrupt log file, so I have run xfs_repair with -L to
>>> clear that. Now, xfs_repair segfaults in Phase 3. I have tried
>>> -P and a huge -m to no avail. It always seems to segfault at the
>>> same point:
>>>
>>> bad directory block magic # 0 in block 11 for directory inode
>>> 341521797 corrupt block 11 in directory inode 341521797 will junk
>>> block Segmentation fault (core dumped)
>> For starters, which xfsprogs version.... if not latest, try
>> latest... if latest, I'll grab that metadump image and see if I can
>> reproduce it.
>>
>> -Eric
>
> Sorry - forgot to mention that.
>
> Running on Fedora 11 (64bit). Tried using 2.10.2 (from yum) and
> building from latest stable source (3.0.1). Let me know if I should
> try a dev build.
(Hm, did I really leave F11 at 2.10.2? I thought it was newer, but anyway)
No, I doubt anything else has fixed this since 3.0.1
I'll try pulling down that metadump image & see what I can see.
Feel free to file an xfsprogs bug with fedora, too, so the issue doesn't
get lost...
-Eric
> Thanks,
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-06 3:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 22:22 Segmentation fault during xfs_repair Richard Kolkovich
2009-06-06 2:45 ` Eric Sandeen
2009-06-06 3:14 ` Richard Kolkovich
2009-06-06 3:25 ` Eric Sandeen [this message]
2009-06-06 4:44 ` Eric Sandeen
2009-06-06 5:10 ` 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=4A29E1A1.1010202@sandeen.net \
--to=sandeen@sandeen.net \
--cc=richard@intrameta.com \
--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