From: Dave Chinner <david@fromorbit.com>
To: Mark Tinguely <tinguely@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v2 2/7] xfs: add support FALLOC_FL_COLLAPSE_RANGE for fallocate
Date: Sat, 31 May 2014 10:39:18 +1000 [thread overview]
Message-ID: <20140531003918.GI14410@dastard> (raw)
In-Reply-To: <538743E0.70103@sgi.com>
On Thu, May 29, 2014 at 09:27:44AM -0500, Mark Tinguely wrote:
> On 05/27/14 19:29, Dave Chinner wrote:
> >On Tue, May 27, 2014 at 05:56:54PM -0500, Mark Tinguely wrote:
> >>A 7-8 hours on spinning rust. This is my burn in test.
> >
> >Can you try to narrow the problem down? Otherwise it's going to be a
> >case of looking for a needle in a haystack....
>
> Nod on the needle in a hay stack if it bmbt is really corrupt.
>
> I am running fsstress from xfstests with the top commit 9b7f704, and
> I don't see any newer fsstress patches since then.
>
> I moved the test to another box with a kdump that works on top of
> tree Linux and grabbed a vmcore. I grabbed a metadata dump of the
> filesystem after the ASSERT. That should give some idea of what
> inode/block it was looking up.
>
> I sent email to Namjae when I first tripped over this problem in
> late April. No longer on the face of the earth and I can't look at
> this until the weekend.
No worries - it looks pretty hard to hit, so it's not something we
urgently need to track down. Any time you can spare to try to narrow
it down would be great!
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:[~2014-05-31 0:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 14:29 [PATCH v2 2/7] xfs: add support FALLOC_FL_COLLAPSE_RANGE for fallocate Namjae Jeon
2014-05-27 22:20 ` Mark Tinguely
2014-05-27 22:51 ` Dave Chinner
2014-05-27 22:56 ` Mark Tinguely
2014-05-28 0:29 ` Dave Chinner
2014-05-28 22:48 ` Dave Chinner
2014-05-29 14:27 ` Mark Tinguely
2014-05-31 0:39 ` Dave Chinner [this message]
2014-06-01 1:22 ` Mark Tinguely
2014-06-01 1:25 ` Mark Tinguely
2014-06-01 22:43 ` Dave Chinner
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=20140531003918.GI14410@dastard \
--to=david@fromorbit.com \
--cc=tinguely@sgi.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