From: Christoph Hellwig <hch@infradead.org>
To: Bartosz Cisek <bartosz.cisek@nasza-klasa.pl>
Cc: Christoph Hellwig <hch@infradead.org>,
Michael Monnerie <michael.monnerie@is.it-management.at>,
xfs@oss.sgi.com
Subject: Re: xfs_repair segfaut in stage 6
Date: Wed, 14 Sep 2011 10:24:30 -0400 [thread overview]
Message-ID: <20110914142430.GA28049@infradead.org> (raw)
In-Reply-To: <4E707624.9030703@nasza-klasa.pl>
On Wed, Sep 14, 2011 at 11:38:44AM +0200, Bartosz Cisek wrote:
> W dniu 12.09.2011 18:12, Christoph Hellwig pisze:
> > I've repaired the image fine using xfs_repair from the Debian testing
> > xfsprogs 3.1.5+nmu1 package. It found two invalid blocks in a
> > directory, which look like the result from the hardware error you saw.
> >
> > You should be able to just rebuild the current xfsprogs (from
> > testing/unstable or git) on Lenny and get the same result.
>
> I've build xfs_repair from git on lenny and got segfault before my first
> email to this list (please refer to first email in this thread) :)
Ooops.
> What else I can do to find what differ our two cases?
The hardware? Given that you were getting read I/O errors from the
hardware when shutting the fs down you probably got those as well when
running repair and that caused the segfault. Can you run xfs_repair
under gdb for me, that is:
gdb /path/to.xfs_repair
(gdb) set args /dev/cciss/c0d5p1
(gdb) run
and see what backtrace it gives you?
Please make sure to build xfs_repair in the git tree manually using
make and not the Debian packaging, as that removes the debug symbols.
You can run gdb on the xfs_repair binary just built in the tree, no
need to install it first.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-09-14 14:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 8:43 xfs_repair segfaut in stage 6 Bartosz Cisek
2011-09-09 12:01 ` Michael Monnerie
2011-09-09 15:06 ` Bartosz Cisek
2011-09-12 15:42 ` Bartosz Cisek
2011-09-12 15:58 ` Christoph Hellwig
2011-09-12 16:12 ` Christoph Hellwig
2011-09-14 9:38 ` Bartosz Cisek
2011-09-14 14:24 ` Christoph Hellwig [this message]
2011-09-14 14:57 ` Eric Sandeen
2011-09-14 15:10 ` Bartosz Cisek
2011-09-14 15:23 ` Eric Sandeen
2011-09-14 14:59 ` Bartosz Cisek
2011-09-14 15:38 ` Christoph Hellwig
2011-09-14 16:05 ` Bartosz Cisek
2011-09-20 20:25 ` Alex Elder
2011-09-20 20:28 ` Christoph Hellwig
2011-09-09 12:38 ` Christoph Hellwig
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=20110914142430.GA28049@infradead.org \
--to=hch@infradead.org \
--cc=bartosz.cisek@nasza-klasa.pl \
--cc=michael.monnerie@is.it-management.at \
--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