On Tue, 2002-01-15 at 13:33, Ian D. Hardy wrote:
> Hi,
>
> For some time we've been having problem with a server, which is acting
> as a master/control node and NFS server for a computational cluster
> (~180 client nodes). The server will crash after anywhere between
> a few hours and 10 days operation. We've tried various kernels and
> XFS patch versions from 2.4.9 kernel with XFS patch-2.4.9-xfs-2001-08-17
> up to and including 2.4.16 kernel with the xfs-2.4.16-all-i386 patch,
> if anything the 2.4.9 kernel has proved the most reliable (it normally
> lasts between 4 and 10 days! - 2.4.16 lasted less than 24hrs).
>
> I've just recovered and processed the following Oops from the most
> recent crash (running 2.4.9 kernel), ksymoops output below which would
> appear to point to a problem in the XFS kernel code as called from the
> nfsd daemon process.
>
> The server is a dual (1Ghz PIII) based on a SuperMicro ServerWorks LE
> motherboard with 1Gbyte RAM, 40Gbyte Maxtor system disk and a QLogic
> QLA2200 FC card connecting an external HW (IDE) RAID array. Its got
> a RedHat 6.2 based distro but with the 2.4.x series kernel and XFS
> patches. (We're just starting to run some controlled tests with a similar
> server with a RH 7.2 distro and 2.4.14 kernel/XFS 1.0.2 release and or
> 2.4.17 and latest XFS patch release).
>
> Anyone any ideas what is causing this? or better still how to fix it?
>
> Thanks
>
> Ian
>
Almost certainly this is an out of memory condition, just from looking
at the code in the function you oopsed in. Would you say your system is
stressed when it comes to memory?
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx
|