From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 19 Mar 2013 11:23:47 -0400 From: David Teigland Message-ID: <20130319152347.GA986@redhat.com> References: <1363699970-10002-1-git-send-email-bubble@hoster-ok.com> <1363699970-10002-2-git-send-email-bubble@hoster-ok.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1363699970-10002-2-git-send-email-bubble@hoster-ok.com> Subject: Re: [linux-lvm] [PATCH 01/10] lvchange: Allow cluster lock conversion Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Vladislav Bogdanov Cc: linux-lvm@redhat.com On Tue, Mar 19, 2013 at 01:32:41PM +0000, Vladislav Bogdanov wrote: > Allow clvm locks to be converted shared <-> exclusive with corosync/dlm. > > Without this it is impossible to alow both > * VM migration (shared lock is required) > * host-side snapshots of VM disks (exlusive lock is required) > > Locks are only converted if --force parameter passed to lvchange. > > Internally LKF_CONVERT flag is passed to dlm, so that is a real lock > conversion. > > Also deny release of an exclusive lock on a remote note without --force > flag to lvchange -an. I'm trying to figure out why the code doesn't already use CONVERT when possible; I would have expected it to. (It has to be combined with NOQUEUE to avoid deadlocks.) What happens now without this force/CONVERT patch? a new lock created/requested?