public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: mbroz@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW tools/vgchange.c
Date: Thu, 12 Jun 2008 11:49:00 -0000 [thread overview]
Message-ID: <20080612114947.31490.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mbroz@sourceware.org 2008-06-12 11:49:46
Modified files:
. : WHATS_NEW
tools : vgchange.c
Log message:
Fix vgchange to not activate mirror leg and log volumes directly.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.899&r2=1.900
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/vgchange.c.diff?cvsroot=lvm2&r1=1.64&r2=1.65
--- LVM2/WHATS_NEW 2008/06/11 12:14:41 1.899
+++ LVM2/WHATS_NEW 2008/06/12 11:49:45 1.900
@@ -1,6 +1,8 @@
Version 2.02.39 -
================================
-
+ Fix vgchange to not activate mirror leg and log volumes directly.
+ Fix test directory clean up in make distclean.
+
Version 2.02.38 - 11th June 2008
================================
Fix tracking of validity of PVs with no mdas in lvmcache.
--- LVM2/tools/vgchange.c 2008/04/10 17:09:32 1.64
+++ LVM2/tools/vgchange.c 2008/06/12 11:49:46 1.65
@@ -66,10 +66,14 @@
if ((lv->status & SNAPSHOT) || lv_is_cow(lv))
continue;
- /* Can't deactive a pvmove or log LV */
+ /* Only request activation of mirror LV */
+ if ((lv->status & MIRROR_IMAGE) || (lv->status & MIRROR_LOG))
+ continue;
+
+ /* Can't deactivate a pvmove LV */
/* FIXME There needs to be a controlled way of doing this */
if (((activate == CHANGE_AN) || (activate == CHANGE_ALN)) &&
- ((lv->status & PVMOVE) || (lv->status & MIRROR_LOG)))
+ ((lv->status & PVMOVE) ))
continue;
if (activate == CHANGE_AN) {
next reply other threads:[~2008-06-12 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 11:49 mbroz [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-14 18:20 mbroz
2010-10-29 21:15 agk
2010-10-25 10:40 agk
2010-05-24 9:03 zkabelac
2010-05-24 8:59 zkabelac
2009-11-24 16:08 mbroz
2009-11-18 17:20 mbroz
2004-06-24 14:48 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=20080612114947.31490.qmail@sourceware.org \
--to=mbroz@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: link
Be 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).