From owner-freebsd-current Mon Jul 23 8:54:52 2001 Delivered-To: freebsd-current@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id 5DDE237B403 for ; Mon, 23 Jul 2001 08:54:36 -0700 (PDT) (envelope-from max@vega.com) Received: from mail.uic-in.net (root@[212.35.189.4]) by kalaid.f2f.com.ua (8.11.4/8.11.4) with ESMTP id f6NFuMT62021 for ; Mon, 23 Jul 2001 18:56:25 +0300 (EEST) (envelope-from max@vega.com) Received: from vega.vega.com (das0-l20.uic-in.net [212.35.189.147]) by mail.uic-in.net (8.11.4/8.11.4) with ESMTP id f6NFsQt10052 for ; Mon, 23 Jul 2001 18:54:28 +0300 (EEST) (envelope-from max@vega.com) Received: (from max@localhost) by vega.vega.com (8.11.4/8.11.3) id f6NFsLk65848 for current@FreeBSD.org; Mon, 23 Jul 2001 18:54:21 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) From: Maxim Sobolev Message-Id: <200107231554.f6NFsLk65848@vega.vega.com> Subject: NFS client unable to recover from server crash To: current@FreeBSD.org Date: Mon, 23 Jul 2001 18:53:05 +0300 (EEST) X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I found that after introduction of the new RPC NFS client is no longer able to recover from server crash (both cluent and server are 5-CURRENT systems). After a well known `nfs server not responding' message, client hangs and even though server comes back in a minute or two it doesn't recover and just sits in this state forvewer. All unmount requests gets stuck in the kernel, so as a processes that accessing files from that mount point. This doesn't looks like a right thing and obviously should be fixed before 5.0-RELEASE. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message