Ubuntu
linux package

  1. Bug #974664
  2. Comment #54

Comment 54 for bug 974664

Revision history for this message
In , Tim (tim-redhat-bugs) wrote :

(In reply to comment #23)
> By default, nfs.ko does flock() emulation on top of POSIX locks.
>
> If you find that programs that use flock don't work properly on top of NFS, you
> can mount with local_lock=flock and that will disable that behavior. Of course,
> no other client will be aware of flock locks at that point...

In which case this may still be a problem. I mount with local_lock=none

The only way to get correct flock() emulation would be to silently reopen the FD as writable on the NFS server if LOCK_EX is requested (but presumably keep letting the VFS believe it's read-only). flock() will cheerfully let you exclusive-lock a read-only FD. Ick :-)