From: Matthias Reichling (reichling@rz.uni-wuerzburg.de)
Date: Tue Jan 17 2006 - 02:58:03 EST
Adding no_subtree_check did the trick. insecure_locks isn't sufficient.
Thanks to Ken Kleiner!
Matthias Reichling
> Hello,
>
> our NFS server runs under SLES 9 (kernel 2.6.5-7.244-smp). On the NFS
> client under Tru64 5.1B-3 we have a problem with file locking: If I edit a
> file on the NFS server with vi, the warning "FILE BEING MODIFIED BY ANOTHER
> PROCESS" appears. If I change the permissions of the according directory
> with chmod o+x, all works fine. From the Linux NFS-HOWTO I found that I
> have to export the file system with the insecure_locks option. However,
> this doesn't work for me. I also used the flag insecure, but no effect. At
> the moment in /var/lib/nfs/xtab on the server there are the flags
> rw,sync,wdelay,hide,nocrossmnt,insecure,no_root_squash,no_all_squash,subtre
>e_check,insecure_locks,acl ,mapping=identity,anonuid=65534,anongid=65534
> (of course I umounted the file system on the client and mounted it again
> after exporting with the new options).
>
> Any ideas?
>
>
> Regards,
>
> Matthias Reichling
> reichling@rz.uni-wuerzburg.de
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:27 EDT