bashrc, and these would trigger the automounts. However, for build systems that may have their working directory set to another location, they may still access content from /home like. ![]() The expiration logic probably doesn't trigger in this case, because it cannot be unmounted. For regular uses, this one is likely safe due to held open files including set working directories that would prevent the user's /home from being unmounted. This applies to all of the below concerns, in that wouldn't unmount of the NFS file system cause the cache to be invalidated, and wouldn't this cause performance issues during each of the use cases I am about to describe?Ģ) /home directories. There are a few main areas of concern for me:ġ) Caching. In our case, we have thousands of clients, and thousands of automounts configured via LDAP. Specifically related to sfdc case 01909702, customer usage and concerns are as followed: The new behavior seems to have been implemented in the below BZ and commit: The desire it to return the prior RHEL7.3 behavior in which path traversal results in a timeout refresh. The mount point has a unmount event once the timeout hits, even though the network traffic and debug show that the mount point is being traversed. ![]() Check the /var/log/messages, observation that automount is unmounted and remounted several times during the test (typically equal to the number of timeout periods) ![]() Allow some time (2-3x timeout period) to pass then kill bash command # while true do df /nfs/ >/dev/null sleep 10 done Create autofs mount (ideally with some low timeout for testing): Installed generic versions of autofs, nfs and rpcbind packages Libsss_autofs-1.15.86_64 Tue Aug 15 11:58:45 2017Īlways, with 'ls' and 'df' commands additionally occurs with 'noac' mount option. Version-Release number of selected component (if applicable): Prior to RHEL7.4 if a path was traversed this would renew the timeout value.Īdditionally, the hope for this BZ is to gain additional details on the new behavior and address some of the concerns in case 01909702 This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.Īutofs will unmount within the specified timeout regardless of queries/stats of the mount point. 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 " ", where " X" is a digit). Individual Bugzilla bugs that are migrated will be moved to status " CLOSED", resolution " MIGRATED", and set with " MigratedToJIRA" in " Keywords". ![]() The email creates a ServiceNow ticket with Red Hat. That failing, please send an e-mail to the RH Jira admins at to troubleshoot your issue as a user management inquiry. If you cannot log in to RH Jira, please consult article #7032570. Bugs against components " kernel", " kernel-rt", and " kpatch" are only migrated if still in " NEW" or " ASSIGNED". Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Individual Bugzilla bugs in the statuses " NEW", " ASSIGNED", and " POST" are being migrated throughout September 2023. If you're not, please head to the " RHEL project" in Red Hat Jira and file new tickets here. If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira ( ).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |