Device-mapper devices are available only after a 'change' event,
so it's quite pointless to check for the 'add' event.
Signed-off-by: Hannes Reinecke <hare@xxxxxxx>
---
multipathd/main.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/multipathd/main.c b/multipathd/main.c
index 9975dd8..94b0b95 100644
--- a/multipathd/main.c
+++ b/multipathd/main.c
@@ -648,10 +648,12 @@ uev_trigger (struct uevent * uev, void *
lock(vecs->lock);
/*
- * device map add/remove event
+ * device map event
+ * Add events are ignored here as the tables
+ * are not fully initialised then.
*/
if (!strncmp(devname, "dm-", 3)) {
- if (!strncmp(uev->action, "add", 3)) {
+ if (!strncmp(uev->action, "change", 6)) {
r = uev_add_map(devname, vecs);
goto out;
}
--
1.4.3.4
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
