On Tue, 08.02.11 12:07, Lennart Poettering (lennart@xxxxxxxxxxxxxx) wrote: > > At this point we know it is container, know that it has external > > metadata and know that we need external metadata handler (mdmon). But > > it is too late for systemd. > > Kay, do you know why this "change" event is used here? Any chance we can > get rid of it? So, it seems that the "change" event does make some sense here. I have now added a new property to systemd: if you set SYSTEMD_READY=0 on a udev device then systemd will consider it unplugged even if it shows up in the udev tree. If this property is not set for a device, or is set to 1 we will conisder the device plugged. To make this md stuff compatible with systemd we hence just need to set SYSTEMD_READY=0 during the "new" event and drop it when the device is fully set up. Andrey, since you are playing around with this, do you happen to know which attribute we should check to set SYSTEMD_READY=0 properly? It would be cool if we could come up with a default rule for inclusion in our systemd rules file that will ensure the device only shows up when it is ready. Lennart -- Lennart Poettering - Red Hat, Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
