You are not logged in.
I'm having issues mounting a NFS share located on an Arch based server from an Arch based client (I've successfully mounted the same share many a time from Lubuntu/Ubuntu). Network subnet's etc. are all fine with IPs provided by my ADSL router. When, however, I try to NFS mount a share on my server (192.18.168.108) the share does not show up on the client -
showmount -e 192.18.168.108
results in a hanging cursor in the client machine's terminal window.
Server config:
cat /etc/exports
returns:
# /etc/exports - exports(5) - directories exported to NFS clients
#
#
# Use `exportfs -arv` to reload.
/srv/nfs4 192.168.168.0/24(rw,no_subtree_check,async)
Excerpt from
cat /etc/fstab
returns:
# mount raid array
UUID=ec10abf5-40c4-4ca5-8f95-77ae05431510 /mnt/md0 ext4 user,noatime,noexec,nodev 0 0
# bind nfs share
/mnt/md0 /srv/nfs4 none bind 0 0
mount
returns:
/dev/md0 on /mnt/md0 type ext4 (rw,nosuid,nodev,noexec,noatime,stripe=512,data=ordered)
/dev/md0 on /srv/nfs4 type ext4 (rw,nosuid,nodev,noexec,noatime,stripe=512,data=ordered)
exportfs -v
returns:
/srv/nfs4 192.168.168.0/24(rw,async,wdelay,root_squash,no_subtree_check,sec=sys,rw,root_squash,no_all_squash)
On the client side I've done the following:
sudo pacman -Sy nfs-utils
sudo systemctl enable rpcbind.service
sudo systemctl start rpcbind.service
systemctl enable nfs-client.target
systemctl start nfs-client.target
For some reason NFS shares on Arch have always been problematic for me. What am I missing/ have I overlooked?
Last edited by audiomuze (2014-10-06 16:23:45)
Linux user #338966
Offline
192.168.168.xxx ? The address from the ADSL router, are you sure its' not 192.168.254.xxx ? Did you sudo enable/start nfs-client.target? Did you check the other nfs services such as nfs-mountd, nfs-idmapd, etc. to see if they came as their dependencies?
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
... 192.18...
... 192.168...
You have each of these twice, otherwise I'd assume it was just a typo.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
audiomuze wrote:... 192.18...
... 192.168...You have each of these twice, otherwise I'd assume it was just a typo.
Aaargh!!!! Damnit, I cannot believe I didn't pick this up - it was a typo, not in my post, but in the what I'd been doing in the terminal session. Thank you.
Re the IP range I'm 100% sure on that part - it's a change I made to accommodate some static IP's I'd set up years ago on some older devices.
Linux user #338966
Offline
Now I'm getting:
showmount -e 192.168.168.108
clnt_create: RPC: Program not registered
rpcinfo -p 192.168.168.108
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
Linux user #338966
Offline
Check your nfs related services on the server and the client.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline