NFS Locking: HP-UX/Linux

[Aaron Caine]

I'm having some trouble getting NFS Locking to work between HP-UX and Linux.

I have a Linux file server, running kernel version 2.4, and a HP-UX client (11.00), using AutoFS (NFS PV3).

When my software (IC446, Cadence) on the HP-UX machine tries to execute a flock command, it receives the error ENOLCK. (Meaning that the System lock table is full... too many files have file locks on them etc. [See errno(2) for ENOLCK (HP man pages)].)

Things work with HP-UX client/server, but when I bring the Linux server in, that's when the problems start.

It there an equivilent mount option "no_lock" that exists under Linux for HP-UX? The "no_lock" option, to my understanding, forces the client to not use locking, which in turn, causes flock to return no error, without the file really being locked.

Could anyone shed any light on this?

Thanks in advance... --anc

[Frank Li]

Maybe you can increase the number of lock : "nflocks" of the HP kernel parameter to solve this problem ?

[Paul R. Dittrich]

Is it possible you need to use NFS PV_2_ and use automount instead of AutoFS?

[PT_2]

I have the same problems (on HP-UX from 10.20 to 11.11!), either with or without AutoFS. NFS-V2 is no option for me, 'cause it made big trouble starting with not seeing any nfsshares anymore and such. Anybody has hints, tips or patches??

Ciao
Klaus

[Olav Baadsvik]

Hi,

I would think that the sofware is calling
lockf and not flock.
Even if there was a "lo_lock" option for the
hp-ux mount command I am sure that would
not be a solution to your problem.
When a program uses file-locking you must
assume that it is needed. So disabling
file-locking while the software thinks it is
using it is no solution.
I advise you to write a small c-program
to test the file-locking mechanisme between
Linux and HP-UX.

Regards
Olav

[Brian Hackley]

Folks,

The original posting for this was in July, 2001.

However I have thought about a couple of things. Assuming all the usual attempts have been made to clear up NFS file locking issues, for example as noted in http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xb27a5220af9bd5118ff10090279cd0f9,00.html
then I would suggest trying to use the undocumented -C parameter on the HP-UX rpc.lockd, to see if that clears up the issue. The -C flag is required to correct an HP-UX behavior in certain lock NLM_CANCEL case.

Hope that helps,

-> Brian Hackley