In article <20060611222209.006B8325B0@cs.usask.ca>,
	Greg Oster <oster@cs.usask.ca> writes:
> Frederick Bruckman writes:
>> 
>> I've always assumed there's a date stamp that
>> tells raidframe which compenent is newer.  Is there?  It'd be
>> nice to be able to see that date with "-g".
> 
> It's not a "date stamp" but a "modification counter".  Look for "Mod 
> Counter" in the output of "raidctl -s raid0".  These modification 
> counters are used in a voting fashion to determine what the correct 
> count should be (highest counter value used in case of a tie).
> 
> So in the case where a disk "happens to go away, and then come back 
> at the next reboot", the modification counter for the drive that 
> 'disappeared' should be 2 or 3 lower than the count for the good 
> drive.  Since the rest of the component labels match up, the 
> 'disappearing' drive will be added to the set, but in the "failed" 
> state.  Thus, the automatic parity rebuild will actually fail in this 
> case.

Ahh. Thanks for clearing that up.


Frederick