On 03/27/2015 06:59 AM, Benjamin Marzinski wrote: > On Mon, Mar 16, 2015 at 01:37:05PM +0100, Hannes Reinecke wrote: >> During startup multipathd might race with udev and device discovery. >> During that time any information from libudev might not be fully >> available, leading to spurious multipathd failures during startup. >> So instead of scanning all devices on our own we should just >> re-trigger the existing devices; with that we'll read _all_ >> devices via uevents during startup and avoid the race condition. > > Should we also be sending change uevents for the dm devices? > No. We just need to retrigger the 'sd' devices, as with them we'll be reconfiguring the dm devices anyway. Cheers, Hannes -- Dr. Hannes Reinecke zSeries & Storage hare@xxxxxxx +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton HRB 21284 (AG Nürnberg) -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel