From: brem belguebli <brem.belguebli@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] CLVMD Simple method to get who holds a lock in a cluster
Date: Mon, 27 Jul 2009 14:25:15 +0200 [thread overview]
Message-ID: <29ae894c0907270525v63f0a334n464bb49ea60f71cf@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 641 bytes --]
next reply other threads:[~2009-07-27 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 12:25 brem belguebli [this message]
2009-07-27 12:30 ` [linux-lvm] CLVMD Simple method to get who holds a lock in a cluster Christine Caulfield
2009-07-27 12:48 ` brem belguebli
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=29ae894c0907270525v63f0a334n464bb49ea60f71cf@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).