strange nfs problem, need nfs guru

[Tom H]

On Thu, Aug 21, 2014 at 6:27 AM, Gene Heskett <gheskett at wdtv.com> wrote:
> On Thursday 21 August 2014 04:24:42 Nils Kassube did opine
> And Gene did reply:
>> Tom H wrote:
>>>
>>> # 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
>
> But, ssh'd into one of those machines, there isn't anything at the /net/
> link.

So nfs is now starting.

In to which machine are you ssh'ing?

The nfs server or an nfs client?

Do you have autofs running on the machine where into which you're
ssh'ing? Is "/net" enabled/uncommented?

What does "ls /net/ip-address-of-nfs-server" (or "ls
/net/hostname-of-nfs-server" if you have dns set up) return?