Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
It is a clone bug from https://bugzilla.redhat.com/show_bug.cgi?id=787595
Running "/bin/ls --color=auto" on directory with a large amount of symlinks to automounted NFS filesystems takes over 10 minutes, whereas the same command runs in less than 2 seconds on an identically configured RHEL5.7 system.
Running "top" while the "ls" is running shows that for each symlink the system tries to mount the linked NFS filesystem, but since some of the NFS servers listed in the automount map aren't available some of the mounts hang until the timeout is reached.
It is a regression issue. It had been fixed in RHEL6.1. But now have this issue on nfs-utils-1.2.3-73.el6.x86_64.rpm
Test on nfs-utils-1.2.3-71.el6.x86_64.rpm:
[06:14:15 root@ ~~]# time /bin/ls --color=auto /mnt/${TESTNAME}/*
/mnt/bz787595/bin
/mnt/bz787595/man
/mnt/bz787595/etc:
/mnt/bz787595/lib:
real 1m26.434s
user 0m0.000s
sys 0m0.004s
Tested on nfs-utils-1.2.3-73.el6.x86_64.rpm:
[06:23:15 root@ ~~]# time /bin/ls --color=auto /mnt/${TESTNAME}/*
/mnt/bz787595/bin
/mnt/bz787595/man
/mnt/bz787595/etc:
/mnt/bz787595/lib:
real 6m18.493s
user 0m0.000s
sys 0m0.006s
Version-Release number of selected component (if applicable):
nfs-utils-1.2.3-73.el6.x86_64.rpm
How reproducible:
100%
Steps to Reproduce:
1. verify that automounter is running
2. run "/bin/ls --color=auto" on dir with symlinks to automounted NFS filesystems
3. wait a long time for output
Actual results:
"/bin/ls --color=auto /mnt/${TESTNAME}/*" need about 6 minute
Expected results:
"/bin/ls --color=auto /mnt/${TESTNAME}/*" need about 1 minute
Additional info:
Steve,
I've worked out what's happening here, please have a look at
comments #26 and #27 of bug 1350786.
I need "mount.nfs -V" to work, I'd appreciate it very much if
you could fix it in revision 73. There might not be a lot that
can be done about the delay we see attempting nfs mounts to
servers that aren't available.
Ian
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://rhn.redhat.com/errata/RHBA-2017-0741.html