Hello list,

I use this box as an emerge host for a couple of smaller boxes on the LAN;
each of those has a main system and a small rescue system. I've been running
with this setup for several years without any real problems. Now, however,
something seems to have changed and I get this error when trying to mount
either of the two rescue systems via NFS (no problem with the main systems):

# 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
mount.nfs: mounting 192.168.1.2:/mnt/rescue/usr/portage failed, reason given by 
server: No such file or directory

# cat /etc/exports              << On the client box
/usr/portage            
192.168.1.5(rw,no_subtree_check,mp,anonuid=250,anongid=250)
/mnt/rescue/usr/portage 
192.168.1.5(rw,no_subtree_check,mp,anonuid=250,anongid=250)
# ls -ld /mnt/rescue/usr/portage                << On the client box
drwxr-xr-x 175 portage portage 4.0K Mar 30 22:15 /mnt/rescue/usr/portage
# find /mnt/rescue/usr/portage -type f | wc             << On the client box
 137415  137415 9254339
# showmount -e          << On the client box
Export list for serv:           << The name of the client box
/mnt/rescue/usr/portage 192.168.1.5             << The address of the emerge 
host
/usr/portage            192.168.1.5

What else might make the NFS server report nonexistent directory? And what
might differ between the main and rescue system on each of two boxes?

-- 
Regards,
Peter.




Reply via email to