From: David Chinner <dgc@sgi.com>
To: Yao Fei Zhu <walkinair@cn.ibm.com>
Cc: David Chinner <dgc@sgi.com>,
linux-kernel@vger.kernel.org, haveblue@us.ibm.com,
xfs@oss.sgi.com
Subject: Re: kernel BUG in __xfs_get_blocks at fs/xfs/linux-2.6/xfs_aops.c:1293!
Date: Thu, 31 Aug 2006 18:17:26 +1000 [thread overview]
Message-ID: <20060831081726.GV5737019@melbourne.sgi.com> (raw)
In-Reply-To: <44F6979C.4070309@cn.ibm.com>
On Thu, Aug 31, 2006 at 04:02:36PM +0800, Yao Fei Zhu wrote:
> 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.
>
> 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.
Nothing too unusual there.
> BTW, I have CONFIG_PPC_64K_PAGES enabled.
But that might be a good place to start. Can you see if you can
reproduce the problem without this config option set?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2006-08-31 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 5:48 kernel BUG in __xfs_get_blocks at fs/xfs/linux-2.6/xfs_aops.c:1293! Yao Fei Zhu
2006-08-31 7:47 ` David Chinner
2006-08-31 8:02 ` Yao Fei Zhu
2006-08-31 8:17 ` David Chinner [this message]
2006-08-31 8:54 ` Andrew Morton
2006-09-01 3:43 ` Yao Fei Zhu
2006-09-01 6:34 ` Yao Fei Zhu
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=20060831081726.GV5737019@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=walkinair@cn.ibm.com \
--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.