[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4976E524.1050607@gmail.com>
Date: Wed, 21 Jan 2009 10:04:36 +0100
From: Jacek Luczak <difrost.kernel@...il.com>
To: Jacek Luczak <difrost.kernel@...il.com>,
Christoph Hellwig <hch@...radead.org>,
Eric Sandeen <sandeen@...deen.net>,
LKML <linux-kernel@...r.kernel.org>,
xfs mailing list <xfs@....sgi.com>
Subject: Re: [XFS] 2.6.29-rc2: XFS internal error XFS_WANT_CORRUPTED_GOTO
Dave Chinner pisze:
> On Tue, Jan 20, 2009 at 03:23:01PM +0100, Jacek Luczak wrote:
>> Christoph Hellwig pisze:
>>> On Tue, Jan 20, 2009 at 02:58:35PM +0100, Jacek Luczak wrote:
>>>> Good job! Is there some ,,quick'' fix?
>>> The patch below makes it go away for me, alternatively just enable
>>> CONFIG_LBD.
>>>
>>>
>>> Index: linux-2.6/fs/xfs/xfs_types.h
>>> ===================================================================
>>> --- linux-2.6.orig/fs/xfs/xfs_types.h 2009-01-20 14:55:55.806068213 +0100
>>> +++ linux-2.6/fs/xfs/xfs_types.h 2009-01-20 14:56:01.437945154 +0100
>>> @@ -96,7 +96,7 @@ typedef __uint64_t xfs_dfilblks_t; /* nu
>>> /*
>>> * Memory based types are conditional.
>>> */
>>> -#if XFS_BIG_BLKNOS
>>> +#if 1 //XFS_BIG_BLKNOS
>>> typedef __uint64_t xfs_fsblock_t; /* blockno in filesystem (agno|agbno) */
>>> typedef __uint64_t xfs_rfsblock_t; /* blockno in filesystem (raw) */
>>> typedef __uint64_t xfs_rtblock_t; /* extent (block) in realtime area */
>>>
>> I've applied it and now running ,,fixed'' kernel. What I've notice is:
>> $ LC_ALL=C df -h
>> Filesystem Size Used Avail Use% Mounted on
>> /dev/sda1 20G -40E 40E - /
>> /dev/sda5 20G -23E 23E - /home
>> /dev/sda6 56G 56G 774M 99% /NORA
>> /dev/sda7 45G 44G 1.2G 98% /MAGAZYN
>
> Please try the patch I posted this morning - it fixes the problem
> properly and shouldn't have this side effect.
>
Your patch work for me. I've made also some tests a'la one proposed by
Christoph, here also everything works. Good work guys!
Have a nice day,
-Jacek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists