From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 31 May 2019 09:38:26 -0500 From: David Teigland Message-ID: <20190531143826.GA25097@redhat.com> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [linux-lvm] A couple of questions on locking library 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: Shawn Guo Cc: linux-lvm@redhat.com, Zdenek Kabelac On Fri, May 31, 2019 at 03:13:39PM +0800, Shawn Guo wrote: > Hi David, Zdenek, > > Comparing to stable-2.02 branch, I noticed that there are significant > changes around locking infrastructure on master branch. I have a > couple of questions regarding to these changes. > > 1. I see External Locking support was removed as part of clvmd > removal. What's the reason for dropping External Locking support? I'm > asking because we are investigating the possibility to use hardware > assisted locking for cluster, in form of External Locking extension. You could create other multi-host locking mechanisms in lvmlockd. There are currently two, see lvmlockd-dlm.c and lvmlockd-sanlock.c. Dave