Hi toasters,
i did a bit more testing in the meanwhile.
One thing i now know is, that you can check with "lock status -h [host] -p NLM" for all NFSv2/3 connections for a specific host.
Like that:
======== NLM host lolek 93 0x19396e07:0x001af399 0:0 0 GRANTED (0x627a7e30) 93 0x19396e07:0x001af3a1 0:0 0 GRANTED (0xa8bb5728) 93 0x19396e07:0x001af39b 0:0 0 GRANTED (0xe5bec7f0) 93 0x19396e07:0x001af39a 0:0 0 GRANTED (0x6ecd44d0) 93 0x19396e07:0x001af398 0:0 0 GRANTED (0x64df7e30) 93 0x19396e07:0x001af397 0:0 0 GRANTED (0xaee564d0) 93 0x19396e07:0x001af396 0:0 0 GRANTED (0x9558be30) 84 0x17396d96:0x000911bb 0:0 0 GRANTED (0x8049d980) 84 0x16396d56:0x00003720 0:0 0 GRANTED (0x719b1ef8) 84 0x19396e07:0x001af395 0:0 0 GRANTED (0x916c58b8)
There you have a PID (the first collumn) which can be used to kill locks per PID. "sm_mon -l [host] -p PID" But sadly this PID is not the PID i can see on the client. Has anybody an idea if there is a link between those PID's??
Regards
Jochen
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Bill Holland Sent: Friday, February 15, 2008 10:28 AM To: Willeke, Jochen Cc: toasters@mathworks.com Subject: Re: filer locks on oracle DB
have you set "vol options <volname> nvfail on"?
On Fri, 2008-02-15 at 09:29 +0100, Willeke, Jochen wrote:
Hello toasters,
we have a problem with some of our oracle databases (LINUX, NFS on Filers). Sometimes when the database crashes, we have locks left on
the
filer.
Currently we use "priv set diag; lock status -f" to check for those locks. And with "priv set diag; sm_mon -l [servername]" we can delete all locks for a specific server.
But this is a problem, if one server hosts more DB's than one. Is
there
any possibility to find out which locks are the blocking ones and
delete
only those?
Does anyone have the same problem and has an interesting solution to that?!?
Best Regards and thanks in advance
Jochen