strange nfs problem, need nfs guru

[Gene Heskett]

On Thursday 21 August 2014 07:22:44 Nils Kassube did opine
And Gene did reply:
> 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

gene at lathe:~$ sudo mount -tnfs 192.168.71.3:/ /net
mount.nfs: access denied by server while mounting 192.168.71.3:/

Playing 10,000 monkeys the error is either
mount.nfs: remote share not in 'host:dir' format

or the above access denied.

My current exports file:

# /etc/exports: the access control list for filesystems which may be exported
#		to NFS clients.  See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes       hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
#
/home/gene	lathe(rw,sync,no_subtree_check)	shop(rw,sync,no_subtree_check)

lathe and shop are the aliases listed in the hosts for addresses used, 
all in this local only 192.168.71 block 

> Provided that 192.168.71.3 is the machine which runs the nfs server.

It is.

> 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.

Acc the man page, the 1st example shows one exported directory, accessible
to 2 clients as shown above.

But the error has now moved to the "client" machines, "shop" which is 
my toy milling machine, and "lathe", running a 7x12 mini-lathe, both 
refusing to mount the share.  So I'm stymied again. 

Thanks a bunch, but it seems I need more clues.
 
> Nils


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