From: Trond Myklebust Subject: Re: Status of mount.nfs Date: Fri, 27 Jul 2007 12:27:59 -0400 Message-ID: <1185553679.6586.34.camel@localhost> References: <20070708191640.GA13962@uio.no> <18065.43199.104020.412029@notabene.brown> <20070715083114.GB4158@uio.no> <18074.50730.591965.39211@notabene.brown> <20070716092047.GA10353@uio.no> <18075.17719.855332.259470@notabene.brown> <20070722191733.GA31501@uio.no> <46A52816.6050500@oracle.com> <20070724172451.GA14026@uio.no> <46A7A5F8.4040204@oracle.com> <46A897CD.50201@RedHat.com> <46A96032.7080503@oracle.com> <46AA089E.50503@RedHat.com> <1185551769.6586.28.camel@localhost> <46AA1A70.5010705@RedHat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: nfs@lists.sourceforge.net To: Steve Dickson Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] helo=mail.sourceforge.net) by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43) id 1IESfh-0007Ym-Jw for nfs@lists.sourceforge.net; Fri, 27 Jul 2007 09:28:10 -0700 Received: from pat.uio.no ([129.240.10.15] ident=[U2FsdGVkX1/3SYBPxt94wY5Gy5BGzWl0Ffb+S3QCK5k=]) by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44) id 1IESfk-0001KP-NU for nfs@lists.sourceforge.net; Fri, 27 Jul 2007 09:28:13 -0700 In-Reply-To: <46AA1A70.5010705@RedHat.com> List-Id: "Discussion of NFS under Linux development, interoperability, and testing." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfs-bounces@lists.sourceforge.net Errors-To: nfs-bounces@lists.sourceforge.net On Fri, 2007-07-27 at 12:16 -0400, Steve Dickson wrote: > > Trond Myklebust wrote: > > On Fri, 2007-07-27 at 11:00 -0400, Steve Dickson wrote: > > > >> That was the main reason for the ping. Since neither portmapper or > >> rpcbind ping their services before they hand out the ports, there > >> is really no way of telling where the server is up? So to avoid > >> the hang, we ping them... Sure its costly network wise, but > >> hanging during a boot because a server is not responding is > >> a bit more costly... imho... > > > > Right, but recent kernels both can and will ping the NFS service for > > you. > Good point... but that's just as costly (wrt network traffic) as > the mount command doing the pinging... plus the status of the > remote mountd is also needed. The kernel ping is sent on the same connection to the server than the NFS client will use, so we don't waste any extra TCP ports. I agree that you need to figure out the mountd parameters, but the right thing to do there is simply to try the command. The RPC return values will tell you if the service or version you tried isn't supported. Cheers Trond ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs