From: Jeremy Sanders <jeremy@jeremysanders.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@oss.sgi.com
Subject: Re: bug in fs/xfs/xfs_aops.c:959! (kernel 3.1.5)
Date: Thu, 29 Dec 2011 11:07:17 +0000 [thread overview]
Message-ID: <4EFC49E5.7050200@jeremysanders.net> (raw)
In-Reply-To: <20111228171643.GA18895@infradead.org>
On 28/12/11 17:16, Christoph Hellwig wrote:
> Something must have set the page dirty without going through the normal
> XFS codepath. Did you use any interesting virtualization things, or
> utrace / systemtap or anything odd?
This is plain hardware running a Fedora 16 standard x86-64 kernel. The
hardware has been fine running F14 a long time for a few years, though I
got the same error when I tried to run a rebuilt F15 kernel on F14
(2.6.38.8). See http://oss.sgi.com/archives/xfs/2011-07/msg00310.html
The problem happened very soon on upgrading from F14->F16.
Jeremy
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-12-29 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 9:36 bug in fs/xfs/xfs_aops.c:959! (kernel 3.1.5) Jeremy Sanders
2011-12-19 22:11 ` Dave Chinner
2011-12-20 9:54 ` Jeremy Sanders
2011-12-28 17:16 ` Christoph Hellwig
2011-12-29 11:07 ` Jeremy Sanders [this message]
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=4EFC49E5.7050200@jeremysanders.net \
--to=jeremy@jeremysanders.net \
--cc=hch@infradead.org \
--cc=linux-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox