So when this bug was first reported we were using multipath 0.4.8, it doesn't appear
to have this cookie mechanism. 0.4.9 does (oneiric and higher); I have been
unable to reproduce the issue with 0.4.9. Going back through the logs...
"""
From 8d63b33d0996e141a2451df552b062b908db15bc Mon Sep 17 00:00:00 2001
From: Benjamin Marzinski <email address hidden>
Date: Mon, 17 May 2010 14:03:38 -0500
Subject: [PATCH] multipath: add udev sync support.
device-mapper in now able to synchronize operations through udev. This patch
allows multipath and kpartx to make use of this feature. If kpartx is run with
"-s", it waits for the partitions to be created before returning. Multipath
will now always wait for the devices to be created before returning.
This feature requires dm_task_set_cookie() which was finalized in device-mapper
version 1.2.38
"""
Appears to be where cookie support was initially added. I'll retest with 0.4.8 to
verify that the fault still exists (probably) and take it from there.
So when this bug was first reported we were using multipath 0.4.8, it doesn't appear
to have this cookie mechanism. 0.4.9 does (oneiric and higher); I have been
unable to reproduce the issue with 0.4.9. Going back through the logs...
""" 1a2451df552b062 b908db15bc Mon Sep 17 00:00:00 2001
From 8d63b33d0996e14
From: Benjamin Marzinski <email address hidden>
Date: Mon, 17 May 2010 14:03:38 -0500
Subject: [PATCH] multipath: add udev sync support.
device-mapper in now able to synchronize operations through udev. This patch
allows multipath and kpartx to make use of this feature. If kpartx is run with
"-s", it waits for the partitions to be created before returning. Multipath
will now always wait for the devices to be created before returning.
This feature requires dm_task_ set_cookie( ) which was finalized in device-mapper
version 1.2.38
"""
Appears to be where cookie support was initially added. I'll retest with 0.4.8 to
verify that the fault still exists (probably) and take it from there.