xfs
[Top] [All Lists]

Re: xfs corruption or not

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: xfs corruption or not
From: Ivan Gyurdiev <ivg2@xxxxxxxxxxx>
Date: Mon, 07 Jun 2004 04:39:20 -0600
Cc: Linux-Kernel <linux-kernel@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <20040604052953.GE13756@frodo>
References: <40BFDB13.7000901@cornell.edu> <20040604052953.GE13756@frodo>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.6 (X11/20040519)

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 in Thread] Current Thread [Next in Thread>