linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: brem belguebli <brem.belguebli@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] CLVMD Simple method to get who holds a lock in a  cluster
Date: Mon, 27 Jul 2009 14:48:33 +0200	[thread overview]
Message-ID: <29ae894c0907270548i53245d96jba3ae51147beddde@mail.gmail.com> (raw)
In-Reply-To: <4A6D9E00.2090600@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]

Hi Chrissie,

RHEL 5.3 shipped  cman-2.0.9-1.el5, any updated RPM available for RHEL 5.3 ?

Thanks

Brem



2009/7/27, Christine Caulfield <ccaulfie@redhat.com>:
>
> On 07/27/2009 01:25 PM, brem belguebli wrote:
>
>> Hi,
>> In a clustered environment, without GFS, we plan to use CLVMD exclusive
>> activation of VG's in order to prevent a VG to be activated on more than
>> 1 node at a time.
>> I've been looking for how to check who holds a lock for a given VG but I
>> could'nt find no suitable way to do it.
>> The only way was to activate debug ( mount -t debugfs debug /debug) and
>> cat /debug/dlm/clvmd_locks.
>> Is there a way to request dlm (via dlm_tool) to get the lock holding
>> node or via  any LVM command.
>> Regards
>>
>>
>>
> Depending on the version you have dlm_tool will show you who holds the
> lock. But all it does is use the same debugfs interface you've already
> mentioned :-)
>
> Chrissie
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

[-- Attachment #2: Type: text/html, Size: 2050 bytes --]

      reply	other threads:[~2009-07-27 12:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 12:25 [linux-lvm] CLVMD Simple method to get who holds a lock in a cluster brem belguebli
2009-07-27 12:30 ` Christine Caulfield
2009-07-27 12:48   ` brem belguebli [this message]

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=29ae894c0907270548i53245d96jba3ae51147beddde@mail.gmail.com \
    --to=brem.belguebli@gmail.com \
    --cc=linux-lvm@redhat.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).