Marco, I CC'd you on this because it's about your proposed solution to #294404, which works very well. However, Erik has pointed out a potential problem.
Based on your suggestion, mdadm now does the following in
S25mdadm-raid:
if [ -d /dev/.udevdb -a ! -e /dev/md0 -a ! -e /dev/md/0 ]; then
echo -n "Creating raid device nodes: "
cd /dev && WRITE_ON_UDEV=1 ./MAKEDEV md
echo "done."
fi
Erik said that if initrd brings up /dev/md0, partitions from other
software RAID devices (e.g. /dev/md7) cannot be brought up since the
above code skips the MAKEDEV call in the case of presence of
/dev/md0.
Thus, my options are:
1 check for another device node, e.g. /dev/md5 and hope that the
initrd only ever configures /dev/md0
2 check for multiple device nodes
3 check for all device nodes (is 0-15 the standard range?)
4 call MAKEDEV regardless of whether devices already exist, if
udev is present
5 use some other way
I personally favour 4, then 3, then 2. If I'd use 4, could
I potentially break things? Or would it be guaranteed that any
/dev/mdX device node brought up by the initrd would be major:minor
9:X as well?
I would appreciate if you could let me know your thoughts and
suggestions.
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, admin, user, and author
`. `'`
`- Debian - when you have better things to do than fixing a system
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
on the other hand, you have different fingers.
signature.asc
Description: Digital signature
