[Linux-cluster] DLM & RedHat Enterprise Linux

[Christos Triantafillou]

Patrick,

Is the query functionality implemented yet?
I defined QUERY in dlmtest.c and I am getting this:
# dlmtest -Q
locking LOCK-NAME EX ...done (lkid = 102da)
Query failed: Invalid argument
unlocking LOCK-NAME...done

Regards,
Christos


>From: Patrick Caulfield <pcaulfie at redhat.com>
>Reply-To: linux clustering <linux-cluster at redhat.com>
>To: linux clustering <linux-cluster at redhat.com>
>Subject: Re: [Linux-cluster] DLM & RedHat Enterprise Linux
>Date: Thu, 01 Jun 2006 13:02:23 +0100
>MIME-Version: 1.0
>Received: from hormel.redhat.com ([209.132.177.30]) by 
>bay0-mc4-f3.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 
>Jun 2006 05:02:31 -0700
>Received: from listman.util.phx.redhat.com (listman.util.phx.redhat.com 
>[10.8.4.110])by hormel.redhat.com (Postfix) with ESMTPid E91BC72E86; Thu,  
>1 Jun 2006 08:02:28 -0400 (EDT)
>Received: from int-mx1.corp.redhat.com 
>(int-mx1.corp.redhat.com[172.16.52.254])by listman.util.phx.redhat.com 
>(8.13.1/8.13.1) with ESMTP idk51C2RXT025641 for 
><linux-cluster at listman.util.phx.redhat.com>;Thu, 1 Jun 2006 08:02:27 -0400
>Received: from pobox.surrey.redhat.com (pobox.surrey.redhat.com 
>[172.16.10.17])by int-mx1.corp.redhat.com (8.12.11.20060308/8.12.11) with 
>ESMTP idk51C2QqF024437 for <linux-cluster at int-mx1.corp.redhat.com>;Thu, 1 
>Jun 2006 08:02:26 -0400
>Received: from [192.168.1.2] (vpn-68-1.surrey.redhat.com [10.32.68.1])by 
>pobox.surrey.redhat.com (8.12.11.20060308/8.12.11) with ESMTP 
>idk51C2ODh016194for <linux-cluster at redhat.com>; Thu, 1 Jun 2006 13:02:25 
>+0100
>X-Message-Info: LsUYwwHHNt1hwMoPuwvRWIu68qUsjYIZZ2SgBHK6+k0=
>Organization: Red Hat
>User-Agent: Thunderbird 1.5 (X11/20051201)
>References: <BAY112-F26E0FD40C60D1BB38527F793900 at phx.gbl>
>X-Enigmail-Version: 0.94.0.0
>X-loop: linux-cluster at redhat.com
>X-BeenThere: linux-cluster at redhat.com
>X-Mailman-Version: 2.1.5
>Precedence: junk
>List-Id: linux clustering <linux-cluster.redhat.com>
>List-Unsubscribe: 
><https://www.redhat.com/mailman/listinfo/linux-cluster>,<mailto:linux-cluster-request at redhat.com?subject=unsubscribe>
>List-Archive: <https://www.redhat.com/archives/linux-cluster>
>List-Post: <mailto:linux-cluster at redhat.com>
>List-Help: <mailto:linux-cluster-request at redhat.com?subject=help>
>List-Subscribe: 
><https://www.redhat.com/mailman/listinfo/linux-cluster>,<mailto:linux-cluster-request at redhat.com?subject=subscribe>
>Errors-To: linux-cluster-bounces at redhat.com
>Return-Path: linux-cluster-bounces at redhat.com
>X-OriginalArrivalTime: 01 Jun 2006 12:02:32.0305 (UTC) 
>FILETIME=[43464610:01C68573]
>
>Christos Triantafillou wrote:
> >> You mean that the users are using the default lockspace even
> >> though the lockspace that was created by root was a different one?
> >> Strange.
> >
> > yes, that is what is happenning:
> > I have got these devices:
> > crwxrwxrwx   1 root root 10, 62 May 30 21:32 dlm-control
> > crwxrwxrwx   1 root root 10, 61 May 30 21:32 dlm_default
> > crwxrwxrwx   1 root root 10, 61 May 31 17:03 dlm_kobe
> >
> > and I can now run all the user tests as a non-root user:
> > # lstest -o -r -l default
> > Opening lockspace default
> > locking LOCK-NAME EX ...ast called, status = 0, lkid=103a8
> > unlocking LOCK-NAME...ast called, status = 65538, lkid=103a8
> >
> > but
> > # lstest -o -l default
> > Opening lockspace default
> > locking LOCK-NAME EX ...ast called, status = 0, lkid=100cf
> > unlocking LOCK-NAME...ast called, status = 65538, lkid=100cf
> > Releasing ls default
> > release ls: Operation not permitted
> >
>
>It looks like the default lockspace didn't get released when the all
>references to it disappeared (unless you have something holding it open!).
>
>I'm not sure how that might happen
>
>--
>
>patrick
>
>--
>Linux-cluster mailing list
>Linux-cluster at redhat.com
>https://www.redhat.com/mailman/listinfo/linux-cluster