Re: 2.1.8* kernels and md raid0

Michael L. Galbraith (mikeg@weiden.de)
Mon, 9 Mar 1998 06:16:26 +0100 (MET)


On Sun, 8 Mar 1998, Andy Higgins wrote:

>
> My experience with md raid0 has been a very good one:
>
> System Dual P-PRO 200 Tyan
> 2 BusLogic BT-948's and one md0 device using raid0
> consisting of 6 Seagate 4GB Hawks.
> Application: multiple full news feeders and readers..
> I've been testing new News software has lead to almost a crash
> a day and fsck cleans up /dev/md0 perfectly with no
> file corruption noticeable. Have been running this configuration
> with INN for about a 6 mos and have yet to lose any data (knock on wood)
>
> Regards
>
> On Sun, 8 Mar 1998, Isaac Connor wrote:
>
> >
> > I have a question about the currnt stability of MD RAID0. The reason I
> > ask is that since implementing it, I have experienced serious
> > instability, and finaly complete utter an total filesystem corruption in
> > the space of 48 hours uptime. (Fresh install to complete crap in 48
> > hours). I am trying to determine whether the md code is at fault, or
> > perhaps if using it has revealed a problem with my hardware. I am just
> > curious if others use this and find it stable. Here is my system:
> >
> > Tyan Tomcat IIID
> > 2 p200
> > 48M EDO ram.
> > Buslogic bt958 SCSI
> > Glibc 206 based system, 2.1.8* kernels (I tried several).
> >
> > md setup
> > I have an ide 2.0Gb IDE Western Digital Caviar series HD on hdb
> > I have a Seagate 2.1Gb SCSI HD on sda
> >

Maybe that Caviar drive is living up to it's reputation. I have seen
the same thing happen on a windows box with a caviar drive. Appeared
to work, but repeatedly corrupted files.

-Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu