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!