Re: NFS locking and linux NFS server
Hi! Dan Nelson writes: > Are you running statd and lockd (in rc.conf, rpc_statd_enable="YES" and > rpc_lockd_enable="YES")? Make sure that "rpcinfo localhost" and "rpcinfo > otherhost" both show "nlockmgr" and "status" services. it was missing nfs_client_enable="YES" Thanks everyone for the answers! Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NFS locking and linux NFS server
In the last episode (Mar 25), Christoph Egger said: > Hi all! > > I have a Linux Host (2.6.32 kernel, Debian stable) providong NFS > shares. Locking files on that share works fine for linux clients [0] > while it fails on a freebsd 9.0-STABLE system. The interwebs indicate > there have been problems witha buggy linux implementation back in 2006 > but no more hits for that problem in recent times so I assume it's > fixed? > > root@freebsd /mnt/ > 11:27 0 # kldstat -v | grep nfs > 341 nfscommon > 386 nfslockd > 344 nfsd > 385 nfssvc > 342 nfs > 343 nfscl > 384 nfslock > > > > > > root@freebsd /mnt/ > 11:28 0 # flock test -c ls > flock: test: Operation not supported > > root@freebsd /mnt/ > 11:31 0 # mount | grep nfs > 10.70.255.8:/home/ on /mnt/ (nfs) Are you running statd and lockd (in rc.conf, rpc_statd_enable="YES" and rpc_lockd_enable="YES")? Make sure that "rpcinfo localhost" and "rpcinfo otherhost" both show "nlockmgr" and "status" services. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NFS locking and linux NFS server
Hi! Da Rock writes: > On 03/25/12 23:59, Christoph Egger wrote: >> Hi all! >> >>I have a Linux Host (2.6.32 kernel, Debian stable) providong NFS >> shares. Locking files on that share works fine for linux clients [0] >> while it fails on a freebsd 9.0-STABLE system. The interwebs indicate >> there have been problems witha buggy linux implementation back in 2006 >> but no more hits for that problem in recent times so I assume it's >> fixed? >> >> root@freebsd /mnt/ >> 11:27 0 # kldstat -v | grep nfs >> 341 nfscommon >> 386 nfslockd >> 344 nfsd >> 385 nfssvc >> 342 nfs >> 343 nfscl >> 384 nfslock >> >> root@freebsd /mnt/ >> 11:28 0 # flock test -c ls >> flock: test: Operation not supported >> >> root@freebsd /mnt/ >> 11:31 0 # mount | grep nfs >> 10.70.255.8:/home/ on /mnt/ (nfs) > > This may or may not be helpful, but I can't think of anything else at > this time: what version NFS on both sides? NFSv3 on both sides Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NFS locking and linux NFS server
On 03/25/12 23:59, Christoph Egger wrote: Hi all! I have a Linux Host (2.6.32 kernel, Debian stable) providong NFS shares. Locking files on that share works fine for linux clients [0] while it fails on a freebsd 9.0-STABLE system. The interwebs indicate there have been problems witha buggy linux implementation back in 2006 but no more hits for that problem in recent times so I assume it's fixed? root@freebsd /mnt/ 11:27 0 # kldstat -v | grep nfs 341 nfscommon 386 nfslockd 344 nfsd 385 nfssvc 342 nfs 343 nfscl 384 nfslock root@freebsd /mnt/ 11:28 0 # flock test -c ls flock: test: Operation not supported root@freebsd /mnt/ 11:31 0 # mount | grep nfs 10.70.255.8:/home/ on /mnt/ (nfs) This may or may not be helpful, but I can't think of anything else at this time: what version NFS on both sides? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
