* [linux-lvm] CLVMD Simple method to get who holds a lock in a cluster
@ 2009-07-27 12:25 brem belguebli
2009-07-27 12:30 ` Christine Caulfield
0 siblings, 1 reply; 3+ messages in thread
From: brem belguebli @ 2009-07-27 12:25 UTC (permalink / raw)
To: linux-lvm
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] CLVMD Simple method to get who holds a lock in a cluster
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
0 siblings, 1 reply; 3+ messages in thread
From: Christine Caulfield @ 2009-07-27 12:30 UTC (permalink / raw)
To: LVM general discussion and development
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] CLVMD Simple method to get who holds a lock in a cluster
2009-07-27 12:30 ` Christine Caulfield
@ 2009-07-27 12:48 ` brem belguebli
0 siblings, 0 replies; 3+ messages in thread
From: brem belguebli @ 2009-07-27 12:48 UTC (permalink / raw)
To: LVM general discussion and development
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-07-27 12:48 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).