When I have upgraded my system to FreeBSD 6 Stable, I found windows client have hanged when it browsed a share which is a nfs mount fs. However, FreeBSD 5.4 Stable does not have this kind of problem with the same environment. On the other hand, there is no any problem when I access files on nfs fs in console. In addition, I have reinstalled all samba related/depended freebsd ports by "portupgrade -cCuvfrR samba". There is no any nfs related error in system log files. PS: Samba server is in a freebsd jail but I found it did not affect the result. (samba running outside also has this problem) When I browse other shares (not on nfs) on the samba server, there is no any problems NFS server: Debian unstable kernel: 2.6.14-1-686-smp NFS package: nfs-kernel-server-1.0.7-3 /etc/exports: /home/d x.x.x.x (sync,rw,no_root_squash) NFS client: FreeBSD 6 Stable (samba server) /etc/fstab ym78123.ym.edu.tw:/home/x /home/js/x/x nfs rw,nfsv3,soft 0 ps output has showed that smbd processes are in 'lockd' state. client: windows xp sp1/sp2 How-To-Repeat when I browsing a share which is nfs mount fs
Samba uses fcntl locks calls on files being accessed. These are expected to work correctly, even on a remote mounted filesystem. It seems as though there may be a problem with fcntl locks on either the nfs client or server to cause an accessing process to hang. Jeremy.
To verify Jeremy's assumption you might try to set 'posix locking = no' in the share definition. If this helps you still need to look into the locking problem. Volker
When I set 'posix locking = no', the file share works fine. I think Jeremy is right. Maybe there is a problem in file locking.
Created attachment 1567 [details] partial error log
Comment on attachment 1567 [details] partial error log error log before I set 'posix locking = no'
Eric, probably best to follow up with the FreeBSD NFS client maintainers. Closing out this bug.