On Sat, May 21, 2005 at 07:17:21PM +0200, Erik van Konijnenburg wrote: > On Sat, May 21, 2005 at 05:35:48PM +0200, martin f krafft wrote: > > - echo "Starting raid devices: " > > + 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 > > + echo -n "Starting raid devices: "
> Mdadm is of course perfectly capable of creating it's own /dev/md0, > provided auto=md is given for the relevant device in /etc/mdadm/mdadm.conf. Which doesn't help the fact that mdadm -A -s --auto doesn't work, since the whole point of mdadm -A -s is to make this work without needing to populate mdadm.conf... > The problem is that users are not aware that this configuration option > exists, giving rise to repeated bug reports, so you want to create the > device regardless of config setting. Well, no; the problem is that this gives no way to auto-start all RAID arrays from userspace on 2.6 systems using udev, which is a regression against woody and against 2.4 systems using mdadm... > # rm /dev/md0 > rm: cannot remove `/dev/md0': No such file or directory > # cat /etc/mdadm/mdadm.conf > DEVICE partitions > ARRAY /dev/md0 level=raid1 num-devices=2 > UUID=85318365:3b91c827:faee55c7:b1d96199 > # /sbin/mdadm -A -s -a > mdadm: error opening /dev/md0: No such file or directory > # ./mdadm -A -s -a > mdadm: /dev/md0 has been started with 2 drives. > # ls -l /dev/md0 > brw------- 1 root root 9, 0 2005-05-21 19:06 /dev/md0 > # Aha, *that's* what I want to see... :) Thanks, -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
