public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: prajnoha@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW lib/format_text/flags.c Date: Tue, 15 Nov 2011 11:54:00 -0000 [thread overview] Message-ID: <20111115115417.9067.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: prajnoha@sourceware.org 2011-11-15 11:54:17 Modified files: . : WHATS_NEW lib/format_text: flags.c Log message: 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 Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2183&r2=1.2184 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/format_text/flags.c.diff?cvsroot=lvm2&r1=1.48&r2=1.49 --- LVM2/WHATS_NEW 2011/11/14 21:30:35 1.2183 +++ LVM2/WHATS_NEW 2011/11/15 11:54:15 1.2184 @@ -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. --- LVM2/lib/format_text/flags.c 2011/09/08 16:41:18 1.48 +++ LVM2/lib/format_text/flags.c 2011/11/15 11:54:16 1.49 @@ -45,6 +45,7 @@ {ALLOCATABLE_PV, "ALLOCATABLE", STATUS_FLAG}, {EXPORTED_VG, "EXPORTED", STATUS_FLAG}, {MISSING_PV, "MISSING", COMPATIBLE_FLAG}, + {UNLABELLED_PV, NULL, 0}, {0, NULL, 0} };
next reply other threads:[~2011-11-15 11:54 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-15 11:54 prajnoha [this message] -- strict thread matches above, loose matches on Subject: below -- 2004-05-05 18:15 agk
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20111115115417.9067.qmail@sourceware.org \ --to=prajnoha@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).