From: Eric Sandeen <sandeen@sandeen.net>
To: Marc Lehmann <schmorp@schmorp.de>
Cc: xfs@oss.sgi.com
Subject: Re: corruption, xfs_repair 3.1.4 segfaults
Date: Fri, 04 Mar 2011 09:07:09 -0600 [thread overview]
Message-ID: <4D71001D.2040506@sandeen.net> (raw)
In-Reply-To: <20110302175818.GA8290@schmorp.de>
On 3/2/11 11:58 AM, Marc Lehmann wrote:
> Hi!
>
> I had a case of filesystem corruption a day ago:
>
...
> I tried to use xfs_repair on it, but it crashes (and, as I may grudgingly
> add, as usual it crashes because thats what xfsrepair does almost always).
If you provide an xfs_metadump image of the filesystem, I'd be
happy to look into the cause of the segfault.
In my experience xfs_repair does not almost always crash, if you
encounter this, please do send mail/file bugs/provide images.
> Any idea on where to go from here? I tried to build the git xfsprogs, but
> they don't build due to missing -fPIC - and as usual, thanks for any help :)
Bug reports on build problems are welcome as well.
Thanks,
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-03-04 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 17:58 corruption, xfs_repair 3.1.4 segfaults Marc Lehmann
2011-03-02 21:43 ` Emmanuel Florac
2011-03-04 7:11 ` Marc Lehmann
2011-03-04 7:51 ` Emmanuel Florac
2011-03-04 10:29 ` Marc Lehmann
2011-03-04 11:14 ` Emmanuel Florac
2011-03-04 16:31 ` Marc Lehmann
2011-03-04 19:18 ` Eric Sandeen
2011-03-04 17:30 ` corruption, xfs_repair 3.1.4 segfaults, xfs_repair 2.9.8 works Marc Lehmann
2011-03-04 18:17 ` Emmanuel Florac
2011-03-04 15:07 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-02 17:57 corruption, xfs_repair 3.1.4 segfaults Marc Lehmann
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=4D71001D.2040506@sandeen.net \
--to=sandeen@sandeen.net \
--cc=schmorp@schmorp.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.