>Number:         21701
>Category:       kern
>Synopsis:       Kill the filesystem instead of panicing on an unrecoverable error
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed May 28 03:30:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Curt Sampson
>Release:        NetBSD 1.6K
>Organization:
>Environment:
System: NetBSD angelic.cynic.net 1.6K NetBSD 1.6K (ANGELIC2-$Revision: 1.5 $) #0: Tue Nov 26 11:52:20 JST 2002 cjs@angelic.cynic.net:/u/netbsd/libretto/sys/arch/i386/compile/ANGELIC2 i386
Architecture: i386
Machine: i386
>Description:

    Currently, if multiple components in a RAID device fail such that
    the RAID device can no longer reliably continue operation (e.g.,
    in a RAID-5 with one parity disk, two components fail), RAIDframe
    panics the system. This allows some hope of recovery if the second
    component did not fail due to a permenent hardware error. However,
    there's no need to go quite so far; simply deconfiguring that
    RAID device (thus forcably unmounting the filesystem) would also
    do the trick quite nicely, and leave the system up if it were a
    non-critical RAID device that failed.

>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: