Cannot mount NFS share (Fstab special character at the end of the mount)

meki · 12-31-2015, 01:58 PM

Hopefully this is the right place to ask this.
I have read and read everywhere about this issue and cannot figure it out.

I am trying to mount an exported mount

Code:

sudo showmount -e 192.168.1.173
Export list for 192.168.1.173:
/mnt/user/Documentaries (TV)    192.168.1.38
/mnt/user/Documentaries (Movie) 192.168.1.38

In my fstab I put

Code:

192.168.1.173:/mnt/user/Documentaries\040\050TV\051 /mnt/Documentaries_TV       nfs     noatime,vers=3,auto,rw,dev,exec,suid,rsize=32768,wsize=32768 0 0

But it wont mount
when I do

Code:

mount -a

I get this

Code:

sudo mount -a
mount.nfs: access denied by server while mounting 192.168.1.173:/mnt/user/Documentaries (TV\051

If I put another character after \051 then the next character is detected

Code:

sudo mount -a
mount.nfs: access denied by server while mounting 192.168.1.173:/mnt/user/Documentaries (TV)test

It seems that the last character is not parsed.

I am really lost here I am hoping someone can help

jpollard · 01-01-2016, 07:45 AM

Welcome to the world of special characters...

They are not recommended for use.

The problem is that mount isn't the one evaluating the title - it is mount.nfs. Mount -a just passes the strings to mount.nfs, which in turn has to pass it to a remote system.

For testing purposes you can try "mount.nfs" and quoting the desired strings. This will isolate the problem to the handoff between the mount command and the mount.nfs, or between mount.nfs and server.

What distributions/versions are the client and server?

meki · 01-01-2016, 09:36 AM

Quote:

Originally Posted by jpollard

Welcome to the world of special characters...

They are not recommended for use.

The problem is that mount isn't the one evaluating the title - it is mount.nfs. Mount -a just passes the strings to mount.nfs, which in turn has to pass it to a remote system.

For testing purposes you can try "mount.nfs" and quoting the desired strings. This will isolate the problem to the handoff between the mount command and the mount.nfs, or between mount.nfs and server.

What distributions/versions are the client and server?

I kind of caved and updated my remote share to to eliminate special characters which I REALLY didn't want to do...

It was just too much trouble, I still would like to get to the bottom of this though

Here is what half-worked:

If in fstab I added "/" at the end of the

Code:

192.168.1.173:/mnt/user/Documentaries\040\050TV\051/ /mnt/Documentaries_TV       nfs     noatime,vers=3,auto,rw,dev,exec,suid,rsize=32768,wsize=32768 0 0

Code:

mount -a

works!

BUT

Upon restarting of the system fstab mounts every other mount except the one above.

If I issue mount -a when I login it mounts fine! What gives!?!?

Now to answer your questions:

Server is Unraid OS 6.1.6 (Which is slackware based I believe)

Client is Ubuntu Server Ubuntu Server LTS 14.04.03

Do you still want me to try mount.nfs or does above stuff give you enough idea?

jpollard · 01-01-2016, 10:19 AM

Part of the reason to try it is because there are different things doing a mount at different times.

I believe Ubuntu Server has moved to systemd, so normal mounts are no longer done by the mount utility (or the mount.nfs). Instead they are mounted by systemd... which could introduce additional incompatibilities (one being that the fstab option "_netdev" needs to be added so systemd can tell what has to wait until after the network is operational).

I was curious about whether the trims were being done by mount when reading the fstab file, or when passing the strings to mount.nfs. Using the mount.nfs would separate the issues. It almost looked like it was going through a shell somewhere, in which case the () and blank are handled uniquely - the close parenthesis gets chopped when it is parsing a subshell operation.