Ben Collver writes:
> >  6) when the machine comes back, check the status of the parity on raid0..
> >I'm curious to know if it's DIRTY, or clean.
> >
> >If it's dirty, then something is quite wrong somewhere.  If it's clean, then
> >the "parity becomes dirty" problem is related to shutting down the system.
> >My guess is that the 'swapctl -d' doesn't have enough time to do it's
> >job on a 'shutdown'...
> 
> When the machine came back up, the parity status is DIRTY.  Did I do
> something wrong?  If further tests would be helpful, please tell me what to
> do :)

After the 'swapctl -d /dev/raid0b', does a 'swapctl -a /dev/raid0b' succeed?

Let's also backup a step...  If you disable swap completely, does the parity 
remain clean after a reboot?

Later...

Greg Oster