On Wed, Apr 04, 2001 at 12:45:18PM +0200, Michael Meskes wrote: > Is anyone running an NFS mounted partition where file locking correctly > works? yup for ages now. > I have a server running potato with kernel 2.2.18 and nfs-kernel-server and > a client with kernel 2.4.2 and sid. My client mounts the partition but > cannot do file locking. For instance mutt is not able to write a mailbox > (shouldn't it be using dot locking anyway?). It just says mailbox is read > only. mutt uses both (i think) dotlocking and fcntl (or whatever its called) locking. i think dotlocking alone may lead to race conditions since there is potentially a delay before the lockfile appears on the server and to other clients due to caching. > Unfortunately I wasn't able to find some docs helping me so far. ive never really had any problems since dumping the crummy userland nfs daemons. even with pre-2.2.18's broken NFS. all i have had to do is make sure nfs-common, portmap and nfs-kernel-server are all started correctly and in the right order (which happens on a default install of these packages if you didn't fiddle with the symlinks prior). also make sure you have NFSv3 support compiled into both kernels, any clients should be running a newwer mount then what is in potato. also make sure that the client and server all have hosts.allow entries for each other to access statd. make sure the lockd is running on all machines, and no firewalling is in the way. thats all i ever had to do, i currently have a 2.2.19 server, with 2.2.19 and 2.4.3 clients, locking works perfectly. the only time i ever had problems with locking was a long time ago with powerpc rsycn kernel trees, if i used the make pmac-config target the .config would end up screwed so CONFIG_LOCKD was turned off (this is normally turned on when you turn on NFS, you never see this option in config menus). in this case it was simply to stop using the obsolete, uneeded and broken make pmac-config target anymore. (i think powerpc at one point had issues with lockd too. they have obviously been fixed since that 2.2.19 client is a powerpc) -- Ethan Benson http://www.alaska.net/~erbenson/
Attachment:
pgpENaxiiNBdm.pgp
Description: PGP signature