Date: Thu, 27 Jun 2002 10:19:19 -0400 (EDT)
From: Benito Venegas <venevene@securities.com>
To: Seth Mos <knuffie@xs4all.nl>
cc: <linux-xfs@oss.sgi.com>, Marek Kubita <mkubita@securities.com>
Subject: Re: kswapd Oops with 2.4.9-31SGI_XFS_1.1smp
In-Reply-To: <4.3.2.7.2.20020627085551.03c50ce8@pop.xs4all.nl>
Message-ID: <Pine.LNX.4.30.0206271015340.21513-100000@dns.securities.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk


On Thu, 27 Jun 2002, Seth Mos wrote:

> 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 did it of course.

>
> >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.

This oops happened when my server was on production. It freeze from one
momment to other. That ' s all. So it wasn't on reboot process..

>
> 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.

After to be in the list for almost a year, yeah!! I have always in my
considerations.

Thanks Seth

>

Salu2

Vene