On Mon, Oct 29, 2007 at 11:30:53AM -0400, Doug Ledford wrote:
On Mon, 2007-10-29 at 09:41 +0100, Luca Berra wrote:
>Remaking the initrd installs the new mdadm.conf file, which would have
>then contained the whole disk devices and it's UUID. There in would
>have been the problem.
yes, i read the patch, i don't like that code, as i don't like most of
what has been put in mkinitrd from 5.0 onward.
in case you wonder i am referring to things like
emit dm create "$1" $UUID $(/sbin/dmsetup table "$1")
Imho the correct thing here would not have been copying the existing
mdadm.conf but generating a safe one from output of mdadm -D (note -D,
not -E)
I'm not sure I'd want that. Besides, what makes you say -D is safer
than -E?
"mdadm -D /dev/mdX" works on an active md device, so i strongly doubt the
information
gathered from there would be stale
while "mdadm -Es" will scan disk devices for md superblock, thus
possibly even finding stale superblocks or leftovers.
I would strongly recommend against blindly doing "mdadm -Es >>
/etc/mdadm.conf" and not supervising the result.
--
Luca Berra -- [EMAIL PROTECTED]
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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
