xfs
[Top] [All Lists]

Re: oops with CentOS 4.3 / xfs / nfsd

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: oops with CentOS 4.3 / xfs / nfsd
From: Andrew Elwell <andrewe@xxxxxxxxxxxxx>
Date: Wed, 19 Jul 2006 08:37:28 +0100
Cc: xfs@xxxxxxxxxxx, maciej@xxxxxxxxxxxxx
In-reply-to: <20060719083014.B1935136@wobbly.melbourne.sgi.com>
References: <1153214961.6793.15.camel@x41ade> <20060719083014.B1935136@wobbly.melbourne.sgi.com>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
> 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. 

More than likely - the filesystem is exported to our Blue Gene rack
so gets hammered by parallel IO constantly. Oh, and the server also
exports a chunk of SATA raid out (3ware controller) as pvfs2...

I guess our priority should be to try and "source" some more memory
than the 512M we have in at the moment. 

> Your options are to take
> steps to combat inode extent fragmentation (like fsr), or use a
> more recent kernel (2.6.17+ IIRC).

OK - we were trying to stay reasonably simple by using vendor kernels but I 
guess it's time for a quick "make menuconfig"

Ta

Andrew

-- 
Andrew Elwell, System Administrator EPCC
Tel 0131 445 7833 (ACF Building)
Tel 0131 650 5023 (Rm 3309, JCMB)


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