From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 3 18:41:55 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAF9316A4CE for ; Thu, 3 Feb 2005 18:41:55 +0000 (GMT) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A902643D41 for ; Thu, 3 Feb 2005 18:41:54 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j13IfrrT030232; Thu, 3 Feb 2005 12:41:53 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4202706C.60409@centtech.com> Date: Thu, 03 Feb 2005 12:41:48 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041110 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.80/598/Sat Nov 20 16:30:09 2004 clamav-milter version 0.80j on mh1.centtech.com X-Virus-Status: Clean cc: Kevin Kramer Subject: NFS mount / paranoia / conn problems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2005 18:41:56 -0000 I'm having some NFS mounting issues with FreeBSD 5.3 (RELEASE). Here's what my issue is: I have a FreeBSD client, and various NFS servers. The NFS servers are dual homed, and the FBSD client can mount NFS shares from either of the NICs on the servers. When using the automounter, I can connect to either interface on the server, so long as I have the vfs.nfs.nfs_ip_paranoia setting set to '0' (default is '1'). Of course, turning the sysctl to '1' breaks it as expected. Now, here's where the problems come in. If I do a regular mount of the NFS server, it will hang regardless of whether I have the sysctl setting set or not. So, this fails: mount_nfs servernic1:/mount /mnt with this message: [udp] servernic1:/mount: NFSPROC_NULL: RPC: Timed out However, this will work: mount_nfs -c servernic1:/mount /mnt The man page for mount_nfs claims that -c is deprecated, and instead uses the sysctl mentioned above, but it actually ignores the sysctl. Also, the man page claims that adding 'conn' to the mount options in the fstab will do the same as adding -c to the command line, but it seems to ignore it. I'm happy with any solution, as long as I can get my fstab entries working like they should, but this definitely seems like a bug to me. I'm willing to try anything to help fix this. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology I have seen the future and it is just like the present, only longer. ------------------------------------------------------------------------