xfs
[Top] [All Lists]

Re: oops with CentOS 4.3 / xfs / nfsd

To: Andrew Elwell <andrewe@xxxxxxxxxxxxx>
Subject: Re: oops with CentOS 4.3 / xfs / nfsd
From: Nathan Scott <nathans@xxxxxxx>
Date: Wed, 19 Jul 2006 08:30:14 +1000
Cc: xfs@xxxxxxxxxxx, maciej@xxxxxxxxxxxxx
In-reply-to: <1153214961.6793.15.camel@x41ade>; from andrewe@xxxxxxxxxxxxx on Tue, Jul 18, 2006 at 10:29:21AM +0100
References: <1153214961.6793.15.camel@x41ade>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Tue, Jul 18, 2006 at 10:29:21AM +0100, Andrew Elwell wrote:
> Hi Folks,
> 
> We've migrated some of our storage servers to CentOS 4.3 and are seeing
> lockups. It *could* be hardware I know, and I'm scheduling downtime to
> run memtest86+ ASAP.
> ...
>  IP 172.20.0.224
> SysRq : HELP : loglevel0-8 reBoot Crash tErm kIll saK showMem powerOff showPc 
> unRaw Sync showTasks Unmount shoWcpus 
> nfsd: page allocation failure. order:4, mode:0x50

This is very likely to be due to the way older versions of XFS
managed incore inode extent lists.  So, you've likely got a very
fragmented file/files here, and XFS used to require large amounts
of contiguous memory to deal with that.  Your options are to take
steps to combat inode extent fragmentation (like fsr), or use a
more recent kernel (2.6.17+ IIRC).

Oh yes, and like Joshua said, those old kernels also had 4Kstack
related issues.

cheers.

-- 
Nathan


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