[Summary] "No locks available" NFS error?

From: Xavier Mertens (xavier@rootshell.be)
Date: Tue Oct 08 2002 - 04:24:41 EDT

• Next message: McGuinness Todd: "sem-xxx system params."
• Previous message: Carl Bavington: "ACS Controller Software Patchs for V8.6"
• In reply to: Xavier: ""No locks available" NFS error?"
• Next in thread: Adam Bentley: "INN 2.3.3 on Tru64 4.0f"
• Reply: Adam Bentley: "INN 2.3.3 on Tru64 4.0f"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

My problem solved automagically after several stop/start of both NFS client
and server!?

Also thanks to Johan who gave me the following tip:

Usually this is a NFS server-side problem (ie Solaris equiv of rpc.lockd
activity)

In the off-chance it's client-side related, check the following
#dbx -k /vmunix
(dbx)pd flckinfo

and if you get close to the 10000 default of
/sbin/sysconfig -q vfs nlock_record

you can increase it online with

/sbin/sysconfig -r vfs nlock_record=12000

Regards,

Xavier

--
http://www.rootshell.be
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sb20293A2058554E494Csnlbxq'|dc
On Tue, 8 Oct 2002, Xavier wrote:
> Hi Gurus,
> 
> I've a Tru64 (5.1) NFS client which mounts a filesystem from a Solaris (8)
> NFS server. Everything runs well but this morning (after a reboot of the
> Solaris box), i had tons of:
> 
> No locks available
> 
> Errors generated by the application which used the NFS filesystem.
> 
> Any idea?
> 
> --
> http://www.rootshell.be
> echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sb20293A2058554E494Csnlbxq'|dc
> 

• Next message: McGuinness Todd: "sem-xxx system params."
• Previous message: Carl Bavington: "ACS Controller Software Patchs for V8.6"
• In reply to: Xavier: ""No locks available" NFS error?"
• Next in thread: Adam Bentley: "INN 2.3.3 on Tru64 4.0f"
• Reply: Adam Bentley: "INN 2.3.3 on Tru64 4.0f"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:55 EDT