From: agk@sourceware.org <agk@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW lib/metadata/metadata-exported.h
Date: 12 Feb 2012 22:37:25 -0000 [thread overview]
Message-ID: <20120212223725.31322.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk at sourceware.org 2012-02-12 22:37:24
Modified files:
. : WHATS_NEW
lib/metadata : metadata-exported.h
Log message:
FMT_INSTANCE_PV is no longer used
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2276&r2=1.2277
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/metadata-exported.h.diff?cvsroot=lvm2&r1=1.228&r2=1.229
--- LVM2/WHATS_NEW 2012/02/10 02:56:54 1.2276
+++ LVM2/WHATS_NEW 2012/02/12 22:37:24 1.2277
@@ -1,6 +1,7 @@
Version 2.02.91 -
===================================
- Refactor format instances for orphan PVs (internal).
+ Remove PV-based format instances (which are no longer needed).
+ Link all orphan PVs directly to a per-format global orphan VG.
Refactor lvmcache around an internal API.
Stop processing lvextend if trying to extend a mirror that is being recovered.
Add pool_below_threshold() function to check thin pool percent status.
--- LVM2/lib/metadata/metadata-exported.h 2012/02/10 02:53:05 1.228
+++ LVM2/lib/metadata/metadata-exported.h 2012/02/12 22:37:24 1.229
@@ -200,16 +200,13 @@
/*
* These flags define the type of the format instance to be created.
- * There are two basic types: a PV-based and a VG-based format instance.
+ * There used to be a PV-based type, but all are now VG-based.
* We can further control the format_instance initialisation and functionality
* by using the other flags. Today, the primary role of the format_instance
* is to temporarily store metadata area information we are working with. More
* flags can be defined to cover even more functionality in the future...
*/
-/* PV-based format instance */
-#define FMT_INSTANCE_PV 0x00000000U
-
/* VG-based format instance */
#define FMT_INSTANCE_VG 0x00000001U
reply other threads:[~2012-02-12 22:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120212223725.31322.qmail@sourceware.org \
--to=agk@sourceware.org \
--cc=lvm-devel@redhat.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.