From: Christoph Hellwig <hch@infradead.org>
To: Simon Kirby <sim@hostway.ca>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [2.6.30.4] XFS-related BUG and hang via shrink_icache_memory
Date: Tue, 25 Aug 2009 21:15:32 -0400 [thread overview]
Message-ID: <20090826011532.GA24362@infradead.org> (raw)
In-Reply-To: <20090826004658.GA30929@hostway.ca>
On Tue, Aug 25, 2009 at 05:46:58PM -0700, Simon Kirby wrote:
> On an NFS storage server, we started using some XFS filesystems along
> with many other EXT3 (on LVM on AOE). The following bug has occurred
> twice, with the machine hanging immediately after (console full of
> scrolling oopses or bugs -- haven't seen it myself -- after this):
Known and fortunately fixed bug, get the patches to fix it from:
http://bugzilla.kernel.org/attachment.cgi?id=22741
It should also be included in the next upcoming 2.6.30-stable release.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-08-26 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 0:46 [2.6.30.4] XFS-related BUG and hang via shrink_icache_memory Simon Kirby
2009-08-26 1:15 ` Christoph Hellwig [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=20090826011532.GA24362@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sim@hostway.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox