Hide Forgot
Created attachment 1211760 [details] pcap file Description of problem: attached pcap file represents scenario with blocked lock: // Client_1 takes lock of a file 67 1.023190 192.168.22.110 192.168.9.100 NLM 246 V4 LOCK Call 69 1.106087 192.168.9.100 192.168.22.110 NLM 94 V4 LOCK Reply // Client_2 trying to lock the file and gets blocked status 90 5.021826 192.168.22.111 192.168.9.100 NLM 246 V4 LOCK Call 93 5.102103 192.168.9.100 192.168.22.111 NLM 94 V4 LOCK Reply NLM_BLOCKED //pending 97 25.109965 192.168.22.111 192.168.9.100 NLM 246 V4 LOCK Call 100 25.110528 192.168.9.100 192.168.22.111 NLM 94 V4 LOCK Reply NLM_BLOCKED // Client 1 unlocks the file 106 31.106284 192.168.22.110 192.168.9.100 NLM 230 V4 UNLOCK Call 109 31.106905 192.168.9.100 192.168.22.110 NLM 94 V4 UNLOCK Reply // Client_2 takes lock of a file 126 45.118343 192.168.22.111 192.168.9.100 NLM 246 V4 LOCK Call 128 45.118958 192.168.9.100 192.168.22.111 NLM 94 V4 LOCK Reply // Client unlock the file 182 115.119089 192.168.22.111 192.168.9.100 NLM 230 V4 UNLOCK Call 185 115.119639 192.168.9.100 192.168.22.111 NLM 94 V4 UNLOCK Reply After the Client 1 had unlocked the file, Server attempted to grant lock to Client 2 To did it, Server attempted to get NLM port of Client 2. But Client_2 does not listen port 111 and reset connections. The problem is that the Server went on its attempts to create connections even after Client 2 got that lock and even after Client 2 unlocked the file, until Client 2 was shutdown. Version-Release number of selected component (if applicable): Fedora 23, RHEL6.5 How reproducible: mount nfsv3, try Steps to Reproduce: 1. mount nfsv3 2. try to lock a file to get blocked status 3. do not run listener for 111 port (rpc portmap) Actual results: Fedora23, RHEL6.5 NFS Server host spam Client host Expected results: As NetApp NFS Server. It stops connecting Client host after granting lock. Additional info:
I suspect blocking port 111 on the client will create other problems, so this isn't really a configuation we should try to support. That said: (In reply to radchenkoy from comment #0) > Expected results: > As NetApp NFS Server. It stops connecting Client host after granting lock. I agree that this sounds like the nicer behavior. So, for now, I'm not convinced this should be a priority, but I'd probably accept a patch.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.