/etc/exports:
/glados 192.168.1.0/24(rw,fsid=0,no_subtree_check)
And on the client side I just did:
sudo mount 192.168.1.101:/ server/
The issue was on the exports file, I was using 192.168.0.* instead of 192.168.1.*
Damn stupid mistake!
Thanks everyone for your help!
]]>192.168.1.250:/ /mountpoint/xyz ...
and in server's /etc/exports;
/export 192.168.1.0/24 ( ... )
Hope it helps.
]]>He's able to use showmount -e 192.168.1.101 from the machine with the ip 192.168.0.99 so assumed his network's functioning ok ... but you know what they say about 'assume', which machine did you actually run the showmount command on? This might be stating the obvious, but if you ran it on 192.168.0.101 make sure 192.168.0.99 and 192.168.1.101 are communicating with each other
Also I think you're not mounting the path correctly, you have movies exported as:
/glados/movies 192.168.0.99(rw,no_subtree_check)
But you're trying to mount it as:
sudo mount -t nfs4 192.168.1.101:/movies server/
Try mounting it something like this:
sudo mount -t nfs4 192.168.1.101:/glados/movies /server/movies
That command is assuming you're wanting to put your nfs shares inside a folder called /server, also be aware that the directory you're trying to mount your shares inside of has to already exist
Incidentally, why are you mounting /glados and then also mounting directories unger /glados such as /glados/movies, by mounting /glados as an nfs share you already have access to /glados/movies. Once /glados is mounted then you can symlink to or bind mount any directories under it to any location you want
]]>On the server side:
$ nfsstat -v | grep nfs
Server nfs v4:
Server nfs v4 operations:
This tells me they're nfs v4, right?
On the client side:
$ nfsstat -c | grep nfs
Client nfs v4:
I didn't install a Firewall that I can recall. Tried mounting them as nfs and without specifying the type, and same happens. I remember on previous installations being able to just mount server:/whatever and that would work.
]]>If you haven't already try mounting them as nfs not nfs4
Firewall on the server interfering maybe?
Probably not part of your problem but I've had experiences of nfs being a bit bit fiddly when using networkmanager (especially with wifi), what I do on a netbook and laptops here is not start the services on boot, created a script that starts the services and mounts the shares with a .desktop file pointing to it for convenience, works well and it means I only have the nfs related services running when I need them as I'm a stickler for not running things I don't need (Another 'nonfs' script unmounts the shares and stops the services when I don't need the shares to be available)
]]>/glados 192.168.0.99(rw,fsid=0,no_subtree_check)
/glados/movies 192.168.0.99(rw,no_subtree_check)
And the order of the rc.conf daemons on the server:
DAEMONS=(syslog-ng dbus network @netfs crond rpcbind nfs-common nfs-server !hwclock ntpd)
On the client (laptop):
DAEMONS=(syslog-ng dbus network crond @bumblebeed @networkmanager @postgresql rpcbind nfs-common nfs-server sshd)
$ showmount -e 192.168.1.101
Export list for 192.168.1.101:
/glados/movies 192.168.0.99
/glados 192.168.0.99
Now try mount:
$ sudo mount -t nfs4 192.168.1.101:/movies server/
Here it just freezes and nothing happens. I also did the configuration both on server and client side of /etc/idmapd.conf, adding a domain.
Nothing happens on the client side when I try to mount. It just freezes there. Both machines running up to date ArchLinux.
Any help is appreciated!