From owner-freebsd-questions@FreeBSD.ORG Tue May 2 23:50:15 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62ED916A402 for ; Tue, 2 May 2006 23:50:15 +0000 (UTC) (envelope-from dpkirchner@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 913DB43D4C for ; Tue, 2 May 2006 23:50:14 +0000 (GMT) (envelope-from dpkirchner@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so8274uge for ; Tue, 02 May 2006 16:50:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=mE90wyE3vkNTZNqgg2++lF2ywT0Pg7dLHbDjGeGDieFQizjQNv+fgjnWF+9U9Yqm415Rz2nzFpcSPRgq5ozsdDyA/oSNUAiNrpplOt+l9Nnyop6R5pqXrPj9J8FQyVHM6he/5rU+0x8G3lSfCu8zk4dp45KTmWDc4LI2BchenB8= Received: by 10.78.47.9 with SMTP id u9mr14761huu; Tue, 02 May 2006 16:50:13 -0700 (PDT) Received: by 10.78.13.2 with HTTP; Tue, 2 May 2006 16:50:13 -0700 (PDT) Message-ID: <35c231bf0605021650q5d386f4bi65ec24bb1cc9a6e2@mail.gmail.com> Date: Tue, 2 May 2006 16:50:13 -0700 From: "David Kirchner" Sender: dpkirchner@gmail.com To: "FreeBSD Questions" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Google-Sender-Auth: 72bf9ada145ccd30 Cc: Subject: NFS server not responding, new in 6.0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 23:50:15 -0000 We recently replaced FreeBSD 4.5 with 6.0-RELEASE on a pair of servers. One of the servers runs rsync to copy its contents to the other server, over a NFS mount. Everything worked just fine under 4.5, but with 6.0, we're seeing dozens of these errors every rsync: May 2 14:00:59 xxx1 kernel: nfs server xxx2:/usr: not responding The rsync does eventually complete successfully. The NFS client system uses the em0 driver on a gigabit port, and the NFS server system uses the fxp0 driver on a 100Mbit/full duplex port. The client system doesn't come close to 100Mbit during the rsync (or otherwise) -- more like 5Mbit. Neither server is what I'd consider "busy" -- they're actually basically idle unless this script or some crons are running. We're using NFSv3 soft, interruptable mounts. We've tried using TCP and UDP, and have tried different -r and -w sizes, up to 32768 each. We've trie= d it with and without nfsiod. We haven't tried changing the mount_nfs -D option, because that seems like it would only serve to mask the real problem, whatever that is. a) Is this a real problem, or simply a reporting problem? What exactly is i= t reporting if it's not a real problem? b) If you've had this trouble before, what settings have you used to fix it= ? Another issue is we're not seeing the usual "is alive again" message you'll usually see when the server becomes unavailable and then returns. I searched the PRs before posting this, but if there's a PR you know about I could add a followup message to it. If you need other info, I can provide that as well.