On Tue, 25 Feb 2014, Eyal Lebedinsky wrote:
Final thought: if this sector is in an important header, when it *does*
need to be read (and fail), how bad a reaction should I expect?
I have two thoughts here:
Check data offset when doing mdadm -E. There you will see how much unused
data is allocated between the superblock and start of the actual array
data contents. This might be where your pending block is.
Regarding re-write. I have had happen to me that one drive that had bad
blocks that "check" didn't find errors on, when I rebooted that drive had
read errors on the superblock, was not assembled into the array, and
instead md started rebuilding to a spare since the array was degraded. So
my wonder is, when issuing "check" or "repair", does md actually check if
the superblocks are readable? If not, perhaps it should? Should it check
the contents of the superblocks are consistent with the data that the
kernel has in its data structures?
--
Mikael Abrahamsson email: swmike@xxxxxxxxx
--
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
