From: Christoph Hellwig <hch@infradead.org>
To: Bartosz Cisek <bartosz.cisek@nasza-klasa.pl>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>, xfs@oss.sgi.com
Subject: Re: xfs_repair segfaut in stage 6
Date: Mon, 12 Sep 2011 11:58:38 -0400 [thread overview]
Message-ID: <20110912155838.GA14744@infradead.org> (raw)
In-Reply-To: <4E6E285A.5090905@nasza-klasa.pl>
On Mon, Sep 12, 2011 at 05:42:18PM +0200, Bartosz Cisek wrote:
> W dniu 09.09.2011 17:06, Bartosz Cisek pisze:
>
> >> Can you provide a metadump of that partition? By this, the devs can
> >> reproduce the bug on their machine, and resolve issues much quicker.
> >
> > xfs_metadump -g /dev/cciss/c0d5p1 - | bzip2 > metadump.bz2
> >
> > http://bartoszcisek.pl/metadump.bz2
>
> Is there anything more I can get from failed partition to help solving
> this bug? Or it can be safely recreated?
Sorry for not replying earlier Bart. I'm downloading the metadump image
now and will look at it.
Do you still have the kernel logs from when the issue happened?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-09-12 15:58 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 [this message]
2011-09-12 16:12 ` Christoph Hellwig
2011-09-14 9:38 ` Bartosz Cisek
2011-09-14 14:24 ` Christoph Hellwig
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=20110912155838.GA14744@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