Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#43181 - [nfs-utils] NFSv4 mount always ends up with port=0

Attached to Project: Arch Linux
Opened by czk (czk) - Sunday, 21 December 2014, 13:38 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 05 February 2015, 10:48 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

An NFSv4 mount always ends up with port=0 in spite of me setting port=2049:

Additional info:
* package version(s): 1.3.1-1

Steps to reproduce:

$ sudo mount -v -t nfs4 -o proto=tcp,port=2049,users,sync,rsize=131072,wsize=131072,timeo=14,noatime,soft server.name:/exported_dir /mountpoint_on_client
mount.nfs4: timeout set for Sun Dec 21 10:25:39 2014
mount.nfs4: trying text-based options 'proto=tcp,port=2049,rsize=131072,wsize=131072,timeo=14,soft,addr=192.168.1.113,clientaddr=192.168.1.132'

$ grep nfs4 /proc/mounts
server.name:/exported_dir /mountpoint_on_client nfs4 rw,sync,nosuid,nodev,noexec,noatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,port=0,timeo=14,retrans=2,sec=sys,clientaddr=192.168.1.132,local_lock=none,addr=192.168.1.113 0 0
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 05 February 2015, 10:48 GMT
Reason for closing:  Not a bug
Comment by Tobias Powalowski (tpowa) - Thursday, 05 February 2015, 10:48 GMT
The port=0 means just it takes the port the server gives it.
2049 is the standard port so there is no need to show something else here.

To me this is not a bug.

Loading...