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 can still see this issue in RHEL-8.6.0-20220312.3-x86_64-dvd1.iso
[root@shshang-rhel8 ~]# rm -rf sa.new ; strace -fttT -o sadc.trc /usr/lib64/sa/sadc -F -L 1 2 sa.new ; grep mtab sadc.trc
16188 16:55:16.100156 openat(AT_FDCWD, "/etc/mtab", O_RDONLY) = 3 <0.000079>
[root@shshang-rhel8 ~]# uname -r
4.18.0-372.el8.x86_64
[root@shshang-rhel8 ~]# rpm -q sysstat
sysstat-11.7.3-7.el8.x86_64
Comment 11Frantisek Sumsal
2022-03-14 10:33:14 UTC
IIUC, reading /etc/mtab is fine, the original issue is about calling statfs() on the autofs handle, thus triggering the auto mount. CC'ing @msekleta for confirmation.
Here is test result from RHEL-9 and I do not find 1670060 changed the pass criteria.
I am adding needinfo to Michal.
[root@localhost ~]# uname -r
5.14.0-75.el9.x86_64
[root@localhost ~]# rm -rf sa.new ; strace -fttT -o sadc.trc /usr/lib64/sa/sadc -F -L 1 2 sa.new ; grep mtab sadc.trc
[root@localhost ~]# echo $?
1
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (sysstat bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:1892
(In reply to Frank Liang from comment #12)
> Here is test result from RHEL-9 and I do not find 1670060 changed the pass
> criteria.
> I am adding needinfo to Michal.
>
> [root@localhost ~]# uname -r
> 5.14.0-75.el9.x86_64
> [root@localhost ~]# rm -rf sa.new ; strace -fttT -o sadc.trc
> /usr/lib64/sa/sadc -F -L 1 2 sa.new ; grep mtab sadc.trc
> [root@localhost ~]# echo $?
> 1
As mentioned previously reading mtab in of itself is not a problem. Issue was calling statvfs() on autofs filesystems which caused them to automount. This is now fixed and RHEL-9 contains this fix as well.