From owner-freebsd-current@FreeBSD.ORG Tue Jun 2 15:14:45 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 E82061065675 for ; Tue, 2 Jun 2009 15:14:45 +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 704FC8FC08 for ; Tue, 2 Jun 2009 15:14:45 +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) with esmtp (envelope-from ) id <1MBVhM-0002z5-GX>; Tue, 02 Jun 2009 17:14:44 +0200 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1MBVhM-0005yq-FE>; Tue, 02 Jun 2009 17:14:44 +0200 Message-ID: <4A254194.7080807@zedat.fu-berlin.de> Date: Tue, 02 Jun 2009 15:13:24 +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: Rick Macklem References: <4A2504AA.1020406@zedat.fu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Cc: freebsd-current@FreeBSD.org Subject: Re: 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 15:14:46 -0000 Rick Macklem wrote: > > > On Tue, 2 Jun 2009, O. Hartmann wrote: > >> 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? >> > By default, everything should work just like before, using the vanilla NFS > server, etc. The message indicates that mountd wasn't responding. So, > first off, check that it is running. > > I did integrate some changes into mountd for the new experimental nfs > subsystem, but those should only be invoked if "-e" was provided on its > command line. > > I'll go through the changes I made to mountd.c again, but it has been > working ok for me. > >> 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? >> > Using "mount -t newnfs" uses the experimental nfs client instead of the > regular one, but they should both work. The problem seems to be an > unresponsive mountd. > > Let us know if you find out anything more about it, rick > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Mounting via '-o nfsv3,tcp' in addition, everthing works all right again. I do not know why udp is invoked automatically by now. But for short, we always did NFS mounts over tcp AND udp, so for tcp it worked again! Oliver