From: Christoph Hellwig <hch@infradead.org>
To: Claas Langbehn <claas@rootdir.de>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: XFS forced shutdown with kernel 2.6.0
Date: Fri, 2 Jan 2004 18:29:21 +0000 [thread overview]
Message-ID: <20040102182921.A27237@infradead.org> (raw)
In-Reply-To: <20040102095051.GA19872@rootdir.de>; from claas@rootdir.de on Fri, Jan 02, 2004 at 10:50:51AM +0100
On Fri, Jan 02, 2004 at 10:50:51AM +0100, Claas Langbehn wrote:
> Hello!
>
>
> Last night one of my machines running xfs shut down my /homes partition.
>
> That machine was running Azureus (a bittorrent client) with probably
> high memory usage.
>
> But even if the memory usage of one program is going near to 100% it
> should not force the filesystem to shutdown. Instead it should crash
> the application.
>
> I could also think of bad memory, but we did test the SDRAM modules
> only a week ago, and they passed memtest86.
>
> After rebooting everything was working fine, again.
>
> So, is this a bug of xfs?
I've seen the same bug a few times lately, but only if I had previous
memory corruption due to code I was hacking on. Can you reproduce it
without the nvidia module loaded as that is likely source of such
corruption?
next prev parent reply other threads:[~2004-01-02 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 9:50 XFS forced shutdown with kernel 2.6.0 Claas Langbehn
2004-01-02 18:29 ` Christoph Hellwig [this message]
2004-01-02 20:27 ` Valdis.Kletnieks
2004-01-02 20:35 ` Christoph Hellwig
[not found] ` <04a601c415a5$0513b020$d100000a@sbs2003.local>
2004-03-29 16:05 ` Christoph Hellwig
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=20040102182921.A27237@infradead.org \
--to=hch@infradead.org \
--cc=claas@rootdir.de \
--cc=linux-kernel@vger.kernel.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 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.