I have a SuSE linux nfs client receiving files via
ftp. The ftp process applies a lock to incoming files (which I can see locally). When I mount the receiving directory via NFS from a file server, I cannot see the locks on the file server (I can see them on the cilent just using lsof). The problem appears to not involve ftp--I have replicated with a small perl-based file locking tester script I wrote.
So, the question is: should I be able to see file locks created on the NFS client when I'm on the server looking at the remotely mounted files? Seems like I should be able to. I've read articles from people who say they can with no problems. I've also read postings from admins who say they can't.
Here is the mount fstab entry on the client:
testmw:/usr/local/val/uplo
ad/lftp/re
quests /usr/local/val/upload/ftp nfs rw,bg,hard,intr,tcp,vers=3
,wsize=819
2,rsize=81
92 0 0
Here is the export entry from the server:
/usr/local/val/upload/ftp/
requests vwfe1(sync,no_root_squash,
rw,subtree
_check)
I've experimented with various options on both of these settings.
Server
Linux testmw 2.6.18.2-34-bigsmp #1 SMP Mon Nov 27 11:46:27 UTC 2006 i686 athlon i386 GNU/Linux
testmw:~ # rpm -qf `which rpc.nfsd`
nfs-utils-1.0.10-22
Client:
Linux krusty 2.6.4-52-smp #1 SMP Wed Apr 7 02:11:20 UTC 2004 i686 i686 i386 GNU/Linux
I hand built nfs-utils 1.1.2 for the client from source.
The objective is
mount a filesystem on the client
apply a lock to a file on the client (on an nfs dir) using just a test script that applies a lock
I can then see the lock on the client with lsof
I want to be able to use lsof on the server to see the same lock
Any ideas?