[Top] [All Lists]

Re: [PATCH v2 2/7] xfs: add support FALLOC_FL_COLLAPSE_RANGE for falloca

To: Mark Tinguely <tinguely@xxxxxxx>
Subject: Re: [PATCH v2 2/7] xfs: add support FALLOC_FL_COLLAPSE_RANGE for fallocate
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Sat, 31 May 2014 10:39:18 +1000
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <538743E0.70103@xxxxxxx>
References: <1378132151-2685-1-git-send-email-linkinjeon@xxxxxxxxx> <53850F92.7010401@xxxxxxx> <20140527225138.GD8554@dastard> <53851836.2070301@xxxxxxx> <20140528002906.GH8554@dastard> <538743E0.70103@xxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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!


Dave Chinner

<Prev in Thread] Current Thread [Next in Thread>