1 |
Hello list, |
2 |
|
3 |
I use this box as an emerge host for a couple of smaller boxes on the LAN; |
4 |
each of those has a main system and a small rescue system. I've been running |
5 |
with this setup for several years without any real problems. Now, however, |
6 |
something seems to have changed and I get this error when trying to mount |
7 |
either of the two rescue systems via NFS (no problem with the main systems): |
8 |
|
9 |
# mount -t nfs -o rsize=1024,wsize=1024,vers=3 192.168.1.2:/mnt/rescue/usr/portage /mnt/atomresc/usr/portage << On the emerge host |
10 |
mount.nfs: mounting 192.168.1.2:/mnt/rescue/usr/portage failed, reason given by server: No such file or directory |
11 |
|
12 |
# cat /etc/exports << On the client box |
13 |
/usr/portage 192.168.1.5(rw,no_subtree_check,mp,anonuid=250,anongid=250) |
14 |
/mnt/rescue/usr/portage 192.168.1.5(rw,no_subtree_check,mp,anonuid=250,anongid=250) |
15 |
# ls -ld /mnt/rescue/usr/portage << On the client box |
16 |
drwxr-xr-x 175 portage portage 4.0K Mar 30 22:15 /mnt/rescue/usr/portage |
17 |
# find /mnt/rescue/usr/portage -type f | wc << On the client box |
18 |
137415 137415 9254339 |
19 |
# showmount -e << On the client box |
20 |
Export list for serv: << The name of the client box |
21 |
/mnt/rescue/usr/portage 192.168.1.5 << The address of the emerge host |
22 |
/usr/portage 192.168.1.5 |
23 |
|
24 |
What else might make the NFS server report nonexistent directory? And what |
25 |
might differ between the main and rescue system on each of two boxes? |
26 |
|
27 |
-- |
28 |
Regards, |
29 |
Peter. |