Description of problem: rpc.nfsd no longer listens on udp after updating to 2.1.1-2.rc1.f25 or later. this isn't a trivial change which shouldn't be happened with the update. Version-Release number of selected component (if applicable): nfs-utils-2.1.1-5.rc2.fc25.x86_64 How reproducible: always Steps to Reproduce: 1.systemctl start nfs 2.rpcinfo -p | grep nfs 3. Actual results: 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl Expected results: 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100227 3 udp 2049 nfs_acl Additional info:
*** This bug has been marked as a duplicate of bug 1450765 ***
Hey, why is this a dup of bug#1450765? I have rpcbind-0.2.4-6.rc2.fc25.x86_64 installed but there are still no listens on udp. This can be worked around by adding --udp to $RPCNFSDARGS in /etc/sysconfig/nfs or "udp=y" at [nfsd] section in /etc/nfs.conf but there wasn't any announcement for such drastic changes in updates. I don't say anything on it for the future releases but should be reverted for updates.
(In reply to Akira TAGOH from comment #2) > Hey, why is this a dup of bug#1450765? > I have rpcbind-0.2.4-6.rc2.fc25.x86_64 installed but there are still no > listens on udp. you are right....this is no a dup... > > This can be worked around by adding --udp to $RPCNFSDARGS in > /etc/sysconfig/nfs or "udp=y" at [nfsd] section in /etc/nfs.conf but there > wasn't any announcement for such drastic changes in updates. With the upstream commit: commit fbd7623dd8d5e418e7cb369d4026d5368f7c46a6 Author: Jeff Layton <jlayton> Date: Wed Apr 5 13:26:49 2017 -0400 nfsd: don't enable a UDP socket by default udp sockets are off by default. > > I don't say anything on it for the future releases but should be reverted > for updates. I forgot all about that commit... I probably should have left it on for released versions... Thinking about it... why do you needed udp? using tcp is the way to go...
Dev VM instance of some project I'm getting involved forcibly uses nfs mount over udp. I don't know why they prefer it.
(In reply to Akira TAGOH from comment #4) > Dev VM instance of some project I'm getting involved forcibly uses nfs mount > over udp. I don't know why they prefer it. I would take a hard look at because you really don't want to be using udp if you doing a lot of I/O. TCP is a much better protocol because it knows how to manage network congestion.
I'm going to close this off since there is a valid workaround...
Well, "what's better" is another story. what I'm saying here is the drastic changes like changing the default behavior shouldn't be happened in the updates and this had been made without any notice and logs even. that's really the worst case.
(In reply to Akira TAGOH from comment #7) > Well, "what's better" is another story. what I'm saying here is the drastic > changes like changing the default behavior shouldn't be happened in the > updates and this had been made without any notice and logs even. that's > really the worst case. I completely agree... it was a mistake on my part... my apologies