Hi Drew,You might want to try [EMAIL PROTECTED] - network locking is an NFSv3 technology. For NFSv4 there's no need for lockd as locking is part of the NFSv4 protocol.
I'm trying to track down some performance issues on a Solaris 10 U5 nfs server, and having some difficulties with it. What I'm specifically trying to find out right now is what files are being locked via lockd - and how long each individual lock operation is taking.
DTrace would be a good tool.
Anyone have any idea what the right DTrace incantation might be to get this information?
IIRC lockd does very little aside from opening up some listeners and handing them off to a pool of kernel threads. All the action occurs inside the kernel including handling of incoming lock requests. The Kernel Lock Manager is currently part of the 'closed' source so it's not something that can be made public today.
Ultimately the klm calls VOP_FRLOCK() and VOP_SHRLOCK() so tracing those calls should give you visibility of how locks are being handled. These macros call their fop_foo() equivalents such as fop_frlock().
-- Peter
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ dtrace-discuss mailing list [email protected]
