xfs
[Top] [All Lists]

Re: XFS NFS server Oops

To: "Ian D. Hardy" <i.d.hardy@xxxxxxxxxxx>
Subject: Re: XFS NFS server Oops
From: Steve Lord <lord@xxxxxxx>
Date: 06 Mar 2002 13:12:19 -0600
Cc: linux-xfs@xxxxxxxxxxx, idh@xxxxxxxxxxx
In-reply-to: <3C5E8CFA.CACF28C3@soton.ac.uk>
References: <3C5E8CFA.CACF28C3@soton.ac.uk>
Sender: owner-linux-xfs@xxxxxxxxxxx
On Mon, 2002-02-04 at 07:30, Ian D. Hardy wrote:
> Hi,
> 
> Anyone any ideas on the following Oops (processed with ksymoops 2.4.3). It is
> from a NFS server (Dual 1Ghz Supermicro LE, 1Gbyte RAM, 40Gbyte Maxtor IDE 
> system disk, Zero-D/GForce RI Fibrechannel to IDE hardware RAID-5 500Gbyte
> disk unit). It is running the Linux 2.4.17-xfs kernel taken as a CVS image
> on 27th January. The main area of disk it is serving is on the HW RAID unit,
> which is the only XFS filesystem on the system. The system had been up
> for just over 3 days when it crashed.
> 
> I reported a very similar failure a few weeks ago, at that time running a
> 2.4.9 based kernel, Steve Lord suggested that we tried the latest CVS image
> as this had fixed some memory alloacation problems.
> 
> The machine is essentially an NFS fileserver to a computational cluster. 
> Though
> of possible interest is the 'save' process that was running on one of the
> processes, this is the Legato Networker backup client process (which was
> performing a full backup of the XFS filesystem at the time). I don't think
> this is significant as I was seeing these crashes (at ~4 to 12 day intervals)
> with the 2.4.9 kernel not dependant upon a 'save' session running.
> 
> 

Ian, can you try the attached patch against a current cvs kernel and see
if it helps at all.

Steve



-- 

Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@xxxxxxx

Attachment: vnode.patch
Description: Text document

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