xfs
[Top] [All Lists]

Re: Strange df output

To: Jarrod Johnson <jbj-ksylph@xxxxxxxxxxxxxxxx>
Subject: Re: Strange df output
From: "Net Llama!" <netllama@xxxxxxxxxxxxx>
Date: Sat, 17 Jan 2004 07:04:41 -0800
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20040117091614.7d172889.jbj-ksylph@ken-ohki>
Organization: HAL III
References: <20040108154940.7dd28591.jbj-ksylph@ken-ohki> <1073595887.27384.260.camel@stout.americas.sgi.com> <20040117091614.7d172889.jbj-ksylph@ken-ohki>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031125
On 01/17/04 06:16, Jarrod Johnson wrote:

Unfortunately, this was first created ~1.5 years ago, so I have no mkfs 
arguments, I assume the default from whatever it was back then.  I've gone 
since to kernel 2.4.23 with the snapshot for download applied, and it was about 
then I started noticing this behavior.  The system crashed at one point listing 
about ~4G free, but on reboot the system had 0 free.

I tried to run xfs_check on it, but xfs_check is killed partway through, kernel 
prints:
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
VM: killing process xfs_db

I might be wrong, but isn't that what the kernel spits out when the box is running out of memory (and swap)? THat looks exactly like the non-OOM killer message to me.


--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                                    netllama@xxxxxxxxxxxxx
Linux Step-by-step & TyGeMo:                    http://netllama.ipfox.com

 07:00:01  up 41 days, 11:45,  1 user,  load average: 0.13, 0.08, 0.02


<Prev in Thread] Current Thread [Next in Thread>