From owner-freebsd-net  Sun Mar 19 12:41:12 2000
Delivered-To: freebsd-net@freebsd.org
Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9061637B5AD; Sun, 19 Mar 2000 12:41:03 -0800 (PST)
	(envelope-from toasty@celery.dragondata.com)
Received: (from toasty@localhost)
	by celery.dragondata.com (8.9.3/8.9.3) id OAA26182;
	Sun, 19 Mar 2000 14:40:55 -0600 (CST)
	(envelope-from toasty)
From: Kevin Day <toasty@dragondata.com>
Message-Id: <200003192040.OAA26182@celery.dragondata.com>
Subject: Re: NFS disconnecting - HELP
To: nicole@unixgirl.com (Nicole Harrington.)
Date: Sun, 19 Mar 2000 14:40:55 -0600 (CST)
Cc: freebsd-isp@FreeBSD.ORG, freebsd-net@FreeBSD.ORG
In-Reply-To: <XFMail.000319123654.nicole@unixgirl.com> from "Nicole Harrington." at Mar 19, 2000 12:36:54 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> 
> 
>  Greetings all
>  I have two servers running FreeBSD 3.4-STABLE connected via NFS via
> independedent Intel pro 10/100 Nic cards (using a 10.0.0.1 type of network) and
> an intel switch. The directory structure is rather large but the traffic should
> not be that heavy. I was rather suprised to start seeing the disconnection
> notices below.
>  I have had similar problem with NFS locking up on large/deep directories,
> however I was able to correct it by lowing the mount MTU to 1250 which didn't
> seem to make any difference on this system.
> 
>  Any advice on what to try would be greatly appreciatted!
>  Please CC me in response.
> 
> 
>   Thanks!
> 
>     Nicole
> 
> Mar 17 15:52:11 www /kernel: nfs server pi.p.com:/home/web/WWW: not responding
> Mar 17 15:52:12 www /kernel: nfs server pi.p.com:/home/web/WWW: is alive again
> Mar 17 15:52:16 www /kernel: nfs server pi.p.com:/home/web/WWW: not responding
> Mar 17 15:52:16 www /kernel: nfs server pi.p.com:/home/web/WWW: is alive again
> Mar 17 15:52:54 www /kernel: nfs server pi.p.com:/home/web/WWW: not responding
> Mar 17 15:52:54 www /kernel: nfs server pi.p.com:/home/web/WWW: is alive again
> Mar 17 15:56:20 www /kernel: nfs server pi.p.com:/home/web/WWW: not responding
> Mar 17 15:56:20 www /kernel: nfs server pi.p.com:/home/web/WWW: is alive again
> Mar 17 16:03:48 www /kernel: nfs server pi.p.com:/home/web/WWW: not responding
> Mar 17 16:03:48 www /kernel: nfs server pi.p.com:/home/web/WWW: is alive again
> Mar 17 16:04:42 www /kernel: nfs server pi.p.com:/home/web/WWW: not responding
> Mar 17 16:04:43 www /kernel: nfs server pi.p.com:/home/web/WWW: is alive again
> Mar 17 16:07:59 www /kernel: nfs server pi.p.com:/home/web/WWW: not responding


Mount the nfs filesystem (on the client side) with the '-d' option. I'm
actually working on a fix for this, though.

Example:

nfs:/home       /home           nfs     rw,-b,-d,noatime        1       1


Kevin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message