From owner-freebsd-stable@freebsd.org Wed Jan 18 23:29:06 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5061CCB6EED for ; Wed, 18 Jan 2017 23:29:06 +0000 (UTC) (envelope-from karly@kipshouse.net) Received: from mgmt.ironboy.kipshouse.net (ironboy.kipshouse.net [IPv6:2001:470:835a:4242::42]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "mx.kipshouse.net", Issuer "Starfield Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C94E181B for ; Wed, 18 Jan 2017 23:29:05 +0000 (UTC) (envelope-from karly@kipshouse.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kipshouse.org; i=@kipshouse.org; q=dns/txt; s=kh-ss; t=1484782146; x=1516318146; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; z=Date:=20Wed,=2018=20Jan=202017=2015:03:56=20-0800|From: =20Karl=20Young=20|To:=20Greg=20Bysh enk=20|Cc:=20FreeBSD=20Stable=20Mail ing=20List=20|Subject:=20Re: =20NFS=20and=20amd=20on=20older=20FreeBSD=20[SOLVED] |Message-ID:=20<20170118230356.GD26386@mailboy.kipshouse. net>|References:=20<20170111234737.GK26386@mailboy.kipsho use.net>=0D=0A=20<20170112075816.GQ731@v1.leiden.byshenk. net>=0D=0A=20<20170112190007.GQ26386@mailboy.kipshouse.ne t>|MIME-Version:=201.0|In-Reply-To:=20<20170112190007.GQ2 6386@mailboy.kipshouse.net>; bh=3LeVz1+RfSIf0JzXYQQh8Ix8Aj+pRpqzA7NtsvTs4m0=; b=ChglUNbRCq5SZchpp5ZbAAlRBFM4A1nxlITobw3mGCVl5Eqi2KQ/RWXe vyoCmmSNB57QCDXmK63j0xvq4864I5IqIcBz312jUCSfAw0ZzxaDPY9h4 lZ33frbsqIZvbuvx05BWGVfpvnufFQp+fxO6NkuzGcP5LsY6QP2HoVkjP Pz16lcHz0DWYhUoXjpxC23Cu12a8t+Kpr5a+ZVumWFvjEKnT18cu+hiCi pbXS8y/dCeUDj3C8B394Ob26t3odS3Z7pc9XPakth1EXlS9Rsfd0a7j6Q lKxIeFcmjlF6u2xW882nqQqKT+LeUmDC9rJCWCpwtq3qJH/ESzMK98dzf w==; Authentication-Results: d2.ironport.kipshouse.net; dkim=none (message not signed) header.i=none; spf=None smtp.pra=karly@kipshouse.org; spf=None smtp.mailfrom=karly@kipshouse.net; spf=None smtp.helo=postmaster@mailboy.kipshouse.net Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of karly@kipshouse.org) identity=pra; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="karly@kipshouse.org"; x-conformance=sidf_compatible Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of karly@kipshouse.net) identity=mailfrom; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="karly@kipshouse.net"; x-conformance=sidf_compatible Received-SPF: None (d2.ironport.kipshouse.net: no sender authenticity information available from domain of postmaster@mailboy.kipshouse.net) identity=helo; client-ip=2001:470:835a:1010::26; receiver=d2.ironport.kipshouse.net; envelope-from="karly@kipshouse.net"; x-sender="postmaster@mailboy.kipshouse.net"; x-conformance=sidf_compatible X-SBRS: None X-MID: 232206 X-RemoteIP: 2001:470:835a:1010::26 X-RemoteHost: 2001:470:835a:1010::26, mailboypriv.kipshouse.net X-IronPort-AV: E=McAfee;i="5700,7163,8412"; a="232206" Received: from mailboypriv.kipshouse.net (HELO mailboy.kipshouse.net) ([IPv6:2001:470:835a:1010::26]) by d2.ironport.kipshouse.net with ESMTP; 18 Jan 2017 15:29:05 -0800 Received: by mailboy.kipshouse.net (Postfix, from userid 500) id B3AAC42497; Wed, 18 Jan 2017 15:03:56 -0800 (PST) Date: Wed, 18 Jan 2017 15:03:56 -0800 From: Karl Young To: Greg Byshenk Cc: FreeBSD Stable Mailing List Subject: Re: NFS and amd on older FreeBSD [SOLVED] Message-ID: <20170118230356.GD26386@mailboy.kipshouse.net> References: <20170111234737.GK26386@mailboy.kipshouse.net> <20170112075816.GQ731@v1.leiden.byshenk.net> <20170112190007.GQ26386@mailboy.kipshouse.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170112190007.GQ26386@mailboy.kipshouse.net> X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.kipshouse.org/karly X-Work-URL: http://www.cisco.com/ X-Disclaimer: My opinions do not necessarily represent those of my employer. User-Agent: Mutt/1.5.20 (2009-12-10) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2017 23:29:06 -0000 Karl Young(karly@kipshouse.org)@2017.01.12 11:00:07 -0800: > Thanks Greg > > One correction. The new server is FreeBSD 9.2, not 9.3. Replies below > > Greg Byshenk(freebsd@byshenk.net)@2017.01.12 08:58:16 +0100: > > On Wed, Jan 11, 2017 at 03:47:37PM -0800, Karl Young wrote: > > > I inherited a lab that has a few hundred hosts running FreeBSD 7.2. > > > These hosts run test scripts that access files that are stored on > > > FreeBSD 6.3 host. The 6.3 host exports a /data directory with NFS > > > > > > [...] > > > > > > $ showmount -e 9.3-host > > > Exports list on 9.3-host: > > > /data Everyone > > > > > > But I can't automount it: > > > > > > $ ls -l /net/9.3-host/data > > > ls: /net/9.3-host/data: No such file or directory > > > > > > If I manually mount the exported directory, it works: > > > > > > $ sudo mount -t nfs 9.3-host:/data /mnt/data/ > > > $ mount | grep nfs > > > 9.3-host:/data on /mnt/data (nfs) > > > > > > $ ls -l /mnt/data > > > total 4 > > > drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 > > > > > > I've spent some time on Google, but haven't found a solution. I realize > > > these are very old versions, but I'm not in a position to upgrade them > > > right now. My last resort will be to use /etc/fstab to do the NFS > > > mount, but I'd rather avoid that if I can. > > > > If you can mount the share manually, there is almost > > certainly nothing wrong with the server. Based on the > > error ("No such file or directory"), I would recommend > > checking your amd config on the client. > > > > Yes, that makes sense, but I'm using the same client in both cases. In > rc.conf on client, I have: > > nfs_reserved_port_only="YES" > nfs_client_enable="YES" > amd_enable="YES" > > > And ps shows the amd process started with these flags: > > /usr/sbin/amd -p -a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map > > amd.map is the default > > $ cat /etc/amd.map > # $FreeBSD: src/etc/amd.map,v 1.10.8.1 2009/04/15 03:14:26 kensmith Exp > # $ > # > /defaults type:=host;fs:=${autodir}/${rhost}/host;rhost:=${key} > * opts:=rw,grpid,resvport,vers=3,proto=tcp,nosuid,nodev > > This is the same default amd.map as 9.2. > > Another data point: I see the same behavior with a 9.2 client: I can > automount a share from my 6.3 server, but not from the 9.2 server. Well, I might have found a workaround, but it's weird, seems to be DNS-related. Something I left out (didn't think it was important) is that the 6.3 server is out on our corporate net, so I used a FQDN: ls -l 6.3-server.example.com/data But the new server lives in our lab, so it has an RFC1918 address, and doesn't have a .com TLD. ls -l 9.2-server.lab/data I found that if I use the IP address, OR if I terminate the server name with a '.', it now works. ls -l /net/10.15.2.22/data/ total 4 drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 $ ls -l /net/9.2-server.lab./data/ total 4 drwxr-xr-x 9 root wheel 512 Dec 20 17:41 iaf2 $ ls -l /net/9.2-server.lab/data/ ls: /net/9.2-server.lab/data/: No such file or directory $ showmount -e 9.2-server.lab Exports list on 9.2-server.lab: /data Everyone Sorry for the diversion. -karl