xfs
[Top] [All Lists]

Re: Request for known XFS bugs.

To: Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Subject: Re: Request for known XFS bugs.
From: Seth Mos <knuffie@xxxxxxxxx>
Date: Wed, 16 Oct 2002 10:12:14 +0200 (CEST)
Cc: linux-xfs@xxxxxxxxxxx, <andrea@xxxxxxx>
In-reply-to: <1034721379.4972.28.camel@UberGeek.coremetrics.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On 15 Oct 2002, Austin Gonyou wrote:

> I don't know if the issue is XFS, but I don't know it's *not* either.
> The server stats right now, are that I have two Dell 6650's with 8GB
> ram, RH 7.2 from the xfs 1.1 installer base, with most recent redhat
> updates, QLogic 2300Fs atached to ~1TB - 3TB of FC2 storage using LVM
> for volume management.

Does the box use interrupt sharing? There are also a lot of people on
linux-poweredge@xxxxxxxx that see interrupt only handled by the first
processor.

> The symptoms are that after about 6 days of uptime with loadavg ~10-12%
> most of the time, running oracle8i and some other apps we have, the box
> locks.

I could get this on a pe2550 that shared interrupts with a gigabit nic. If
you loaded NFS enough it would lock up.

These dell boxen are quite sensitive to the issue. Perhaps because of the
serverworks chipsets.

> Usually bad enough that none of the volumes ever get's shut down in any
> way, and usually corrupting the xfs log header, so that I have to run

Sounds familiar enough.

> p.s. We've performed all the usual diagnostics, troubleshooting, etc
> with all vendors in this situation, but still cannot find a resolution
> because when the box crashes, there are no bad log entries, or
> noticeable bad messages anywhere.

Did you do the interrupt trick?

Switch of what you don't need in the bios and reboot.
Go into the bios and switch on the scroll,caps and num lock.
Press Ctrl-E and system should beep at you.
reboot.

It will nog have reassigned the IRQ table.

Cheers
Seth


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