Message-Id: <4.3.2.7.2.20020627085551.03c50ce8@pop.xs4all.nl>
Date: Thu, 27 Jun 2002 09:03:29 +0200
To: Benito Venegas <venevene@securities.com>, <linux-xfs@oss.sgi.com>
From: Seth Mos <knuffie@xs4all.nl>
Subject: Re: kswapd Oops with 2.4.9-31SGI_XFS_1.1smp
Cc: Marek Kubita <mkubita@securities.com>
In-Reply-To: <Pine.LNX.4.30.0206261918400.20099-100000@dns.securities.co
 m>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

At 22:32 26-6-2002 -0400, Benito Venegas wrote:
>Hi Boys (any girl here :P)
>
>System was running ok until today. I had to reboot server manually.
>This is the first one Oops since a  long time ago (last was on xfs  1.0.2)
>This server is not using NFS server.
>We use some perl script, java tools for internal worflow system.

checking/repairing your filesystem might be a good idea. Even when it's not 
damaged it would not hurt to check.

>I will check if I need update firmware.

There have been both raid and bios updates in the past. I know of at least 
one PERC2 update that fixes corruption during poweroff with write back 
cache enabled. (even with the battery pack).

Do you get this oops at every boot of the machine or very frequent? 
Checking your system after an Oops is always a good idea in my opinion.

Journaling filesystems can recover from a poweroff and have filesystem 
integrity.
But they can NOT protect you from data corruption when your kernel oopses. 
If something is clobbering some important part of memory that just got 
written to you have a serious problem.

Cheers

--
Seth
It might just be your lucky day, if you only knew.