Error mount NFS -- nfs4_get_rootfh
Geoffrey Leach
geoff at hughes.net
Thu Jan 5 04:17:28 UTC 2012
On 01/04/2012 05:08:41 PM, Craig White wrote:
> On Wed, 2012-01-04 at 13:21 -0800, Geoffrey Leach wrote:
> > On 01/02/2012 04:02:55 PM, Ed Greshko wrote:
>
> > >> ** On server....
> > >
> > > systemctl is-enabled nfs-lock.service
> > > systemctl is-enabled nfs-server.service
> > > systemctl is-enabled nfs-idmap.service
> >
> > nfs-idmap.service loaded active running NFSv4
> ID-name
> > mapping daemon
> > nfs-lock.service loaded active running NFS file
> > locking service.
> > nfs-server.service loaded active running NFS Server
> >
> > Firewall disabled. Shhh - don't tell anybody.
> >
> > > Also, make sure Port 2049 is open on the firewall
> >
> > on client, disabled. Verified.
> >
> > > ** On client
> > >
> > > systemctl is-enabled nfs-idmap.service
> > > systemctl is-enabled nfs-lock.service
> >
> > Verified
> >
> > > Then go on to configure the shares....
> > >
> > > ** Server....
> > >
> > > mkdir -m 1777 /nfs4exports
> > > cd /nfs4exports
> > > mkdir -m 1777 home
> > > mount --bind /home home
> >
> > drwxrwxrwt 5 root root 4096 Dec 31 15:34 /nfs4exports/
> > drwxrwxrwt. 6 root root 4096 May 18 2011 /nfs4exports/home/
> > drwxrwxrwt 2 root root 4096 Dec 31 15:34 /nfs4exports/tmp/
> > drwxrwxrwt 2 root root 4096 Dec 27 16:20 /nfs4exports/usrlocal/
> > root at mtranch[14]->umount /nfs4exports/tmp/ /nfs4exports/usrlocal/
> > umount: /nfs4exports/tmp/: not mounted
> > umount: /nfs4exports/usrlocal/: not mounted
> >
> > > To make the bind effective a boot time edit /etc/fstab to contain
> > >
> > > /home /nfs4exports/home none rw,bind 0 0
> >
> > #tail /etc/fstab
> > /home /nfs4exports/home none rw,bind 0 0
> >
> > > vi /etc/idmapd.conf (Modify "Domain" line, making sure to
> remove
> > > leading #)
> >
> > # The default is the host's DNS domain name.
> > Domain = mtranch.mtranch.com
> >
> > This should be just mtranch.com, yes?
> ----
> yes, 'Domain = mtranch.com'
> ----
> >
> > > vi /etc/exports (Added 2 lines)
> > >
> > > /nfs4exports
> > > 192.168.0.0/24
> (ro,sync,insecure,root_squash,no_subtree_check,fsid=0)
> > > /nfs4exports/home
> > > 192.168.0.0/24
> (rw,nohide,sync,insecure,root_squash,no_subtree_check)
> >
> > #cat /etc/exports
> > /nfs4exports 192.168.0.0/24
> > (ro,sync,insecure,root_squash,no_subtree_check,fsid=0)
> > /nfs4exports/home 192.168.0.0/24
> > (rw,nohide,sync,insecure,root_squash,no_subtree_check)
> >
> > > exportfs -rv
> >
> > #exportfs -rv
> > exporting 192.168.0.0/24:/nfs4exports/home
> > exporting 192.168.0.0/24:/nfs4exports
> >
> > >
> > > ** Client....
> > >
> > > mkdir /mtranch-home
> >
> > Verified
> >
> > > Then just mount....
> >
> > Connection refused, as before
> >
> > No actual output from the client, as I'm reduced to sneakernet at
> this
> > point.
> ----
> but we didn't see the command nor the result...
>
> mkdir /mtranch-home # I think this you did
> mount -t nfs4 $SERVER:/home /mtranch-home
>
> Obviously for the $SERVER, you should substitute either the
> IP_Address
> of your NFS4 server (or the FQDN/Hostname of your NFS Server IF you
> can
> ping it from the NFS client by the same name).
>
> Any time you change /etc/idmapd.conf you should restart
> idmapd.service
> (client or server)...
> systemctl restart nfs-idmap.service
>
Domain = change made as advised. service restarted. no change.
Please see file attached to my reply to Ed's posting to the same
subject.
Regards.
More information about the users
mailing list