On Mon, 2006-09-04 at 12:00 -0400, Josh Litherland wrote:
> I'll test to see if they actually change values, but I can say for
> certain that they are still invalid checksum, i.e. once I stop the array
> I have to assemble it with -U resync to get it back online. (and it of
> course rebuilds)
Some real strangeness here... So, while the array was up and running
(after mdadm -A -f -U resync ...) I checked the checksums:
Checksum : 70c30de5 - expected 70c30db5
Checksum : 70c30df7 - expected 70c30dd7
Checksum : 70c30e09 - expected 70c30de9
Checksum : 70c30e1b - expected 70c30deb
Then I unmounted, checked again... here's where things get weird
Checksum : 70c352e8 - correct
Checksum : 70c352fa - expected 70c352da
Checksum : 70c3530c - expected 70c352ec
Checksum : 70c3531e - correct
Went ahead and issues mdadm -S
Checksum : 70c352e8 - expected 70c352c8
Checksum : 70c352fa - expected 70c352da
Checksum : 70c3530c - expected 70c352ec
Checksum : 70c3531e - expected 70c352fe
Now utterly perplexed, I went ahead and checked mdadm -E several more
times. The actual stored checksum value isn't changing, but it's
switching around to saying "expected <something else>" to saying
"correct"... on ALL 4 drives at different times.
Anybody have a clue what's going on here? How does mdadm (or the
kernel, for that matter) decide what the checksum SHOULD be? I'll
code-dive to see if I can answer that myself, but if anyones knows, I'd
appreaciate a pointer.
Thanks!
--
Josh Litherland (josh@xxxxxxxxxxx)
-
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
