On Thu, Nov 27, 2008 at 00:45, Dan Williams <dan.j.williams@xxxxxxxxx> wrote: > This is hopefully the tail of the feature additions from me for > mdadm-3.0-final. It adds the capability for mdadm to detect platform > raid capabilities, and honor them when creating new arrays. > This implementation crawls through sysfs to put this information > together, I believe it is crawling in a future proof fashion, but here > are my assumptions: > 1/ /sys/bus/pci/drivers/ahci/<x>/device will identify a pci ahci device Why "device"? You just check for the "device" attribute file of the PCI device? > 1/ An attempt to cover the delay between mdadm creating an array and the > friendly-named device node showing up in /dev/md/ by calling 'udevadm > settle' before starting starting Incremental assembly. This > specifically fixes scripts that do: > mdadm -A /dev/md/<container> > mdadm -I /dev/md/<container> > There is a good chance there is a better place to put this call, but > putting it in create_mddev didn't work, and moving it up in main() > resulted in a hang. I didn't want to hold up the other patches for this > debug. If mdadm calls "udevadm settle", we can not call mdadm (which we do already) from udev rules because it will just deadlock. We need to make "udevadm settle" smarter and not to wait for its own event, or make it wait for something specific and not just "all" events, or find a different way for mdadm to sync with udev. Thanks, Kay -- 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
