(cc XFS mailing list)
Quoting Tom Tran <tom.tran@xxxxxxxxx>:
> I am seeing that you have the latest 6.8 codeset.
Yes. I upgraded when I found out about it. I found out about it when the kernel
ChangeLog showed a 3ware drive upgrade. These normally come with firmware
upgrades so after upgrading my kernel I flashed my controller.
> 1. Were you using the old driver and firmware before upgrading to the
> current software?
No. I upgraded my kernel first to one which matched the currently latest driver
(I forget if this was 2.4.6 or 2.4.7).
> 2. What about the ext2 file system? I am seeing the xfs problems but could
> not tell if ext2 also has problems or not.
My only ext2 partition is my /boot and that doesn't get written to often.
>From the report of Dan Yocum <yocum@xxxxxxxx> (maybe you can get in touch with
him?) it looks like the 3ware Escalade 6000 controllers have difficulty with
situations where a drive element of a RAID5 array goes offline while a write is
in progress. These cause data corruptions at least in XFS (as I've experienced).
My data corruption happened when one drive died, which was around 11:00am. I
didn't notice the corruption until 2:00pm when a script did a "du -csm" on some
directories in /home that were hit by this data corruption. E-mail, not so
critical, thank God (although still not good). I still have three live drives
and am running degraded mode now (so far no problems, I have my fingers
crossed). I am rushing to get a replacement soon (I know, I should have had a
>From what Dan Yocum said it's only the 7000 series that can handle this "drive
going offline while writing data" problem. I do not know if he did tests with
ReiserFS and/or ext2. And while we're at it: JFS and ext3. Maybe you can
attempt to run into these problems in your lab? I'm sure you have enough
machines to get the various filesystems on them.
Federico Sevilla III :: jijo@xxxxxxxxxxxxxxxxxxxx
Network Administrator :: The Leather Collection, Inc.
GnuPG key: <http://www.leathercollection.ph/jijo.gpg>