[Top] [All Lists]

Re: Problems with kernel 3.6.x (vm ?) (was : Is kernel 3.6.1 or filestre

To: linux-xfs@xxxxxxxxxxx
Subject: Re: Problems with kernel 3.6.x (vm ?) (was : Is kernel 3.6.1 or filestreams option toxic ?)
From: Gaudenz Steinlin <gaudenz@xxxxxxxxxxxxx>
Date: Wed, 31 Oct 2012 11:45:12 +0000 (UTC)
References: <508554AF.5050005@xxxxxxxxxxxxxx> <50865453.5080708@xxxxxxxxxxxxxx> <508958FF.4000007@xxxxxxxxxxxxxx> <20121025211047.GD29378@dastard> <508A600C.1020109@xxxxxxxxxxxxxx> <508B092E.6070209@xxxxxxxxxxxxxx> <20121028234802.GE4353@dastard> <20121029012540.GO29378@dastard> <20121029121851.GQ29378@dastard> <508E79D4.5090507@xxxxxxxxxxxxxx> <20121030013309.GX29378@dastard>
User-agent: Loom/3.14 (http://gmane.org/)

Dave Chinner <david <at> fromorbit.com> writes:

> On Mon, Oct 29, 2012 at 01:43:00PM +0100, Yann Dupont wrote:
> > Le 29/10/2012 13:18, Dave Chinner a écrit :
> > OK, very glad to hear you were able to reproduce it.
> > Good luck, and now let the chase begin :)
> Not really a huge chase, just a simple matter of isolation. The
> patch below should fix the problem.

I ran into the same bug this morning with my home partition after a crash on
suspend to ram. I can confirm that the patch posted to the list by Dave fixes
the problem. I have a backup of the raw log and the whole filesystem if you need
it for further investigation.

BTW: Is this fix already sent upstream? I could not find it anywhere. But then
it may just not be there yet.


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