Bug 161358

Summary: ghosted wildcard mounts from NIS maps fail to remount properly after timeout
Product: Red Hat Enterprise Linux 3 Reporter: David Lehman <dlehman>
Component: autofsAssignee: Chris Feist <cfeist>
Status: CLOSED ERRATA QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: jmoyer, poelstra
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: RHBA-2006-0043 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-15 15:31:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 168426, 173829    
Description Flags
log output from reproducer none

Description David Lehman 2005-06-22 17:20:21 UTC
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 19:38:28 UTC
Chris, can you take a look at this?

Comment 27 Red Hat Bugzilla 2006-03-15 15:31:49 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.