[SOLVED] nfs failing

stockton · 05-20-2018, 12:35 PM

When I run the following command I get these errors:-

Code:

sudo mount -t nfs -vo nolocks 192.168.0.120:music /mnt/nfs
mount.nfs: timeout set for Sun May 20 19:21:38 2018
mount.nfs: trying text-based options 'nolocks,vers=4,addr=192.168.0.120,clientaddr=192.168.0.150'
mount.nfs: mount(2): Invalid argument
mount.nfs: an incorrect mount option was specified

music at 192.168.0.120 exists but is a link created with

Code:

ln -sv /media/pi/My\ Passport/Media/music music

and the reason for creating the link is to get past the space in the name of the folder to which I really want to link/nfs connect to.
As I say I would really like to nfs link to /media/pi/My Passport/Media/music rather than go indirectly, so please tell me how I do this.
I have attempted connecting from the client to /media/pi/My Passport/Media/music directly by placing double quotes around it as well as inserting \space rather than just space as well as both double quotes and \space. All fail by not being able to interpret /media/pi/My Passport/Media/music correctly. All attempts fail at the space.

yancek · 05-20-2018, 01:14 PM

Quote:

mount.nfs: an incorrect mount option was specified

Your mount option is incorrect as indicated in the output. You need the path to the location on the machine you are trying to access and you don't show a correct path.

Code:

sudo mount -t nfs -vo nolocks 192.168.0.120:music

You need at least a forward slash in front of music and that will only work if music is in the / (root) of the filesystem so put the correct path where the directory is on 192.168.0.120.

stockton · 05-21-2018, 04:04 AM

That made no difference as can be seen by:-

Code:

sudo mount -t nfs -vo nolocks 192.168.0.120:/home/pi/music /mnt/nfs
mount.nfs: timeout set for Mon May 21 11:04:35 2018
mount.nfs: trying text-based options 'nolocks,vers=4,addr=192.168.0.120,clientaddr=192.168.0.150'
mount.nfs: mount(2): Invalid argument
mount.nfs: an incorrect mount option was specified

michaelk · 05-21-2018, 04:35 AM

The correct syntax is nolock not nolocks.

Whether you need the option or not depends on what nfs version or if your running the rpc.statd daemon.

stockton · 05-21-2018, 07:13 AM

Thank you that worked.