From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 13:00:40 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AE2B16A41C for ; Wed, 8 Jun 2005 13:00:40 +0000 (GMT) (envelope-from robin.blanchard@gactr.uga.edu) Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 195B143D53 for ; Wed, 8 Jun 2005 13:00:39 +0000 (GMT) (envelope-from robin.blanchard@gactr.uga.edu) Received: from localhost (localhost [127.0.0.1]) by mail.gactr.uga.edu (Postfix) with ESMTP id 41D7A5C0B7; Wed, 8 Jun 2005 09:00:38 -0400 (EDT) Received: from mail.gactr.uga.edu ([127.0.0.1]) by localhost (mail.gactr.uga.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 29265-01-3; Wed, 8 Jun 2005 09:00:38 -0400 (EDT) Received: from EBE1.gc.nat (E2K1.gc.nat [10.10.11.21]) by mail.gactr.uga.edu (Postfix) with ESMTP id 16BC05C0AE; Wed, 8 Jun 2005 09:00:38 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 8 Jun 2005 09:00:38 -0400 Message-ID: <9B5C1FCAFB35084787C21EFFFA78DD9EF13777@EBE1.gc.nat> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: strange NFS failure Thread-Index: AcVrwF3trfhNXpIeQ3SKaS25D2iUGQAaWLFg From: "Robin P. Blanchard" To: "fergus" , X-Virus-Scanned: by amavisd-new at gactr.uga.edu Cc: Subject: RE: strange NFS failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 13:00:40 -0000 > just upgraded two systems to RELENG_5 this evening and NFS=20 > client has collapsed. is this known issue? apologies -- i=20 > realise i should really be tracking stable list. >=20 > the error is >=20 > [udp] 10.12.12.66:/usr/cabinet: RPCPROG_NFS: RPC: Port=20 > mapper failure - > RPC: Unable to recieve >=20 > and yes rpcbind is running OK. rpcinfo of the system=20 > produces normal output. >=20 > thanks for any pointers. Sounds related to: http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/015726.ht= ml Using "broken" kernel also yields "broken" nfs...