Red Hat Bugzilla – Bug 238529
autofs can return incorrect status from mount under heavy load
Last modified: 2008-05-21 10:37:23 EDT
Description of problem:
During heavy mount and umount activity it is possible
foe the /etc/mtab to get out of sync with what is
actually mounted. This issue was resolved in autofs
version 4 in RHEL-3 and 4 by changing autofs to use
/proc/mounts instead of /etc/mtab.
This approach isn't feasible in version 5 because of
the possibility of there being many more entries in
/proc/mounts than in /etc/mtab leading to performance
issues given the heavy use of checking the mount table.
The approach to be used in version 5 is to use the return
code from mount to check that the mtab has been updated
and if not call mount again to allow the mtab update.
Steps to Reproduce:
To be determined from upstream reports as part of
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #0)
> > > How reproducible:
> > > With difficulty.
> > >
> > > Steps to Reproduce:
> > > To be determined from upstream reports as part of verification.
> > Would you provide a few pointers?
> Yes, sorry about the vague nature of this bug.
> The reason I logged this bug is that we've seen this very
> often and so I fixed it upstream. Version 5 requires a
> different approach to version 4.
See bugs 191210 and 191213 for RHEL3 and 220506 for RHEL-4.
It is a bit harder to trigger in version 5 but I should be
able to construct a reproducer out of these bugs.
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.