From: Nathan Scott <nathans@sgi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at fs/direct-io.c:916!
Date: Mon, 27 Mar 2006 16:33:37 +1100 [thread overview]
Message-ID: <20060327053337.GB2481@frodo> (raw)
In-Reply-To: <20060326230358.GG4776@charite.de>
On Mon, Mar 27, 2006 at 01:03:59AM +0200, Ralf Hildebrandt wrote:
> * Nathan Scott <nathans@sgi.com>:
>
> > Hmm, there were XFS patches in -mm last week, but they also got
> > merged to mainline last week, not clear whether your git kernel
> > had those changes or not. I think there's probably some direct
> > I/O (generic) changes in -mm too based on list traffic from the
> > last couple of weeks (I'm an -mm lamer, sorry, couldn't easily
> > tell you exactly what patches those might be) - could you retry
> > with todays git snapshot and see if mainline is affected? Else
> > we'll need to find and analyse any -mm fs/direct-io.c patches.
>
> 2.6.16-git12 also fails utterly:
Could you find the inode number where its failing (fsr -v -d) and
send me the xfs_bmap output for that file - use find -inum to get
from an inum to a path for bmap.
thanks.
--
Nathan
next prev parent reply other threads:[~2006-03-27 5:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 18:04 kernel BUG at fs/direct-io.c:916! Ralf Hildebrandt
2006-03-26 18:46 ` Ralf Hildebrandt
2006-03-26 22:08 ` Nathan Scott
2006-03-26 23:03 ` Ralf Hildebrandt
2006-03-27 5:33 ` Nathan Scott [this message]
[not found] ` <20060327060436.GC2481@frodo>
[not found] ` <20060327110342.GX21946@charite.de>
2006-03-28 5:01 ` Nathan Scott
2006-03-28 11:28 ` Ralf Hildebrandt
2006-03-28 21:43 ` Nathan Scott
2006-03-29 8:35 ` Ralf Hildebrandt
2006-03-28 17:30 ` Badari Pulavarty
2006-03-28 22:23 ` Nathan Scott
2006-03-30 18:42 ` Badari Pulavarty
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=20060327053337.GB2481@frodo \
--to=nathans@sgi.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox