xfs
[Top] [All Lists]

Re: xfs bug in 2.6.26-rc9

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: xfs bug in 2.6.26-rc9
From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Date: Fri, 11 Jul 2008 12:21:56 +0200 (CEST)
Cc: linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <20080711084248.GU29319@disturbed>
Organization: People's Front Against WWW
References: <alpine.DEB.1.10.0807110939520.30192@xxxxxxxxxxxxxxxx> <20080711084248.GU29319@disturbed>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Alpine 1.10 (DEB 962 2008-03-14)
On Fri, 11 Jul 2008, Dave Chinner wrote:

That aside, what was the assert failure reported prior to the oops? i.e. paste the lines in the log before the ---[ cut here ]--- line? One of them will start with 'Assertion failed:', I think....

These ones?

Jul  8 04:44:56 via kernel: [554197.888008] Assertion failed: whichfork == 
XFS_ATTR_FORK || ip->i_delayed_blks == 0, file: fs/xfs/xfs_bmap.c, line: 5879
Jul  9 03:25:21 via kernel: [42940.748007] Assertion failed: whichfork == 
XFS_ATTR_FORK || ip->i_delayed_blks == 0, file: fs/xfs/xfs_bmap.c, line: 5879

I'll happily rebuild the kernel without the debug option and do xfs_check to weed out any possible logical problem with the volume, if you don't need any further information from the current state of my volume.

I should also say that this assert failue happened two nights in a row so I guess it's fairly reproducible (didn't happen on the 10th, and today, the 11th it seems to have panic:ed around 03:30 (I start the defragmentation via cron at 03:00) which I think is related.

--
Mikael Abrahamsson    email: swmike@xxxxxxxxx


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