Received: (from majordomo@localhost)
	by oss.sgi.com (8.11.2/8.11.3) id f766gwu27436
	for linux-xfs-outgoing; Sun, 5 Aug 2001 23:42:58 -0700
Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135])
	by oss.sgi.com (8.11.2/8.11.3) with SMTP id f766gtV27416
	for <linux-xfs@oss.sgi.com>; Sun, 5 Aug 2001 23:42:55 -0700
Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.168])
	by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id IAA01685;
	Mon, 6 Aug 2001 08:42:39 +0200 (CEST)
Message-Id: <4.3.2.7.2.20010806083700.03264608@pop.xs4all.nl>
X-Sender: knuffie@pop.xs4all.nl
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 06 Aug 2001 08:42:14 +0200
To: Federico Sevilla III <jijo@leathercollection.ph>,
   Linux XFS Mailing List <linux-xfs@oss.sgi.com>
From: Seth Mos <knuffie@xs4all.nl>
Subject: Re: corrupt inode
Cc: Linux 3Ware Support <linux@3ware.com>
In-Reply-To: <Pine.LNX.4.33.0108061409270.5135-100000@gusi.leathercollec
 tion.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

At 14:13 6-8-2001 +0800, Federico Sevilla III wrote:
>Hi everyone,
>
>Today's my "ghost in the machine" day.
>
>First one of the drives in my four-disk RAID5 fails. So far the three are
>okay so I'm surviving. I'm using a 3ware Escalade 6400 controller with:
>
>  o Montior version ME6X 1.01.00.028
>  o Firmware version FE6X 1.02.03.053
>  o BIOS version BE6X 1.07.01.015
>
>AFAIK this doesn't have that RAID5 degraded problem. I'm using Linux
>kernel 2.4.7 with XFS. I got the following error:

Someone else on the list could produce corruption when the power of the 
drive went and you had a raid5 volume. Although that was a 6800. I don't 
know if the person is lurking around on the list.

Below is his mail.

-----<snip>
FWIW, I got really good at reliably corrupting my data with the 3ware 6800
card and RAID5: just turn off a drive while it was writing.  Bad things
happened.  I've been testing 3 7810 cards they lent to me a couple weeks
ago, and I haven't had a problem yet (after ~10TB write/reads and ~12
simulated drive failures under a variety of high and low I/O and CPU duty
cycles.

Cheers,

Dan
--
Dan Yocum
----<snip>

He can be reached at yocum@fnal.gov


>Aug  6 14:05:18 gusi kernel: cmn_err level 4 Filesystem "sd(8,11)": 
>corrupt inode 21967679 (btree).  Unmount and run xfs_repair.

You can see a oops comming when your file system shutsdown ;)

>It's the middle of the day and everyone's working but I told them all to
>shut down. I'm sending this message then I'm unmounting and running
>xfs_repair. I've got my fingers crossed. I hope nothing will mess up. I
>hope to be able to get back to the list about this after.

Good Luck!

>  --> Jijo
>
>--
>Federico Sevilla III  :: jijo@leathercollection.ph
>Network Administrator :: The Leather Collection, Inc.
>GnuPG Key: <http://www.leathercollection.ph/jijo.gpg>

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.