nfsd: plock failed

[Alex Hose]

I am facing a problem in our D370 server. I wanted to mount one remote dir . But it was not able to mount that remote dir.Then I checked remote machine's /etc/exports file. It was perfectly ok. /etc/rc.config.d/nfsconf has proper entries for nfsserver. Atlast I have seen nfsd is not running. When I tried to run that process then it is showing following error :
nfsd: plock failed: Not enough space

What should I do?

[Patrick Wallek · Accepted solution]

Here are a couple of documents from the TKB that may help you:

http://us-support.external.hp.com/cki/bin/doc.pl/sid=cc25f5c91337bac1a3/screen=ckiDisplayDocument?docId=200000050014316

http://us-support.external.hp.com/cki/bin/doc.pl/sid=cc25f5c91337bac1a3/screen=ckiDisplayDocument?docId=200000024614186

[Andy McDade]

Any chance of putting some of the content for these links in this thread? When I click on them I get the following message:

Your User ID and Password are not found at this IT Resource Center site. Please check and re-enter your User ID and Password. Also, be sure you are using the site where you registered: Americas/Asia-Pacific customers should use the Americas/Asia-Pacific site, and European customers should use the European site.
If you do not have a User ID and Password for the IT Resource Center, please register. European support customers should register at the European site.

Obviously I have an ITRC userid or I wouldn't be able to post here.

[T G Manikandan]

This is the document.
Even I am not able to view it

Problem Description

Some of my applications are taking up memory. I'm receiving
the following error:

plock failed not enough space when starting the nfs daemons.

I modified my kernel parameters and would like to know which
ones could have influenced the memory?

Configuration Info

Operating System -HP-UX
Version -10.20
Hardware System - HP 9000
Series -E25

Solution

unlockable_mem defines the minimum amount of memory that is to always
remain available for virtual memory management and system overhead.
Increasing the amount of unlockable memory decreases the amount of
lockable memory because:

Total available system memory - unlockable_mem = lockable memory

Specify unlockable_mem in 4-Kbyte pages. Note that current amounts of
available and lockable memory are listed along with the physical page
size in startup messages, which you can view later by running
/etc/dmesg.

If the value for unlockable_mem exceeds available system memory, it is
set equal to available memory (reducing lockable memory to zero).

Any call that requires lockable memory may fail if the amount of
lockable memory is insufficient. Note that lockable memory is available
for virtual memory except when it is locked.

Lockable memory is used for:

Process images and overhead locked using the plock() system call
(see plock(2)).

Shared memory segments locked with the SHM_LOC command of the
shmctl() system call (see shmctl(2)).

Miscellaneous dynamic kernel data structures used by the shared
memory system and some drivers.

Related Parameters:

unlockable_mem must always be less than the total amount of available
memory in the system.

HP Only Info