From: Jacek Luczak <difrost.kernel@gmail.com>
To: Jacek Luczak <difrost.kernel@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@sandeen.net>,
LKML <linux-kernel@vger.kernel.org>,
xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [XFS] 2.6.29-rc2: XFS internal error XFS_WANT_CORRUPTED_GOTO
Date: Wed, 21 Jan 2009 10:04:36 +0100 [thread overview]
Message-ID: <4976E524.1050607@gmail.com> (raw)
In-Reply-To: <20090121040512.GK10158@disturbed>
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Jacek Luczak <difrost.kernel@gmail.com>
To: Jacek Luczak <difrost.kernel@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@sandeen.net>,
LKML <linux-kernel@vger.kernel.org>,
xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [XFS] 2.6.29-rc2: XFS internal error XFS_WANT_CORRUPTED_GOTO
Date: Wed, 21 Jan 2009 10:04:36 +0100 [thread overview]
Message-ID: <4976E524.1050607@gmail.com> (raw)
In-Reply-To: <20090121040512.GK10158@disturbed>
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
next prev parent reply other threads:[~2009-01-21 9:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 11:49 [XFS] 2.6.29-rc2: XFS internal error XFS_WANT_CORRUPTED_GOTO Jacek Luczak
2009-01-19 18:44 ` Eric Sandeen
2009-01-19 18:44 ` Eric Sandeen
2009-01-20 0:46 ` Dave Chinner
2009-01-20 0:46 ` Dave Chinner
2009-01-20 9:26 ` Jacek Luczak
2009-01-20 9:26 ` Jacek Luczak
2009-01-20 11:29 ` Christoph Hellwig
2009-01-20 11:29 ` Christoph Hellwig
2009-01-20 11:47 ` Jacek Luczak
2009-01-20 11:47 ` Jacek Luczak
2009-01-20 11:49 ` Christoph Hellwig
2009-01-20 11:49 ` Christoph Hellwig
2009-01-20 12:13 ` Christoph Hellwig
2009-01-20 12:13 ` Christoph Hellwig
2009-01-20 12:45 ` Christoph Hellwig
2009-01-20 12:45 ` Christoph Hellwig
2009-01-20 13:58 ` Jacek Luczak
2009-01-20 13:58 ` Jacek Luczak
2009-01-20 14:05 ` Christoph Hellwig
2009-01-20 14:05 ` Christoph Hellwig
2009-01-20 14:13 ` Jacek Luczak
2009-01-20 14:13 ` Jacek Luczak
2009-01-20 14:23 ` Jacek Luczak
2009-01-20 14:23 ` Jacek Luczak
2009-01-20 14:32 ` Christoph Hellwig
2009-01-20 14:32 ` Christoph Hellwig
2009-01-21 4:05 ` Dave Chinner
2009-01-21 4:05 ` Dave Chinner
2009-01-21 9:04 ` Jacek Luczak [this message]
2009-01-21 9:04 ` Jacek Luczak
2009-01-21 22:58 ` Dave Chinner
2009-01-21 22:58 ` Dave Chinner
2009-01-20 13:35 ` Dave Chinner
2009-01-20 13:35 ` Dave Chinner
2009-01-20 23:03 ` [PATCH] " Dave Chinner
2009-01-20 23:03 ` Dave Chinner
2009-01-20 23:22 ` Christoph Hellwig
2009-01-20 23:22 ` Christoph Hellwig
2009-01-20 9:24 ` Jacek Luczak
2009-01-20 9:24 ` Jacek Luczak
2009-01-20 10:42 ` Jacek Luczak
2009-01-20 10:42 ` Jacek Luczak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4976E524.1050607@gmail.com \
--to=difrost.kernel@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.