From 5680d14ecd1cc788dd06bce6642fa605659414ed Mon Sep 17 00:00:00 2001 From: Peter Rajnoha Date: Tue, 15 Nov 2011 11:54:15 +0000 Subject: [PATCH] Avoid 'mda inconsistency' by properly registering UNLABELLED_PV flag (2.02.86). When a PV label write is deferred to a vg_write call (as introduced by a patch in 2.02.86), the PV is flagged with the internal UNLABELLED_PV flag. However, when calling vg_archive before vg_write, we still have the PV labelled with the UNLABELLED_PV flag which was not recognised as a proper flag while exporting VG metadata: # vgcreate vg /dev/sda No physical volume label read from /dev/sda Metadata inconsistency: Not all flags successfully exported. Metadata inconsistency: Not all flags successfully exported. Writing physical volume data to disk "/dev/sda" Physical volume "/dev/sda" successfully created Volume group "vg" successfully created --- WHATS_NEW | 1 + lib/format_text/flags.c | 1 + 2 files changed, 2 insertions(+) diff --git a/WHATS_NEW b/WHATS_NEW index 1b1181d38..2413b6b82 100644 --- a/WHATS_NEW +++ b/WHATS_NEW @@ -1,5 +1,6 @@ Version 2.02.89 - ================================== + Avoid 'mda inconsistency' by properly registering UNLABELLED_PV flag (2.02.86). Fix --enable-static_link unless using --enable-dmeventd / --enable-udev_sync. Move gentoo MAKEDEV to /sbin in lvm2create_initrd. Add filter to avoid scan of device if it is part of active multipath. diff --git a/lib/format_text/flags.c b/lib/format_text/flags.c index a65736d34..9b2788f4c 100644 --- a/lib/format_text/flags.c +++ b/lib/format_text/flags.c @@ -45,6 +45,7 @@ static const struct flag _pv_flags[] = { {ALLOCATABLE_PV, "ALLOCATABLE", STATUS_FLAG}, {EXPORTED_VG, "EXPORTED", STATUS_FLAG}, {MISSING_PV, "MISSING", COMPATIBLE_FLAG}, + {UNLABELLED_PV, NULL, 0}, {0, NULL, 0} }; -- 2.43.5