"Louis Guillaume" writes:
> 
> 
> Greg Oster writes:
> > "Louis Guillaume" writes:
> > 
[snip]
> > 
> >> in small, subtle and 
> >>as-of-yet non-critical ways. Lucky me! This, of course, only gets fixed 
> >>by fsck-ing. Any idea of what's causing this 
> > 
> > 
> > My guess would be bad RAM, but I might be biased...  (There are NO 
> > bugs (at least that I'm aware of) in RAIDframe that would be causing 
> > this sort of lossage.)
> > 
> > 
> >>or if it could be avoided by configuring Raid differently?
> > 
> 
> > 
> > You havn't given any config files, but you shouldn't see filesystem 
> > lossage from any valid RAIDframe configuration (and if a 
> > configuration isn't valid, RAIDframe shouldn't allow it).
> > 
> Perhaps the problem wasn't with RAIDframe itself but with my 
> configuration. Here are the old and new configs. Please let me know if 
> you see anything funky.

I didn't see any problems with any of the config files or any of the 
disklabels.  

I'd still be looking to run something that checks the memory... :-/

> The old configuration was a single RAID-1 array with 3 filesystems, / 
> /home and swap.
> 
> The new one is 5 RAID-1 arrays one for each of / /home /usr /var and swap.
[snip]

Later...

Greg Oster