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/locking.c Date: Tue, 27 Mar 2012 15:53:00 -0000 [thread overview] Message-ID: <20120327155347.10271.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: mbroz@sourceware.org 2012-03-27 15:53:45 Modified files: . : WHATS_NEW lib/locking : locking.c Log message: Fix exclusive lvmchange -aey to fail if volume is active on different node. Activation on remote node should be tried only if it is masked by tags locally (like when hosttags enabled, IOW activate_lv_excl_local() doesn't return error.) Introduced change caused that lvchange -aey succeeded even if volume was activated exclusively remotely. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2371&r2=1.2372 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/locking/locking.c.diff?cvsroot=lvm2&r1=1.104&r2=1.105 --- LVM2/WHATS_NEW 2012/03/27 11:04:46 1.2371 +++ LVM2/WHATS_NEW 2012/03/27 15:53:45 1.2372 @@ -1,5 +1,6 @@ Version 2.02.96 - ================================ + Fix exclusive lvchange running from other node. (2.02.89) Add 'vgscan --cache' functionality for consistency with 'pvscan --cache'. Keep exclusive activation in pvmove if LV is already active. Disallow pvmove for exclusive LV if some affected LVs are not exclusively activated. --- LVM2/lib/locking/locking.c 2012/03/26 20:33:40 1.104 +++ LVM2/lib/locking/locking.c 2012/03/27 15:53:45 1.105 @@ -551,7 +551,7 @@ if (!vg_is_clustered(lv->vg)) return activate_lv_excl_local(cmd, lv); - if (lv_is_active_exclusive(lv)) + if (lv_is_active_exclusive_locally(lv)) return 1; if (!activate_lv_excl_local(cmd, lv))
next reply other threads:[~2012-03-27 15:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-27 15:53 mbroz [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-08-10 16:07 mbroz 2011-01-13 14:56 zkabelac 2010-03-31 17:23 mbroz 2010-01-13 17:40 mbroz 2009-11-23 10:55 mbroz 2009-07-14 11:01 agk 2009-02-22 16:13 agk 2008-05-08 18:35 agk 2006-10-14 16:37 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=20120327155347.10271.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: linkBe 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).