From: Dave Chinner <david@fromorbit.com>
To: Robert Jacobs <debbtsb06@eamp.org>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>, xfs@oss.sgi.com
Subject: Re: Bug#638158: xfsprogs: Damaged filesystem causes xfs_repair to sometimes (but not always) segfault
Date: Mon, 22 Aug 2011 11:27:05 +1000 [thread overview]
Message-ID: <20110822012705.GC3162@dastard> (raw)
In-Reply-To: <E1QvGzO-0001aI-4l@eamp.org>
On Sun, Aug 21, 2011 at 03:59:34PM -0700, Robert Jacobs wrote:
> > On Mittwoch, 17. August 2011 Robert Jacobs wrote:
> > > I've attached the outputs of xfs_check and three different runs of
> > > xfs_repair (with backtrace, when available).
> >
> > Can you provide a XFS metadump? That should help devs to reproduce the
> > error.
>
> I've uploaded it to <http://eamp.org/metadumpf.lzma>. It's 9MB but I
> have somewhat limited upload quota. I noticed that some filenames
> weren't obscured so I obscured them by hand -- if this is a problem,
> please tell me.
The metadump image you have provided does not trigger problems on
either 3.1.5 on a current xfs_repair build out of the xfsprogs-dev
repository on my machines. Can you restore the image and run
xfs_repair on the image and confirm it still crashes?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-08-22 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 8:22 Bug#638158: xfsprogs: Damaged filesystem causes xfs_repair to sometimes (but not always) segfault Robert Jacobs
2011-08-17 13:18 ` Michael Monnerie
2011-08-21 22:59 ` Robert Jacobs
2011-08-22 1:27 ` Dave Chinner [this message]
2011-08-22 3:28 ` Dave Chinner
2011-08-22 7:04 ` Robert Jacobs
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=20110822012705.GC3162@dastard \
--to=david@fromorbit.com \
--cc=debbtsb06@eamp.org \
--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 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.