mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: steve@chygwyn.com
To: Kirill Kuvaldin <kirill.kuvaldin@gmail.com>
Cc: linux-cluster@redhat.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: GFS2 file locking issues
Date: Wed, 11 Feb 2009 17:18:16 +0000	[thread overview]
Message-ID: <20090211171816.GA14516@fogou.chygwyn.com> (raw)
In-Reply-To: <2d42915c0902110637o2c0a88c7h72b280b972a6162e@mail.gmail.com>

Hi,

On Wed, Feb 11, 2009 at 05:37:11PM +0300, Kirill Kuvaldin wrote:
> On Wed, Feb 11, 2009 at 4:36 PM,  <steve@chygwyn.com> 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
cat /proc/mounts

It should be listed in the options. That will also tell you if localflocks
has been set as well. We do know of a bug in the GFS/GFS2 flock code though,
it ought to be using an interruptible wait and it doesn't at the moment.
Otherwise I don't know of any other issues.

Which kernel version are you using?

Steve.


  reply	other threads:[~2009-02-11 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 10:55 Kirill Kuvaldin
2009-02-11 13:36 ` steve
2009-02-11 14:37   ` Kirill Kuvaldin
2009-02-11 17:18     ` steve [this message]
2009-02-11 17:57       ` Kirill Kuvaldin
2009-02-12 11:22         ` steve

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=20090211171816.GA14516@fogou.chygwyn.com \
    --to=steve@chygwyn.com \
    --cc=kirill.kuvaldin@gmail.com \
    --cc=linux-cluster@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®