As per Summary this is regression compared to 2.20 series. The relevant fstab entry: 192.168.137.10:/data/ /home/data/ nfs4 intr,async,bg,exec,nosuid,user 0 0 Mount state: 192.168.137.10:/data/ on /home/data type nfs4 (rw,user=root,noexec,nosuid,nodev,intr,bg,addr=192.168.137.10,clientaddr=192.168.137.1) Latest release (2.22.2) still shows the problem.
from the man page: user Allow an ordinary user to mount the filesystem. The name of the mounting user is written to mtab so that he can unmount the filesystem again. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line user,exec,dev,suid). in your mount option, you put "user" after "exec" which means it's the same as: intr,async,bg,exec,nosuid,noexec,nosuid,nodev and you can see "exec" is clobbered by the "noexec" later
