From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Nathan Scott <nathans@sgi.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>, linux-xfs@oss.sgi.com
Subject: Re: xfs corruption or not
Date: Mon, 07 Jun 2004 04:39:20 -0600 [thread overview]
Message-ID: <40C445D8.80804@cornell.edu> (raw)
In-Reply-To: <20040604052953.GE13756@frodo>
> Do you know if the kernel was low on memory at the time? (any
> signs of allocation failures in your system log?)
>
> This looks like a memory allocation failure which hasn't been
> gracefully handled (or approriately retried) in XFS - there's
> a few patches being worked on to improve this, but they aren't
> ready to be merged in just yet.
---
Well, now that you mention it, there's another trace right in front of
the oops. Don't know why I missed it - probably thought it was the same
thing. It says allocation failure. I am running FC2 with 128MB SDRAM.
----
(Trace in previous message in thread)
I think this is caused by working with a 385 MB LKML archive file when
low on memory (basically all the time..) I can't ls -l that particular
folder after t-bird locks up, since ls locks up too and becomes unkillable.
prev parent reply other threads:[~2004-06-07 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 2:14 xfs corruption or not Ivan Gyurdiev
2004-06-04 5:29 ` Nathan Scott
2004-06-04 6:39 ` Ivan Gyurdiev
2004-06-07 10:39 ` Ivan Gyurdiev [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=40C445D8.80804@cornell.edu \
--to=ivg2@cornell.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@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