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 lib/locking/cluster_locking.c
Date: Mon, 26 Mar 2012 20:29:00 -0000 [thread overview]
Message-ID: <20120326202947.14242.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mbroz@sourceware.org 2012-03-26 20:29:46
Modified files:
. : WHATS_NEW
lib/locking : cluster_locking.c
Log message:
Remove unused and wrongly set cluster VG flag from clvmd lock query command.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2367&r2=1.2368
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/locking/cluster_locking.c.diff?cvsroot=lvm2&r1=1.64&r2=1.65
--- LVM2/WHATS_NEW 2012/03/23 16:28:40 1.2367
+++ LVM2/WHATS_NEW 2012/03/26 20:29:45 1.2368
@@ -1,5 +1,6 @@
Version 2.02.96 -
================================
+ Remove unused and wrongly set cluster VG flag from clvmd lock query command.
Fix pvmove for exclusively activated LV pvmove in clustered VG. (2.02.86)
Always free hash table on update_pvid_to_vgid() in lvmetad.
Update and fix monitoring of thin pool devices.
--- LVM2/lib/locking/cluster_locking.c 2012/01/21 05:29:52 1.64
+++ LVM2/lib/locking/cluster_locking.c 2012/03/26 20:29:46 1.65
@@ -538,7 +538,7 @@
strcpy(args + 2, resource);
args[0] = 0;
- args[1] = LCK_CLUSTER_VG;
+ args[1] = 0;
status = _cluster_request(CLVMD_CMD_LOCK_QUERY, node, args, len,
&response, &num_responses);
next reply other threads:[~2012-03-26 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 20:29 mbroz [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-21 15:49 agk
2011-02-02 23:39 agk
2010-04-13 14:36 mbroz
2008-04-14 19:49 agk
2006-06-12 9:46 pcaulfield
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=20120326202947.14242.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).