Bug 1552082 - Mount count bug in nitirpc causes mounts to stop after a while
Summary: Mount count bug in nitirpc causes mounts to stop after a while
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: nfs-ganesha
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.4.0
Assignee: Daniel Gryniewicz
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks: 1503137
TreeView+ depends on / blocked
 
Reported: 2018-03-06 13:23 UTC by Daniel Gryniewicz
Modified: 2018-09-24 10:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 06:54:24 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/nfs-ganesha nfs-ganesha issues 270 0 None None None 2018-03-09 16:24:40 UTC
Red Hat Product Errata RHEA-2018:2610 0 None None None 2018-09-04 06:55:33 UTC

Description Daniel Gryniewicz 2018-03-06 13:23:14 UTC
Description of problem:

Repeated mount/unmount in a loop causes mounts to start failing.


Version-Release number of selected component (if applicable):

nfs-ganesha 2.5.x (actually in ntirpc 1.5.x)


How reproducible:

100%

Steps to Reproduce:
1.Set RPC_Max_Connections = 10
(This is not necessary, it just makes reproduction quicker)
2.mount/unmount in a loop:
while ${true}; do  mount -t nfs <server>:/<path> /<path>; echo "again"; done


Actual results:
Mount stops after 10 (or whatever is in RPC_Max_Connections; default 1024)

Expected results:

Mounts should continue forever



Additional info:

Comment 5 Manisha Saini 2018-03-09 16:32:26 UTC
Sure Kaleb. Will add the test for the same .Thanks..

Comment 11 errata-xmlrpc 2018-09-04 06:54:24 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2610


Note You need to log in before you can comment on or make changes to this bug.