Bug 246254 - mount.nfs unnecessarily passes a socket to the kernel
Summary: mount.nfs unnecessarily passes a socket to the kernel
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: nfs-utils   
(Show other bugs)
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Steve Dickson
QA Contact:
Depends On: 240780
TreeView+ depends on / blocked
Reported: 2007-06-29 16:31 UTC by Jeff Layton
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version: RHBA-2007-0651
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 17:15:45 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:0651 normal SHIPPED_LIVE nfs-utils bug fix and enhancement update 2007-10-30 16:19:49 UTC

Comment 1 Jeff Layton 2007-06-29 16:36:08 UTC
RHEL5's mount.nfs allocates a socket, binds it to a reserved port and then
passes that socket to the kernel. The kernel then ignores this socket and
creates one of its own. On a machine with a lot of NFS mount activity, this can
contribute to reserved port exhaustion.

This upstream patch should help alleviate this. We should consider its inclusion
for RHEL5:


Comment 2 Steve Dickson 2007-07-05 19:36:49 UTC
Fixed in nfs-utils-1.0.9-23.el5.i386.rpm 

Comment 7 Steve Dickson 2007-08-31 19:05:17 UTC
fixed in nfs-utils-1.0.9-24.el5

Comment 8 Steve Dickson 2007-08-31 19:46:17 UTC
I'm using the following scripts and don't see the problem:
for i in `seq 1 1020`
    [ ! -d /mnt/tree/$i ] && mkdir -p /mnt/tree/$i
    $MOUNT -o tcp rhel4hat:/home/tree/$i /mnt/tree/$i || exit 1
    ls -d /mnt/tree/$i;

and then to unmount I do:

for i in `seq 1 1020`
    umount /mnt/tree/$i || exit 1;

Comment 17 errata-xmlrpc 2007-11-07 17:15:45 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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