unintended ATARAIDDELETE

[Doug White]

On Sat, 18 Oct 2003, Barney Wolff wrote:

> > This usually means your disk is bad, which is why it keeps trashing the
> > array.  Your system is trying to tell you something :-)
>
> Well of course the bad block is h/w.  But deleting a raid0 on a hard
> error is insane.  I can more-or-less understand for raid1 why that
> might be thought sensible, but a split raid0 is of no use for anything.
> Nor could I find anywhere in the kernel that actually deletes the raid.
> But for sure -stable from 9/24 behaved differently (ie, sanely) on
> getting the error than -stable from 10/13 or so.  I don't think that's
> hardware.  Time will tell, perhaps.

Since one part of the RAID is defective, and raid0 is not redundant, the
RAID is marked offline.  It is working as designed.

If you need to tolerate disk failure, you probably want raid1, a mirrored
configuration.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite at gumbysoft.com          |  www.FreeBSD.org