Red Hat Bugzilla – Bug 1017477
manpage for NFS(5) implies that local_lock is not supported in RHEL 6, when it is
Last modified: 2014-10-14 00:32:03 EDT
The NFS(5) manpage states:
Specifies whether to use local locking for any or both of the flock and
the POSIX locking mechanisms. mechanism can be one of all, flock,
posix, or none. This option is supported in kernels 2.6.37 and later.
It appears that this mechansim has been back-ported into the 2.6.32 kernel
in e.g. linux-2.6.32-220.el6/fs/nfs/super.c
So local_lock does in fact work in, I believe, all RHEL6 releases
nfs(5) man page is part of the nfs-utils package
[root@dhcp12-241 nfs-utils-1.2.3]# man ./utils/mount/nfs.man | grep local_lock=mechanism -A 10
Specifies whether to use local locking for any or both of the flock and the POSIX locking mechanisms. mechanism can be one of all, flock,
posix, or none.
The Linux NFS client provides a way to make locks local. This means, the applications can lock files, but such locks provide exclusion only
against other applications running on the same client. Remote applications are not affected by these locks.
If this option is not specified, or if none is specified, the client assumes that the locks are not local.
If all is specified, the client assumes that both flock and POSIX locks are local.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.