automounting nfsv4

[Tom H]

On Wed, May 18, 2011 at 2:58 PM, Clem Takahashi <clemtak at gmail.com> wrote:
>
> I'm following https://help.ubuntu.com/community/SettingUpNFSHowTo and
> http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration to set up NFS
> v4 without Kerberos.  The server on 192.168.1.1 is running natty,
> dist-upgraded from maverick, and appears to be set up correctly because I
> can manually mount shares on clients running karmic with:
>
> sudo mount -t nfs4 -o proto=tcp,port=2049 192.168.1.1:/user1
> /home/user1/Share
> sudo mount -t nfs4 -o proto=tcp,port=2049 192.168.1.1:/user2
> /home/user2/Share
>
> However, I can't automount with these /etc/fstab entries:
>
> 192.168.1.1:/user2  /home/user2/Share  nfs4  proto=tcp,port=2049  0  0
> 192.168.1.1:/user1  /home/user1/Share  nfs4  proto=tcp,port=2049  0  0
>
>
> There don't appear to be any significant error messages in
> /var/log/messages.  The messages that contain the strings nfs, rpc, or mount
> are:
>
> May 16 21:05:48 cl1 kernel: [    0.001732] Mount-cache hash table entries:
> 512
> May 16 21:05:48 cl1 kernel: [    3.363645] EXT4-fs (sda1): mounted
> filesystem with ordered data mode
>
> May 16 21:05:48 cl1 kernel: [   24.548685] RPC: Registered udp transport
> module.
> May 16 21:05:48 cl1 kernel: [   24.548689] RPC: Registered tcp transport
> module.
>
> May 16 21:05:48 cl1 kernel: [   25.019198] Installing knfsd (copyright (C)
> 1996 okir at monad.swb.de).

Add "_netdev" to the fstab options because it may be that the mounts
are being attempted before the network's up.