From owner-freebsd-hackers Thu Apr 3 09:36:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA04559 for hackers-outgoing; Thu, 3 Apr 1997 09:36:25 -0800 (PST) Received: from boulder.syr.servtech.com (boulder.syr.servtech.com [206.106.144.94]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA04547 for ; Thu, 3 Apr 1997 09:36:17 -0800 (PST) Received: from boulder.syr.servtech.com (localhost [127.0.0.1]) by boulder.syr.servtech.com (8.8.5/8.8.5) with SMTP id MAA02604; Thu, 3 Apr 1997 12:41:32 -0500 (EST) Message-ID: <3343EBCC.2F1CF0FB@servtech.com> Date: Thu, 03 Apr 1997 12:41:32 -0500 From: Shawn Carey X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: dennis CC: hackers@freebsd.org Subject: Re: 2.2.1R hangs on NFS load References: <3.0.32.19970403120426.00b78860@etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk dennis wrote: > > Using a 21041-based Ethernet card (not at 21040), NFS loads consistently > hang with 2.2.1R (same hardware/system as worked with 2.1.5,6,7). Is > this to be expected? > I've seen problems with NFS on 2.2.1 also, though nothing to hang the machine. We have a remote site connected via 56k that occasionally mounts a filesystem or two. Quite often, an operation (cp, rm, etc) will just hang, or so the reports tell me. Yet another NFS server (on a different 56k to the client) running 2.2-ALPHA serves it's filesystems reliably. I've recently tried mounting with TCP transport, but it hasn't been long enough yet to know if this solves the problem. While we're on the subject of NFS, I see in the release notes for 2.2.1 that you can set NFS up with async writes? I've looked through the documentation, but I don't see anything referring to async NFS. Am i looking in the wrong places? -Shawn Carey