Arch Linux

inkdinky

Member

Registered: 2011-12-08

Posts: 66

[Solved] NFS newb: Get timeout when trying to connect via command line

I'm having some problems with NFS.
I am attempting to setup a server on a BeagleBone Black (ArchARM). I realize that there are some issues with ARM *clients* connecting to an NFS.

Here is my `/etc/exports`

#/srv/nfs4/Remote 192.168.1.139(ro,fsid=0)                192.168.1.130(ro,fsid=0)
/srv/nfs4/SGOne 192.168.1.139(ro,no_subtree_check,nohide) 192.168.1.130(ro,no_subtree_check,nohide)
/srv/nfs4/SGTwo 192.168.1.139(ro,no_subtree_check,nohide) 192.168.1.130(ro,no_subtree_check,nohide)

and my `/etc/fstab`

UUID=40898631-b5a5-4865-a8e7-7031eb872558       /home/beagleboneblack/Remote/SGOne      ext4    defaults,noatime        0       2
UUID=4b1b61e5-4b65-41a6-b58a-b1f59be3e95f       /home/beagleboneblack/Remote/SGTwo      ext4    defaults,noatime        0       2


#/home/beagleboneblack/Remote             /srv/nfs4/Remote     none      bind    0       0
/home/beagleboneblack/Remote/SGOne       /srv/nfs4/SGOne      none      bind    0       0
/home/beagleboneblack/Remote/SGTwo       /srv/nfs4/SGTwo      none      bind    0       0

I only setup nfs4 so I added `NFSD_OPTS="-N 2 -N 3"` to '/etc/conf.d/nfs-server.conf'.

I am attempting to connect to the NFS from an x86_64 Arch using

sudo mount 192.168.1.138:/ Remote/SGOne/

where  192.168.1.138 is the ip of the BeagleBone Black.

This then gives me this as the directory structure:

/home/puffjay/Remote/SGOne/srv/nfs4/SGOne/

If I umount Remote/SGOne and try again with

sudo mount 192.168.1.138:/SGOne Remote/SGOne/

I get

mount.nfs: Connection timed out

I would like this in the end to be done by `/etc/fstab` and currently have this in the client's :

192.168.1.138:/SGOne                            /home/puffjay/Remote/SGOne              nfs4                    rsize=8192,wsize=8192,timeo=14,_netdev  0 0
192.168.1.138:/SGTwo                            /home/puffjay/Remote/SGTwo              nfs4                    rsize=8192,wsize=8192,timeo=14,_netdev  0 0

Where am I going wrong?
Does it have something to do with the NFS root? I have that line commented out in the server's /etc/exports because I wasn't sure if I needed it and what purpose it served.

Thanks in advance.

Last edited by inkdinky (2015-08-11 14:23:17)

graysky

Wiki Maintainer

From: :wq

Registered: 2008-12-01

Posts: 10,697

Website

Re: [Solved] NFS newb: Get timeout when trying to connect via command line

I recommend that you follow the wiki retaining the NFS root.  I haven't experienced a problem with this setup with ARM devices or x64 devices.

---

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packages • Zsh and other configs

inkdinky

Member

Registered: 2011-12-08

Posts: 66

Re: [Solved] NFS newb: Get timeout when trying to connect via command line

You were correct it appears to have been a problem with the NFS root.
changing my `/etc/exports` to have this:

/srv/nfs4/ 192.168.1.139(ro,fsid=0)                192.168.1.130(ro,fsid=0)

(notice the removal of the `Remote` path) seemed to be all that I needed to do.

Now on my client machine the `/etc/fstab` is mounting those served directories.

Thanks.