On Wednesday 05 May 2010 8:52:45 am Octavian Rasnita wrote: > I have a FreeBSD 7.2-RELEASE-p6 FreeBSD 7.2-RELEASE-p6 #0: Wed Jan 6 > 00:43:01 UTC 2010 that works as an NFS server, with the following line in > /etc/exports: [...] > Both these servers mount the local /srv/data directory to the one exported > by the server that uses FreeBSD using NFS I use the following line in > /etc/fstab (where 10.50.28.90 is the IP of the server that runs the NFS > server): > > 10.50.28.90:/mnt/opt/ebroker /srv/data nfs rw,sync 0 0 > > Right after I reboot any of these 2 servers, the /srv/data directory is > mounted correctly and I can access the files and directories under it, but > after a certain period of time (that can be minutes, hours or even days), > the console freezes if I use the command: > > $ cd /srv/data > or > $ ls -l /srv/data > > ...and I can't even break it with Ctrl+C. > The single workaround (for a while) is to reboot the NFS client machine, > which is not an acceptable solution. > > I have tried to add the "hard" and "intr" options in the line from > /etc/fstab that mounts /srv/data, hoping that at least I will be able to > break that frozen directory with Ctrl+C, but nothing changed. [...]
I may be experiencing a similar issue. On the clients, does dmesg say things like nfs: server <server> not responding, still trying nfs: server <server> OK I have been troubleshooting this for the better part of a week and have gotten nowhere. Changing all of the mounts to use nfs4 seems to fix the problem, but I have to use nfs3 for one of the mounts (otherwise I get into ID mapping hell). There is an open bug in (I think) nfs-kernel-server that describes similar symptoms, but offers no solution. Is anyone else experiencing this? MM -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201005051121.20014.anonymous.jon...@gmail.com
