Re: Kernel Oops RedHat 7.1 kernel-2.4.5 xfx-1.0.1

[Seth Mos <knuffie@xxxxxxxxx>]

At 14:28 7-8-2001 -0700, Poul Petersen wrote:
>         As I mentioned in a previous post, I'm running RedHat 7.1 with the
> manually patched 2.4.5 kernel and xfs-1.0.1 on a dual PII (400) with 1 Gig
> of RAM. The XFS filesystems are located on a SAN RAID device accessed
> through a qlogic 2100 Fibre Channel card (using the qla2x00 module provided
> by Qlogic, ver 4.25). This system acts as a "gateway" by mounting the disks
> from the SAN and then exporting them to an array of hosts (Solaris, IRIX,
> Linux, AIX, etc) via NFS. So far, we have had a total of four system oops's.
>
>
>         The first oops was "unprovoked". When we rebooted, the system
> generated the same oops ten minutes later. Then everything was OK. Two weeks
> later, we used xfs_growfs to grow one of the partitions which worked great
> (very cool). A few days later, the machine was accidentaly power cycled
> (human oops). During bootup, the system oops'd when trying to mount the XFS
> partition we had grown. That disk remains unmountable, and will oops any of
> the three machines we have on the SAN when mounted (we had a backup of the
> data and sufficient extra, so we just left this partition of death for
> testing). The fourth oops just occurred today when I tried to xfsdump a
> partition. I've included the ksymoops output for each of the oops's in
> order.

May I suggest running xfs_repair after growing a fs. It think it sets some 
of the neccesary bits right that would otherwise hamper recovery. Although 
i doubt it shoold oops the box.

The first comes from the qlogic driver as it seems, may be wrong about this 
one. Are there later drivers the that available? Do extensive stressing 
make the box oops?

The second, I suspect you need a newer kernel with some NFS fixes. Try the 
CVS tree or the 2.4.7 patch that is one the ftp site.

The third is probably related to the resize. I suggest running repair and 
trying again.
The fourth is probably the nfsdeamon taking a dump in the pool again.

Cheers
--
Seth
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.