Locking on NFS-mounted directory (Mac OS X client)

[Kannan Goundan]

NFS server: Linux 2.4.20 (i686)
NFS client: Mac OS 10.4 (PowerPC)

Using Bazaar 1.6.1 on the Mac machine.

In a non-NFS-mounted directory, everything seems to work fine.  In an NFS-mounted directory, "bzr init" (and every other command I try) gives me the following error:

bzr: ERROR: Could not acquire lock "[Errno 45] Operation not supported"
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/bzrlib/lock.py:79: UserWarning: lock on <open file u'/private/var/automount/s/kannan/Temp/.bzr/checkout/dirstate', mode 'wb+' at 0x2012698> not released warn("lock on %r not released" % self.f)
Exception exceptions.IOError: (45, 'Operation not supported') in <bound method _fcntl_WriteLock.__del__ of <bzrlib.lock._fcntl_WriteLock object at 0x200cb10>> ignored
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/bzrlib/lockable_files.py:116: UserWarning: LockableFiles(<bzrlib.transport.local.LocalTransport url=file:///private/var/automount/s/kannan/Temp/.bzr/checkout/>) was gc'd while locked warnings.warn("%r was gc'd while locked" % self)

I searched online for info and found that the problem may be that NFS locking isn't working.  However, I'm not sure how to verify whether that is my issue or not.  The NFS server is running "rpc.statd" and "[lockd]" (the manpage for "rpc.lockd" says that it normally isn't necessary as long as "[lockd]" is running).  The client machine is running "rpc.statd" and "rpc.lockd -w".

Is there something I can do to diagnose the problem further?  The "lockfile" program that comes with Procmail doesn't report any errors, though maybe that uses a different locking mechanism?

Kannan