strange nfs problem, need nfs guru

[Gene Heskett]

On Thursday 21 August 2014 08:00:46 Joseph Loo did opine
And Gene did reply:
> On 08/21/2014 04:22 AM, Nils Kassube wrote:
> > Gene Heskett wrote:
> >> On Thursday 21 August 2014 04:24:42 Nils Kassube did opine
> >> 
> >> And Gene did reply:
> >>> Tom H wrote:
> >>>> Anyway, it looks like your kernel's failing this test in
> >>>> "/etc/init.d/nfs-kernel-server":
> >>>> 
> >>>> # See if our running kernel supports the NFS kernel server
> >>>> if ! grep -E -qs "[[:space:]]nfsd\$" /proc/filesystems; then
> >> 
> >> Replacing my similar line with this, gets me a more informative msg:
> >> gene at coyote:/etc/init.d$ sudo service nfs-kernel-server restart
> >> 
> >>   * Stopping NFS kernel daemon
> >> 
> >> [ OK ]
> >> 
> >>   * Unexporting directories for NFS kernel daemon...
> >> 
> >> [ OK ]
> >> 
> >>   * Exporting directories for NFS kernel daemon...
> >> 
> >> exportfs: /etc/exports [1]: Neither 'subtree_check' or
> >> 'no_subtree_check' specified for export
> >> "192.168.71.3/24:/home/gene/".
> >> 
> >>    Assuming default behaviour ('no_subtree_check').
> >>    NOTE: this default has changed since nfs-utils version 1.0.x
> >> 
> >> exportfs: /etc/exports [2]: Neither 'subtree_check' or
> >> 'no_subtree_check' specified for export "192.168.71.3/24:/".
> >> 
> >>    Assuming default behaviour ('no_subtree_check').
> >>    NOTE: this default has changed since nfs-utils version 1.0.x
> >> 
> >> [ OK ]
> >> 
> >>   * Starting NFS kernel daemon
> > 
> > Looks good to me.
> > 
> >> But, ssh'd into one of those machines, there isn't anything at the
> >> /net/ link.
> > 
> > I have no idea what you mean by "there isn't anything at the /net/
> > link". But what happens if you try to mount your one of the exported
> > directories from the other machine?
> > 
> > sudo mount -tnfs 192.168.71.3:/ /mnt
> > 
> > Provided that 192.168.71.3 is the machine which runs the nfs server.
> > BTW: In your exports file the IP address specifies which host is
> > allowed to mount the share and it should be either one host (like
> > 192.168.71.3) or a IP range like 192.168.71.0/24 - I have no idea
> > what would happen if you use a host address with a trailing /24.
> > 
> > 
> > Nils
> 
> I believe he is using autofs. Try ls /net/192.168.71.3 and see what is
> showing up.

I believe I am, but
gene at lathe:~$ ls /net/192.168.71.3
ls: cannot access /net/192.168.71.3: No such file or directory
gene at lathe:~$ 

and
gene at lathe:~$ ls /net/coyote
gene at lathe:~$ 

This latter is where I'd expect it to show up.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS