xfs
[Top] [All Lists]

Re: kernel BUG in __xfs_get_blocks at fs/xfs/linux-2.6/xfs_aops.c:1293!

To: David Chinner <dgc@xxxxxxx>
Subject: Re: kernel BUG in __xfs_get_blocks at fs/xfs/linux-2.6/xfs_aops.c:1293!
From: Yao Fei Zhu <walkinair@xxxxxxxxxx>
Date: Thu, 31 Aug 2006 16:02:36 +0800
Cc: linux-kernel@xxxxxxxxxxxxxxx, haveblue@xxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <20060831074742.GD807830@xxxxxxxxxxxxxxxxx>
Organization: IBM
References: <44F67847.6030307@xxxxxxxxxx> <20060831074742.GD807830@xxxxxxxxxxxxxxxxx>
Reply-to: walkinair@xxxxxxxxxx
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)
David Chinner wrote:


Hmmmm. We've mapped a range that has been reserved for a delayed
allocate extent during a direct I/O. That should not happen as XFS
flushes delalloc extents before executing a direct read and holds
the I/O lock which will prevent any new writes from mapping new
delalloc extents. Something went astray, though. :(

Can you give me some more detail on the machine you're running?
e.g. How many CPUs, RAM and what type of disk subsystem you are using?
That will make it easier for us to try to reproduce this problem.

Cheers,

Dave.
The test box is an IBM System p5 Linux partition, allocated with
0.8 physical POWER5+ cpu processing unit/ 2 virtual processors and 8GB memory.
The disk is exported by AIX Virtual IO Server.

BTW, I have CONFIG_PPC_64K_PAGES enabled.



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