martin f krafft wrote:
also sprach martin f krafft <[EMAIL PROTECTED]> [2006.08.10.1400 +0100]:
Could you please try mdadm 2.5.3-1~unreleased.3 ?
It adds the udev rules because mdadm seems to create the device
nodes even for devices that have already been assembled now. This is
not a final fix but I'd like to get confirmation on this behaviour.
http://debian.madduck.net/repo/dists/UNRELEASED/main/source/admin/mdadm_2.5.3-1~unreleased.3.dsc
http://debian.madduck.net/repo/dists/UNRELEASED/main/binary-i386/admin/mdadm_2.5.3-1~unreleased.3_i386.deb
I've "released" 2.5.3-1~unreleased.4.
http://debian.madduck.net/repo/dists/UNRELEASED/main/source/admin/mdadm_2.5.3-1~unreleased.4.dsc
http://debian.madduck.net/repo/dists/UNRELEASED/main/binary-i386/admin/mdadm_2.5.3-1~unreleased.4_i386.deb
It now uses udev again but also adds a script that tries to
determine whether /dev/md/X is in use (for each node). If it cannot
determine that, it uses /dev/mdX.
Awaiting your feedback.
Rebooted fine with /dev/md0 created.
dmesg|grep md
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
md: raid1 personality registered for level 1
md: md0 stopped.
md: bind<hdb3>
md: bind<hda3>
raid1: raid set md0 active with 2 out of 2 mirrors
EXT3 FS on md0, internal journal
Arthur.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
