Jarom r Dolecek <dolecek@ics.muni.cz>  wrote:
 > Greg Oster wrote:
 > > [Yes, I believe that RAIDframe is solid, and yes, I run it on my machines,
 > > both at home and at work, and yes I would (and have) recommend it to others.]
 > 
 > Well, it could also be a hw problem. IIRC Herb used one whole disk
 > as a component, so a problem with the disk might cause such horrific
 > results. How hard it would be to replace the failed component/disk
 > with some other ? 

I used two disks.  Each disk as a seperate component.

Fwiw, I'm considering the possibility that my filesystem problems of 
this morning might be power-supply related.  I've never seen random
data corruption on NetBSD before and I see no reason why it should
start all of a sudden.

I don't honestly think that the raid partition was at fault here. My
reason for considering not using raid are due to the almost 2 hour
fsck/parity rebuild that happened when I rebooted after the panic this
morning.  That's not something I want to go through in the event that
my machine crashes.  I want it up sooner.  The system in question would
probably do just fine with a manual nightly mirror/rsync to protect
me in the event of failure.