Hello list,
I decided to have another go at fixing my nfs setup. The host 192.168.1.4
exports its portage directory to this host, 192.168.1.5. I used to use nfs-v3
for this, but it wasn't working right so I'm trying with v4.
The problem is that, every time I tell this machine to mount the remote
directory, the server insists that it doesn't exist. I can't see what I've
missed. Here's some detail:
mount -t nfs 192.168.1.4:/mnt/nfs/portage /mnt/clrn/usr/portage # script on the
client
Result:
* Mounting chroot dirs under /mnt/clrn ...
mount.nfs: mounting 192.168.1.4:/mnt/nfs/portage failed, reason given by
server: No such file or directory
$ cat /etc/exports # on the server
/mnt/nfs \
192.168.1.5(rw,sync,no_subtree_check,anonuid=250,anongid=250,crossmnt,fsid=0)
/mnt/nfs/portage \
192.168.1.5(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250
/mnt/nfs/port.resc \
192.168.1.5(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250
$ sudo exportfs -v # on the server
/mnt/nfs
192.168.1.5(sync,wdelay,hide,crossmnt,no_subtree_check,fsid=0,anonuid=250,anongid=250,sec=sys,rw,secure,root_squash,no_all_squash)
/mnt/nfs/portage
192.168.1.5(sync,wdelay,nohide,no_subtree_check,anonuid=250,anongid=250,sec=sys,rw,insecure,root_squash,all_squash)
Can anyone see the problem?
--
Regards,
Peter.
