From: Kirill Kuvaldin <kirill.kuvaldin@gmail.com>
To: steve@chygwyn.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 20:57:12 +0300 [thread overview]
Message-ID: <2d42915c0902110957i6c2f645cyfda572a64f19de64@mail.gmail.com> (raw)
In-Reply-To: <20090211171816.GA14516@fogou.chygwyn.com>
On Wed, Feb 11, 2009 at 8:18 PM, <steve@chygwyn.com> wrote:
> cat /proc/mounts
/dev/mapper/gfsc-lvol0 /gfs2 gfs2 rw,hostdata=jid=0:id=720897:first=1 0 0
I also tried mounting explicitly specifying lockproto=lock_dlm, but it
didn't help.
Is my understanding of locking correct after all? Is that the case if
the process makes flock on a file, no other processes including ones
running on other cluster nodes could obtain a lock until the first
writer releases it?
>
> 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?
2.6.18-92.el5xen (from CentOS 5.2)
Kirill
next prev parent reply other threads:[~2009-02-11 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 10:55 GFS2 file locking issues Kirill Kuvaldin
2009-02-11 13:36 ` steve
2009-02-11 14:37 ` Kirill Kuvaldin
2009-02-11 17:18 ` steve
2009-02-11 17:57 ` Kirill Kuvaldin [this message]
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=2d42915c0902110957i6c2f645cyfda572a64f19de64@mail.gmail.com \
--to=kirill.kuvaldin@gmail.com \
--cc=linux-cluster@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@chygwyn.com \
/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;
as well as URLs for NNTP newsgroup(s).