On Sun, May 04, 2008 at 09:30:02AM +0200, Peter Rabbitson wrote:
I want to resurect this discussion with a peculiar observation - the above
mismatch was caused by GRUB.
...
I realized that my grub config contains a savedefault clause, which updates
the file on the raw ext3 volume before any raid assembly has taken place.
Executing grub-set-default from within a booted system (with a mounted
assembled raid) resulted in the subsequent md check to return 0 mismatches.
this has been a long standing issue with grub 1.x
hopefully some day grub 2 will be production ready and the issue will be
forgoten (real md raid support for grub 2 was added in google SOC 2006).
L.
--
Luca Berra -- bluca@xxxxxxxxxx
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
--
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
