Greg Oster wrote:
> The only reason a parity check should fail is if one of the 
> components has errors, which the "has anything failed?" check 
> should detect.

I have a small server (securelevel=2) which went through a power outage 
and when it came up it had both components "optimal", but parity was 
wrong ("Parity status: dirty"; it was not corrected by 
/etc/rc.d/raidframeparity because of securelevel). The current daily 
test doesn't detect this situation.

r.