Neil Brown wrote:
As the event count needs to be updated every time the superblock isMay I ask why?
modified, the event count will be updated forever active->clean or
clean->active transition. All the drives in an array must have the
same value for the event count, so the spares need to be updated even
though they, themselves, aren't exactly 'active' or 'clean'.
I can understand why the active drives need to have the same superblock - it marks the data set as consistent and is used on restart to indicate integrity across the set and avoid a resync.
But the spare has no data on it. What does it mean that the superblock is up to date?
In fact isn't that misleading?
Surely, if anything, the spare _should_ have an out of date superblock?
David
- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
