Date: Tue, 5 Dec 2006 14:13:05 +0100 From: Thierry Lacoste <th.lacoste@wanadoo.fr> To: freebsd-questions@freebsd.org Subject: SOLVED : nfs issue after client crash Message-ID: <200612051413.05560.th.lacoste@wanadoo.fr>
next in thread | raw e-mail | index | archive | help
Somebody gave me the answer to my question http://lists.freebsd.org/pipermail/freebsd-questions/2006-November/135179.html I'm posting it in case somebody hits a similar problem. >I have a bunch of Ubuntu clients which mount /home at boot time from a >FreeBSD 6.1 NFS server. > >When a client crashes it won't mount /home at boot. >In that case, trying to mount manually gives "can not read super bloc". > >The client still appears in the "showmount"output of the server. > >Sometimes /home will be mounted after the second reboot but sometimes >not even after several reboots (I haven't been able to find a regular >pattern here). >If I restart the NFS server or just wait long enough (e.g. one day) >everything is OK. By default the client is using NFS/TCP and when it crashes it does not release the TCP connection. It appears that the server then refuses to establish a second connection. On the linux clients I'm now using "mount -o udp /home" in my rc.local and everything seems fine. Regards, Thierry.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200612051413.05560.th.lacoste>