From owner-freebsd-stable Wed Dec 2 17:15:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03832 for freebsd-stable-outgoing; Wed, 2 Dec 1998 17:15:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03805 for ; Wed, 2 Dec 1998 17:14:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA08949; Wed, 2 Dec 1998 14:58:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812022258.OAA08949@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dom Mitchell cc: cjclark@home.com, freebsd-stable@FreeBSD.ORG Subject: Re: NFS problems... In-reply-to: Your message of "Wed, 02 Dec 1998 09:10:21 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 14:58:53 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. Rubbish. Definitely try using TCP mounts here; there's empirical evidence that tends to indicate that when working with Solaris servers there's a reasonable chance of either dropping response packets or having response packets "lost" in some other fashion. > > > 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. Since the access cache only affects v3 mounts, turning it off really just amounts to the waving of a dead chicken here. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message