Bug 161358 - ghosted wildcard mounts from NIS maps fail to remount properly after timeout
ghosted wildcard mounts from NIS maps fail to remount properly after timeout
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: autofs (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Feist
Brock Organ
Depends On:
Blocks: 168426 173829
  Show dependency treegraph
Reported: 2005-06-22 13:20 EDT by David Lehman
Modified: 2007-12-05 11:24 EST (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2006-0043
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-15 10:31:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
log output from reproducer (20.12 KB, text/plain)
2005-06-22 13:23 EDT, David Lehman
no flags Details

  None (edit)
Description David Lehman 2005-06-22 13:20:21 EDT
Description of problem:
First access of a given expansion of a wildcard key in an NIS map with --ghost
option works fine. If you then leave that directory and allow it to time out and
then try to access it again it shows as though it's not mounted.

Version-Release number of selected component (if applicable):
[root@whiskey root]# uname -r
[root@whiskey root]# rpm -q autofs

How reproducible:

Steps to Reproduce:
1. Set up a ghosted NIS map containing a wildcard mount
2. access the mount
3. allow it to time out and unmount
4. access the mount
Actual results:
second access shows the dir as though it wasn't mounted while mount says it is
mounted. NOTE: subsequent accesses seem to work fine.

Expected results:
second access works

Additional info:
This only happens with wildcard entries in ghosted NIS maps.
Comment 3 Jeff Moyer 2005-06-27 15:38:28 EDT
Chris, can you take a look at this?
Comment 27 Red Hat Bugzilla 2006-03-15 10:31:49 EST
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.