From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kirill Kuvaldin Subject: Re: GFS2 file locking issues Date: Wed, 11 Feb 2009 17:37:11 +0300 Message-ID: <2d42915c0902110637o2c0a88c7h72b280b972a6162e@mail.gmail.com> References: <2d42915c0902110255k3c0741a9s6830765bce6be052@mail.gmail.com> <20090211133648.GA10273@fogou.chygwyn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: linux-cluster@redhat.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: steve@chygwyn.com Return-path: Received: from fk-out-0910.google.com ([209.85.128.189]:34699 "EHLO fk-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753971AbZBKOhN (ORCPT ); Wed, 11 Feb 2009 09:37:13 -0500 In-Reply-To: <20090211133648.GA10273@fogou.chygwyn.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Feb 11, 2009 at 4:36 PM, wrote: > Hi, > > On Wed, Feb 11, 2009 at 01:55:08PM +0300, Kirill Kuvaldin wrote: >> Hi, >> >> I'm trying to understand how the FS locking mechanism should work. >> >> I'm running a clustered GFS2 across two nodes, each node is a Xen domU. >> To check if locking works correctly I wrote the simple perl script below. >> Basically the script opens a file, locks it to prevent others from >> writing into it, writes 20 lines into it, then unlocks and closes. >>i > > It should be exactly the same on GFS and GFS2, after all the code for > flock is almost identical between the two. What mount options did you > use? No specific options used, just mount -t gfs2 /dev/gfsc/lvol0 /gfs2... > Which lock manager are you using - I presume lock_dlm? > Yes, the FS was created using to be used with lock_dlm. I'm not sure if it is actually used for GFS2. How can I check that? Kirill