![]() |
All of a sudden, NFS sharing is busted. Getting 'mount(2) No such file or directory error
When I was running Debian 10.3, this setup worked perfectly. After updating to 10.4 a few weeks ago, my NFS server has been busted. Been trying to fix it for a while and finally threw in the towel and decided to ask for help. :(
Here we go..... /etc/exports from Server-PC: (server IP is 192.168.1.5) Code:
/mnt/md0/data 192.168.1.1/24(ro,insecure,sync,all_squash,nohide,no_subtree_check,anonuid=1000,anongid=1000) Code:
service nfs-kernel-server status When doing exportfs: Code:
sudo exportfs Code:
sudo cat /proc/fs/nfsd/versions Code:
192.168.1.5:/md0/data /mnt/data nfs ro,sync,hard,intr,noexec 0 0 Code:
sudo /sbin/showmount -e 192.168.1.5 Code:
sudo mount -a -vvvv No firewall or security software installed on either machine. Absolutely nothing has changed except for Debian updates being applied once every few weeks. |
Wouldn't you have to put /mnt/md0/data into fstab? "no such file or directory" probably means that /md0/data doesn't exist on the server.
|
Quote:
But in any case, using /mnt/md0/data vs. /md0/data fixed it, thanks for helping out! |
I faintly remember the notion of an NFS root on the server, all shares being relative to that root. The client would then not mount the full pathnames of those shares, but the paths relative to that root.
This can be configured in /etc/exports. I am purely guessing now: Perhaps you used to configure it and the configuration was lost during the upgrade, possibly due to an over-eager post-install script. |
All times are GMT -5. The time now is 04:03 AM. |