Re: NFS and amd on older FreeBSD [SOLVED]
Karl Young(ka...@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(free...@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 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS and amd on older FreeBSD
On Fri, 13 Jan 2017 09:06:56 +0100, Daniel Branisswrote: On 12 Jan 2017, at 21:01, Karl Young wrote: Daniel Braniss(da...@cs.huji.ac.il)@2017.01.12 10:25:03 +0200: On 12 Jan 2017, at 9:49 AM, Daniel Braniss wrote: On 12 Jan 2017, at 1:47 AM, 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 On the 7.2 hosts, I can see the exported directory: $ showmount -e 6.3-host Exports list on 6.3-host /data Everyone And access it with amd $ ls -l /net/6-3.host/data drwxr-xr-x 5 root wheel 512 Jun 4 2009 git drwxr-xr-x 4586 root wheel83968 Nov 2 04:50 home I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's old, but it's the best I can do for now). I export the /data directory on the 9.3 system, and I can see it on my 7.2 hosts. $ 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. Thanks for any pointers on how to resolve this. -karl if you changed the export file on the server after you tried to mount in on the client, and will not realise this, if that’s the case, usually rebooting the client helps. s/and/amd/ ^%$# hate spell checkers Thanks Danny I did try rebooting the client (and server) multiple times to no avail. what does amq say? you can, from another host do: amq -h client-host btw, I thing that nfs_server must also run on the client … I have nfs_server_enable=YES $ 20:10:57 ronald@sjakie [~] grep nfs_ser /etc//defaults/rc.conf nfs_server_enable="NO"# This host is an NFS server (or NO). Is your client a NFS server? If not than there is not need for nfs_server_enable YES on the client. Regards, Ronald. danny ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS and amd on older FreeBSD
Do you have exactly the same export options specified in /etc/exports for the 9.3 server as the 6.3 one? Beyond that, I can only suggest capturing packets when the automount fails and looking at them in wireshark to see what is actually happening. rick From: owner-freebsd-sta...@freebsd.org <owner-freebsd-sta...@freebsd.org> on behalf of Daniel Braniss <da...@cs.huji.ac.il> Sent: Friday, January 13, 2017 3:06:56 AM To: Karl Young Cc: FreeBSD Stable Mailing List Subject: Re: NFS and amd on older FreeBSD > On 12 Jan 2017, at 21:01, Karl Young <ka...@kipshouse.org> wrote: > > Daniel Braniss(da...@cs.huji.ac.il)@2017.01.12 10:25:03 +0200: >> >>> On 12 Jan 2017, at 9:49 AM, Daniel Braniss <da...@cs.huji.ac.il> wrote: >>> >>> >>>> On 12 Jan 2017, at 1:47 AM, Karl Young <ka...@kipshouse.org> 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 >>>> >>>> >>>> On the 7.2 hosts, I can see the exported directory: >>>> >>>> $ showmount -e 6.3-host >>>> Exports list on 6.3-host >>>> /data Everyone >>>> >>>> And access it with amd >>>> >>>> $ ls -l /net/6-3.host/data >>>> >>>> drwxr-xr-x 5 root wheel 512 Jun 4 2009 git >>>> drwxr-xr-x 4586 root wheel83968 Nov 2 04:50 home >>>> >>>> I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's >>>> old, but it's the best I can do for now). >>>> >>>> I export the /data directory on the 9.3 system, and I can see it on my >>>> 7.2 hosts. >>>> >>>> $ 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. >>>> >>>> Thanks for any pointers on how to resolve this. >>>> >>>> -karl >>>> >>>> >>> >>> if you changed the export file on the server after you tried to mount in on >>> the client, >>> and will not realise this, if that’s the case, usually rebooting the client >>> helps. >>> >> s/and/amd/ ^%$# hate spell checkers >> > > Thanks Danny > > I did try rebooting the client (and server) multiple times to no avail. what does amq say? you can, from another host do: amq -h client-host btw, I thing that nfs_server must also run on the client … I have nfs_server_enable=YES danny ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS and amd on older FreeBSD
> On 12 Jan 2017, at 21:01, Karl Youngwrote: > > Daniel Braniss(da...@cs.huji.ac.il)@2017.01.12 10:25:03 +0200: >> >>> On 12 Jan 2017, at 9:49 AM, Daniel Braniss wrote: >>> >>> On 12 Jan 2017, at 1:47 AM, 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 On the 7.2 hosts, I can see the exported directory: $ showmount -e 6.3-host Exports list on 6.3-host /data Everyone And access it with amd $ ls -l /net/6-3.host/data drwxr-xr-x 5 root wheel 512 Jun 4 2009 git drwxr-xr-x 4586 root wheel83968 Nov 2 04:50 home I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's old, but it's the best I can do for now). I export the /data directory on the 9.3 system, and I can see it on my 7.2 hosts. $ 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. Thanks for any pointers on how to resolve this. -karl >>> >>> if you changed the export file on the server after you tried to mount in on >>> the client, >>> and will not realise this, if that’s the case, usually rebooting the client >>> helps. >>> >> s/and/amd/ ^%$# hate spell checkers >> > > Thanks Danny > > I did try rebooting the client (and server) multiple times to no avail. what does amq say? you can, from another host do: amq -h client-host btw, I thing that nfs_server must also run on the client … I have nfs_server_enable=YES danny ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS and amd on older FreeBSD
Dear Karl, > On 12 Jan 2017, at 20:29, Karl Youngwrote: > > Daniel Braniss(da...@cs.huji.ac.il)@2017.01.12 10:25:03 +0200: >> >>> On 12 Jan 2017, at 9:49 AM, Daniel Braniss wrote: >>> >>> On 12 Jan 2017, at 1:47 AM, 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 On the 7.2 hosts, I can see the exported directory: $ showmount -e 6.3-host Exports list on 6.3-host /data Everyone And access it with amd $ ls -l /net/6-3.host/data drwxr-xr-x 5 root wheel 512 Jun 4 2009 git drwxr-xr-x 4586 root wheel83968 Nov 2 04:50 home I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's old, but it's the best I can do for now). I export the /data directory on the 9.3 system, and I can see it on my 7.2 hosts. $ 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. Thanks for any pointers on how to resolve this. -karl >>> >>> if you changed the export file on the server after you tried to mount in on >>> the client, >>> and will not realise this, if that’s the case, usually rebooting the client >>> helps. >>> >> s/and/amd/ ^%$# hate spell checkers >> > > Thanks Danny > > I did try rebooting the client (and server) multiple times to no avail. > > -karl I'm not sure if this is related, but afaik FreeBSD up to 8.x used oldNFS by default. Are you using option -o for nfsd on your 9.3 nfs Server to force using old NFS? It is just a guess of mine, I'm usually not working much with nfs. Best regards, Holger ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS and amd on older FreeBSD
Daniel Braniss(da...@cs.huji.ac.il)@2017.01.12 10:25:03 +0200: > > > On 12 Jan 2017, at 9:49 AM, Daniel Branisswrote: > > > > > >> On 12 Jan 2017, at 1:47 AM, 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 > >> > >> > >> On the 7.2 hosts, I can see the exported directory: > >> > >> $ showmount -e 6.3-host > >> Exports list on 6.3-host > >> /data Everyone > >> > >> And access it with amd > >> > >> $ ls -l /net/6-3.host/data > >> > >> drwxr-xr-x 5 root wheel 512 Jun 4 2009 git > >> drwxr-xr-x 4586 root wheel83968 Nov 2 04:50 home > >> > >> I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's > >> old, but it's the best I can do for now). > >> > >> I export the /data directory on the 9.3 system, and I can see it on my > >> 7.2 hosts. > >> > >> $ 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. > >> > >> Thanks for any pointers on how to resolve this. > >> > >> -karl > >> > >> > > > > if you changed the export file on the server after you tried to mount in on > > the client, > > and will not realise this, if that’s the case, usually rebooting the client > > helps. > > > s/and/amd/ ^%$# hate spell checkers > Thanks Danny I did try rebooting the client (and server) multiple times to no avail. -karl > > my .5 cents > > > > danny > > > >> > >> ___ > >> freebsd-stable@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > > > ___ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS and amd on older FreeBSD
Thanks Greg One correction. The new server is FreeBSD 9.2, not 9.3. Replies below Greg Byshenk(free...@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. Thanks -karl > > -- > greg byshenk - gbysh...@byshenk.net - Leiden, NL > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS and amd on older FreeBSD
> On 12 Jan 2017, at 9:49 AM, Daniel Branisswrote: > > >> On 12 Jan 2017, at 1:47 AM, 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 >> >> >> On the 7.2 hosts, I can see the exported directory: >> >> $ showmount -e 6.3-host >> Exports list on 6.3-host >> /data Everyone >> >> And access it with amd >> >> $ ls -l /net/6-3.host/data >> >> drwxr-xr-x 5 root wheel 512 Jun 4 2009 git >> drwxr-xr-x 4586 root wheel83968 Nov 2 04:50 home >> >> I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's >> old, but it's the best I can do for now). >> >> I export the /data directory on the 9.3 system, and I can see it on my >> 7.2 hosts. >> >> $ 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. >> >> Thanks for any pointers on how to resolve this. >> >> -karl >> >> > > if you changed the export file on the server after you tried to mount in on > the client, > and will not realise this, if that’s the case, usually rebooting the client > helps. > s/and/amd/ ^%$# hate spell checkers > my .5 cents > > danny > >> >> ___ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS and amd on older FreeBSD
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. -- greg byshenk - gbysh...@byshenk.net - Leiden, NL ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: NFS and amd on older FreeBSD
> On 12 Jan 2017, at 1:47 AM, Karl Youngwrote: > > 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 > > > On the 7.2 hosts, I can see the exported directory: > > $ showmount -e 6.3-host > Exports list on 6.3-host > /data Everyone > > And access it with amd > > $ ls -l /net/6-3.host/data > > drwxr-xr-x 5 root wheel 512 Jun 4 2009 git > drwxr-xr-x 4586 root wheel83968 Nov 2 04:50 home > > I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's > old, but it's the best I can do for now). > > I export the /data directory on the 9.3 system, and I can see it on my > 7.2 hosts. > > $ 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. > > Thanks for any pointers on how to resolve this. > > -karl > > if you changed the export file on the server after you tried to mount in on the client, and will not realise this, if that’s the case, usually rebooting the client helps. my .5 cents danny > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
NFS and amd on older FreeBSD
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 On the 7.2 hosts, I can see the exported directory: $ showmount -e 6.3-host Exports list on 6.3-host /data Everyone And access it with amd $ ls -l /net/6-3.host/data drwxr-xr-x 5 root wheel 512 Jun 4 2009 git drwxr-xr-x 4586 root wheel83968 Nov 2 04:50 home I'm trying to retire the 6.3 host and replace it with 9.3 (I know it's old, but it's the best I can do for now). I export the /data directory on the 9.3 system, and I can see it on my 7.2 hosts. $ 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. Thanks for any pointers on how to resolve this. -karl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"