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.
I am trying to use autofs to automatically mount paths on my stackable fs when they are accesssed and unmount them after the configured 'timeout' limit set in auto.master config file.
I normally use my <custom> application to mount/unmount paths.
My auto.master configuration file and my rule file look like below-
[root@localhost ~]# cat /etc/auto.master
/- /etc/auto.rule --timeout=60
[root@localhost ~]# cat /etc/auto.rule
/1 -fstype=<custom>fs :/1
Let's assume that /1 is the path that I am trying to mount on my stackable fs.
But after 60 seconds of inactivity on the path, autofs is not able to automatically unmount it from my stackable fs.
The last autofs logs that I see are -
[root@localhost sbin]# ./automount -v -f
Starting automounter version 5.0.5-123.el6, master map auto.master
using kernel protocol version 5.02
lookup_read_master: lookup(nisplus): couldn't locate nis+ table auto.master
lookup(file): failed to read included master map auto.master
mounted direct on /1 with timeout 60, freq 2 seconds
< Nothing displayed after this >
Is autofs really trying to un-mount since there are no logs related to that, as shown above? Please explain as to how I would be able to achieve un-mounting using the autofs through timeout option. Only when I restart the autofs service am I able to see the path getting un-mounted from my stackable fs.
Thanks
(In reply to hkaur from comment #0)
> I am trying to use autofs to automatically mount paths on my stackable fs
> when they are accesssed and unmount them after the configured 'timeout'
> limit set in auto.master config file.
> I normally use my <custom> application to mount/unmount paths.
>
> My auto.master configuration file and my rule file look like below-
> [root@localhost ~]# cat /etc/auto.master
> /- /etc/auto.rule --timeout=60
>
> [root@localhost ~]# cat /etc/auto.rule
> /1 -fstype=<custom>fs :/1
>
> Let's assume that /1 is the path that I am trying to mount on my stackable
> fs.
Looks like that can't work.
In order to trigger mounts automount managed paths need to
be either the root of or contained in an autofs file system.
Otherwise the kernel won't be aware the path has been accessed
and won't be able to call back to the user space daemon to a
perform mount.
In auto.rule you are mounting a direct mount trigger on path /1
so it covers the original mount at /1. So if it is accessed it
will try and mount itself.
That's probably enough to hang the mount.
Ian
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/