From owner-freebsd-hackers Fri Feb 6 17:45:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11558 for hackers-outgoing; Fri, 6 Feb 1998 17:45:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA11548 for ; Fri, 6 Feb 1998 17:45:12 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 2055 invoked from network); 7 Feb 1998 01:45:10 -0000 Received: from cello.synapse.net (HELO cello) (199.84.54.81) by conductor.synapse.net with SMTP; 7 Feb 1998 01:45:10 -0000 Message-ID: <025801bd336a$037b3cc0$2844c00a@cello.synapse.net> From: "Evan Champion" To: "Greg Lehey" , "Jonathan A. Zdziarski" Cc: "FreeBSD Hackers" Subject: Re: More NFS Problems Date: Fri, 6 Feb 1998 20:45:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe hackers" >I think it's broken. A soft mount should cause NFS to give up after a >while, but I've never seen it happen, and I've given it a long time. This may not directly apply, as it is with BSD/OS 3.1 clients, but I rather doubt the NFS code is all that much different between 2.2-stable and BSD/OS 3.1. What I see is if the server goes down when only a few processes are trying to use the mount, the client never times out, but when the server does come back up, the client restore the mount properly and everything goes along quite nicely. If, on the other hand, a huge number of processes are stuck on the mount, the stuck processes basically have to be terminated before the mount will be accessible again, even long after the server has come back up. Evan