also sprach Piergiorgio Sartor <piergiorgio.sartor@nexgo.de> [2010.02.19.1016 +0100]:
> There is the kernel boot paramenter "rd_NO_MDADMCONF", which
> forces "dracut" to do not use the "mdadm.conf" in the initramfs
> image.
>
> My impression is that it uses the "mdadm -I" functionality.
Indeed, it does. However, I could not find out how it does device
naming? From what I understand, mdadm will only assemble devices
using the name stored in the superblocks iff the homehost matches,
so dracut either doesn't provide for this and requires the use of
UUIDs to mount filesystems (making the array name secondary), or it
needs to know what the homehost is. For this, it either needs
mdadm.conf, or the hostname must be stored in the initramfs.
Could you research this and let us know how dracut invokes mdadm?
--
martin | http://madduck.net/ | http://two.sentenc.es/
"licht wird alles, was ich fasse"
- friedrich nietzsche
spamtraps: madduck.bogus@madduck.net
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)