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: Tue, 13 Apr 2010 14:36:00 -0000 [thread overview]
Message-ID: <20100413143625.13259.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mbroz@sourceware.org 2010-04-13 14:36:25
Modified files:
. : WHATS_NEW
lib/locking : cluster_locking.c
Log message:
Mask LCK_HOLD flag in cluster VG locks for compatibility reasons.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1512&r2=1.1513
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/locking/cluster_locking.c.diff?cvsroot=lvm2&r1=1.41&r2=1.42
--- LVM2/WHATS_NEW 2010/04/13 01:54:32 1.1512
+++ LVM2/WHATS_NEW 2010/04/13 14:36:24 1.1513
@@ -1,5 +1,6 @@
Version 2.02.63 -
================================
+ Mask LCK_HOLD flag in cluster VG locks for compatibility reasons.
Add activation/polling_interval to lvm.conf as --interval default.
Don't ignore error if resuming any LV fails in resume_lvs.
Skip closing persistent filter cache file if open failed.
--- LVM2/lib/locking/cluster_locking.c 2010/03/26 15:40:14 1.41
+++ LVM2/lib/locking/cluster_locking.c 2010/04/13 14:36:25 1.42
@@ -415,6 +415,13 @@
lock_scope = "VG";
clvmd_cmd = CLVMD_CMD_LOCK_VG;
+ /*
+ * Old clvmd does not expect LCK_HOLD which was already processed
+ * in lock_vol, mask it for compatibility reasons.
+ */
+ if (flags != LCK_VG_COMMIT && flags != LCK_VG_REVERT)
+ flags &= ~LCK_HOLD;
+
break;
case LCK_LV:
next reply other threads:[~2010-04-13 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 14:36 mbroz [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-26 20:29 mbroz
2011-10-21 15:49 agk
2011-02-02 23:39 agk
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=20100413143625.13259.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).