From owner-freebsd-current@FreeBSD.ORG Tue Jun 2 10:54:51 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F7891065672 for ; Tue, 2 Jun 2009 10:54:51 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id DF5A78FC1D for ; Tue, 2 Jun 2009 10:54:50 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@FreeBSD.org with esmtp (envelope-from ) id <1MBRdp-0002Dn-VC>; Tue, 02 Jun 2009 12:54:50 +0200 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@FreeBSD.org with esmtpsa (envelope-from ) id <1MBRdp-0005x7-Ts>; Tue, 02 Jun 2009 12:54:49 +0200 Message-ID: <4A2504AA.1020406@zedat.fu-berlin.de> Date: Tue, 02 Jun 2009 10:53:30 +0000 From: "O. Hartmann" Organization: Freie =?ISO-8859-15?Q?Universit=E4t_Berlin?= User-Agent: Thunderbird 2.0.0.21 (X11/20090417) MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Cc: Subject: RPCPROG_MNT: RPC: Timed out / receiving NFS error when trying to mount NFS file system after make world X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 02 Jun 2009 10:54:51 -0000 Hello, since today I get this error when trying to mount a NFS filesystem from NFS server: [udp] foo:/home: RPCPROG_MNT: RPC: Timed out Both boxes, cleint and server, are most recent FreeBSD 8.0-CURRENT/amd64 from today's buildworld/make kernel. nfsd is up and running and worked that way days before. I saw commitments of new NFSv4 code, are these causing this issue? Is 8.0 supposed to be offering nfsv4-server capabilities which I need to switch on anyway? I also tried mount -t newnfs on that NFS filesystem but without any success. Is this a fault of mine or are temporarely not-working-condition? I tried both ZFS and UFS2 NFS exports to get mounted, both are unwilling to mount with the above showed error. Regards, Oliver