On Fri, Feb 6, 2009 at 9:40 AM, Jeremy Katz <katzj@xxxxxxxxxx> wrote: > RAID arrays should be getting started by udev rules, not by explicit > calls to mdadm in /init. Yes, this means having proper integration with > udev for your kernel pieces. But this ends up helping everything as it > will also let us lose the multiple redundant calls to things like mdadm > (and lvm, etc) throughout the boot process which should just be > occurring as devices show up. The trick is determining when a device has not shown up yet versus it will never show up... to prevent the array being marked degraded prematurely. Is there some mechanism for udev to broadcast "if you were waiting for more devices to show up don't hold your breath"? I.e. at the point where a call to "udevadm settle" would reasonably be expected to not find any pending events? I am thinking something along the lines of: <udev: add disk> mdadm --incremental --no-degraded $dev <udev: add disk> mdadm --incremental --no-degraded $dev <udev: probably no more devices> mdadm --incremental $last_dev -- Dan -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
