From: zkabelac@sourceware.org <zkabelac@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW tools/vgchange.c
Date: 24 May 2010 08:59:31 -0000 [thread overview]
Message-ID: <20100524085931.5827.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac at sourceware.org 2010-05-24 08:59:30
Modified files:
. : WHATS_NEW
tools : vgchange.c
Log message:
Replicator: VG with cmd_missing_vgs does not generate output
Do not print message if missing VG is found.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1591&r2=1.1592
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/vgchange.c.diff?cvsroot=lvm2&r1=1.102&r2=1.103
--- LVM2/WHATS_NEW 2010/05/21 15:28:16 1.1591
+++ LVM2/WHATS_NEW 2010/05/24 08:59:29 1.1592
@@ -1,5 +1,6 @@
Version 2.02.67 -
===============================
+ Avoid print activation message if there is a missing VG (Replicator).
Fixed scripts/relpath.awk to work in mawk
Add _add_partial_replicator_to_dtree().
Activation code read and releases also remote VGs (Replicator).
--- LVM2/tools/vgchange.c 2010/05/06 11:15:56 1.102
+++ LVM2/tools/vgchange.c 2010/05/24 08:59:30 1.103
@@ -224,8 +224,10 @@
ret = _activate_lvs_in_vg(cmd, vg, available);
- log_print("%d logical volume(s) in volume group \"%s\" now active",
- lvs_in_vg_activated(vg), vg->name);
+ /* Print message only if there was not found a missing VG */
+ if (!vg->cmd_missing_vgs)
+ log_print("%d logical volume(s) in volume group \"%s\" now active",
+ lvs_in_vg_activated(vg), vg->name);
return ret;
}
next reply other threads:[~2010-05-24 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 8:59 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-14 18:20 LVM2 ./WHATS_NEW tools/vgchange.c mbroz
2010-10-29 21:15 agk
2010-10-25 10:40 agk
2010-05-24 9:03 zkabelac
2009-11-24 16:08 mbroz
2009-11-18 17:20 mbroz
2008-06-12 11:49 mbroz
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=20100524085931.5827.qmail@sourceware.org \
--to=zkabelac@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.