FS#24286 - [nfs-utils] Unable to mount nfs v3 shares with nfs-utils 1.2.3
Attached to Project:
Arch Linux
Opened by (N/A) (wantilles) - Sunday, 15 May 2011, 14:47 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 18 June 2011, 09:58 GMT
Opened by (N/A) (wantilles) - Sunday, 15 May 2011, 14:47 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 18 June 2011, 09:58 GMT
|
Details
Description:
Clients are unable to mount nfs v3 shares from a server, using nfs-utils 1.2.3. The same setup was working flawlessly with nfs-utils 1.2.2. Additional info: * package version(s) nfs-utils-1.2.3-2 - Server is running latest kernel26-lts - Clients are running latest kernel26 - Downgrading nfs-utils to 1.2.2 restores full functionality * config and/or log files etc. Steps to reproduce: Enter one or more lines in the /etc/exports on the server like: <xxxxxxxxxxxxxxxxxx> 192.168.1.0/24(sync,no_root_squash,rw,nohide) Declare them on the /etc/fstab of the clients: <xxxxxxxxxxxxxxxxxx> <yyyyyyyyy> nfs noatime,bg,hard,rsize=32768,wsize=32768 0 0 Do a: mount -a -t nfs on the clients Result: mount.nfs: access denied by server while mounting <xxxxxxxxxxxxxxxxxx> while it mounts perfectly with nfs-utils 1.2.2. |
This task depends upon
[root@vendhya pacman]# /etc/rc.d/nfs-server start
:: Mounting nfsd filesystem [DONE]
:: Exporting all directories [DONE]
:: Starting rpc.nfsd daemon [FAIL]
Reverting to nfs-utils 1.2.2 resolves this.
Note: this is on i686.
[root@vendhya ~]# /etc/rc.d/nfs-server start
:: Mounting nfsd filesystem [DONE]
:: Exporting all directories [DONE]
:: Starting rpc.nfsd daemon [DONE]
:: Starting rpc.mountd daemon [BUSY] /usr/sbin/rpc.mountd: bad version number: 1
Usage: /usr/sbin/rpc.mountd [-F|--foreground] [-h|--help] [-v|--version] [-d kind|--debug kind]
[-o num|--descriptors num] [-f exports-file|--exports-file=file]
[-p|--port port] [-V version|--nfs-version version]
[-N version|--no-nfs-version version] [-n|--no-tcp]
[-H ha-callout-prog] [-s|--state-directory-path path]
[-g|--manage-gids] [-t num|--num-threads=num]
[FAIL]
[root@vendhya ~]# /etc/rc.d/nfs-server stop
:: Stopping rpc.mountd daemon [FAIL]
[root@vendhya ~]# /etc/rc.d/nfs-server start
:: Mounting nfsd filesystem [DONE]
:: Exporting all directories [DONE]
:: Starting rpc.nfsd daemon [FAIL]
Which was fixed by removing the "--no-nfs-version 1" from MOUNTD_OPTS in /etc/conf.d/nfs-server.conf
NFSv4 works as expected.
Sorry again.
The bug report talks about v3, not v4.
And v3 does not work, with the above-mentioned error messages.
The server has (has had for years) the following line in its nfs-server.conf:
MOUNTD_OPTS="--no-nfs-version 1 --no-nfs-version 2 --nfs-version 3"
And nfs-utils 1.2.3, as mentioned before, does not work.
Downgrading to 1.2.2 restores full functionality.
You should take care about all incoming *.pacnew files! The option MOUNTD_OPTS="--no-nfs-version 1" is not default! Please compare what the nfs-utils package is shipping nowadays.
However, we are not talking about nfs v1 here, but about nfs v3.
Unless you are saying that in nfs-utils 1.2.3, the "--no-nfs-version 1" was deprecated / became invalid, and when that line of nfs-server.conf was parsed, it was ignored completely due to the now invalid option.
If that was the case, and such crucial/critical change in configuration files was needed - crucial because of the impact it has - why was not a relevant news entry issued in the main www.archlinux.org page?
Again the "--no-nfs-version 1" deprecation is a hypothesis, I am making here.
I haven't done any relevant testing yet.
-N or --no-nfs-version vers
This option can be used to request that rpc.nfsd does not offer certain versions of NFS. The current version of rpc.nfsd can support both NFS version 2,3 and the newer version 4.
Time is changing. Don't expect a news entry on every change that may happen in out packages.