From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 20:04:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 020CC16A4CE for ; Thu, 9 Dec 2004 20:04:36 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id D50E543D3F for ; Thu, 9 Dec 2004 20:04:35 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB9K4Z60000991 for ; Thu, 9 Dec 2004 12:04:35 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB9K4ZXH000990 for freebsd-current@freebsd.org; Thu, 9 Dec 2004 12:04:35 -0800 (PST) (envelope-from sgk) Date: Thu, 9 Dec 2004 12:04:35 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20041209200435.GA697@troutmask.apl.washington.edu> References: <20041209004335.GA624@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209004335.GA624@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i Subject: Re: nfs appears broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 20:04:36 -0000 On Wed, Dec 08, 2004 at 04:43:35PM -0800, Steve Kargl wrote: > troutmask:root[201] mount /jumbo > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > > troutmask:root[203] grep jumbo /etc/fstab > jumbo:/data /jumbo nfs rw,noauto 0 0 > > > This is with world+kernel from about 30 minutes on amd64. I was > able to mount /jumbo with a kernel from monday. > Argh. I thought this may be related to phk's recent vfs work. It appears the admin of the NFS server tighten his firewall rules and locked me out. -- Steve