1 |
Hello list, |
2 |
|
3 |
I decided to have another go at fixing my nfs setup. The host 192.168.1.4 |
4 |
exports its portage directory to this host, 192.168.1.5. I used to use nfs-v3 |
5 |
for this, but it wasn't working right so I'm trying with v4. |
6 |
|
7 |
The problem is that, every time I tell this machine to mount the remote |
8 |
directory, the server insists that it doesn't exist. I can't see what I've |
9 |
missed. Here's some detail: |
10 |
|
11 |
mount -t nfs 192.168.1.4:/mnt/nfs/portage /mnt/clrn/usr/portage # script on the client |
12 |
|
13 |
Result: |
14 |
* Mounting chroot dirs under /mnt/clrn ... |
15 |
mount.nfs: mounting 192.168.1.4:/mnt/nfs/portage failed, reason given by server: No such file or directory |
16 |
|
17 |
$ cat /etc/exports # on the server |
18 |
/mnt/nfs \ |
19 |
192.168.1.5(rw,sync,no_subtree_check,anonuid=250,anongid=250,crossmnt,fsid=0) |
20 |
/mnt/nfs/portage \ |
21 |
192.168.1.5(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250 |
22 |
/mnt/nfs/port.resc \ |
23 |
192.168.1.5(rw,sync,insecure,nohide,no_subtree_check,all_squash,anonuid=250,anongid=250 |
24 |
|
25 |
$ sudo exportfs -v # on the server |
26 |
/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) |
27 |
/mnt/nfs/portage |
28 |
192.168.1.5(sync,wdelay,nohide,no_subtree_check,anonuid=250,anongid=250,sec=sys,rw,insecure,root_squash,all_squash) |
29 |
|
30 |
Can anyone see the problem? |
31 |
|
32 |
-- |
33 |
Regards, |
34 |
Peter. |