> From [email protected] Mon Jul 1 > 14:33:54 2013 > Delivered-To: [email protected] > From: Joel Sing <[email protected]> > To: [email protected] > Subject: CVS: cvs.openbsd.org: src > Sender: [email protected] > > CVSROOT: /cvs > Module name: src > Changes by: [email protected] 2013/07/01 05:33:21 > > Modified files: > sys/dev : softraid.c > > Log message: > When an I/O error occurs on a softraid chunk, only take it offline if the > discipline supports redundancy. In the non-redundant case, there is little > to gain my failing the chunk, in fact it just makes any form of data > recovery significantly harder. > > ok krw@ todd@
Would it make sense to behave like this when the discipline supports redundancy, but redundancy isn't actually available? I had this happen to me when one mirrored drive went offline, and during rebuild the remaining "good" drive had a transient hiccup, taking the whole thing down.
