[Linux-cluster] Lockingstatistics

[Mark Hlawatschek]

Hi,

I did some reaserach work about the gfs_tool lockdump output and the decipher 
scripts I found in the cvs tree.
A first summary of my observations can be found here:  
http://www.open-sharedroot.org/documentation/gfs-lockdump-analysis

Any comments are welcome !!

Mark

On Tuesday 16 January 2007 16:30, Robert Peterson wrote:
> David Teigland wrote:
> > On Tue, Jan 16, 2007 at 10:32:32AM +0100, Marc Grimme wrote:
> >> Hello,
> >> is there a way to get a status on which node has which files locked and
> >> in what state?
> >> Background:
> >> We sometimes see processes ending up in deadlocks. And it is always very
> >> difficult to see which lock causes the problem. It would be very
> >> helpfull to get a dump on all the locks held by a given node in
> >> reference to the locked file.
> >
> > In RHEL4 you can dump locks from gfs or the dlm:
> > gfs_tool lockdump <mountpoint>
> > echo "lockspace name" >> /proc/cluster/dlm_locks
> > cat /proc/cluster/dlm_locks
> >
> > The number in type 2 locks is the inode number.
> >
> > Dave
>
> Hey, Marc.  Funny you should ask; I just added those to the FAQ on
> Monday.  See:
>
> http://sourceware.redhat.com/cluster/faq.html#lock_dump_gfs
>
> and
>
> http://sourceware.redhat.com/cluster/faq.html#lock_dump_dlm
>
> Regards,
>
> Bob Peterson
> Red Hat Cluster Suite
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster

-- 
Gruss / Regards,

Dipl.-Ing. Mark Hlawatschek
http://www.atix.de/
http://www.open-sharedroot.org/

**
ATIX - Ges. fuer Informationstechnologie und Consulting mbH
Einsteinstr. 10 - 85716 Unterschleissheim - Germany