Date: Wed, 02 Dec 1998 09:10:21 +0000 From: Dom Mitchell <dom@phmit.demon.co.uk> To: cjclark@home.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS problems... Message-ID: <E0zl8Ig-0000Wy-00@voodoo.pandhm.co.uk> In-Reply-To: "Crist J. Clark"'s message of "Tue, 01 Dec 1998 20:28:28 EST" <199812020128.UAA00551@cc942873-a.ewndsr1.nj.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1 December 1998, "Crist J. Clark" proclaimed: > Dom Mitchell wrote, > > % grep /home /etc/fstab > > admin:/export/home /home nfs rw,-i,-3,-T 0 0 > [snip] > > It's running on a 100BaseT switched network to a Solaris 2.6 server. > > Should you be using the '-T' flag with the Solaris server? I don't see why not. NFSv3 is supposed to use tcp AFAIK. > > I realise that this isn't enough to go on for solving the problem. What > > other things can I try when the /home mount gets hung again? Can I > > force a crash dump to take a closer look? > > Can you 'umount -f admin:/export/home'? Naw, it just hung saying "server not responding" again. :-( I've managed to cure my problems by switching back to nfsv2 and turning off the new access cache, in the meantime. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator ``Those who do not understand Unix are condemned to reinvent it, poorly.'' -- Henry Spencer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0zl8Ig-0000Wy-00>