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.
Description of problem:
It seems that systemd-readahead collect tries to touch/create/write /.readahead.
This leads to an error on systems where / is read-only.
Can't read-ahead touch a different file?
Version-Release number of selected component (if applicable):
RHEL 7
How reproducible:
Always
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
I think simple ConditionPathIsReadWrite should do the trick. Hence we would skip collecting read-ahead profile when / is read-only. That would mean users won't get benefits of read-ahead on such systems, but I recon not that many people care for read-ahead these days.
If we use different file then we could run into the same issue.
(In reply to Michal Sekletar from comment #8)
> I think simple ConditionPathIsReadWrite should do the trick. Hence we would
> skip collecting read-ahead profile when / is read-only. That would mean
> users won't get benefits of read-ahead on such systems, but I recon not that
> many people care for read-ahead these days.
>
> If we use different file then we could run into the same issue.
Lukas pointed out that adding condition doesn't cut it, because we need to check the condition after rootfs was remounted. However we can't simply add After=systemd-remount-fs.service, because that would introduce circular dependency.
We need to figure out something else.
Currently when one enables read-only root via /etc/sysconfig/readonly-root it is still necessary to specify "ro" option for rootfs mount in fstab to actually get read-only filesystem. This is a bug in initscripts.
Proposed solution is to have generator that parses /etc/sysconfig/readonly-root and changes generated mount unit so that rootfs is actually mounted read-only w/o user intervention in fstab. Same generator could also runtime mask systemd-readahead-collect.service in such case.
Reassigning to initscripts.
JoeK, our HPE 1191750 is already closed as won't fix so I am marking HPE verified on this bug.
Comment 16David Kaferad // Dee'Kej
2017-11-01 09:17:19 UTC
Hello Joseph,
based on the comment 12 I still don't think this is fixed. If it is really an issue, silently ignoring it might mean than some day in the future it will come back haunting us again (no Halloween reference intended :D).
I'd like to discuss this more with Michal Sekletar when he's back, so I would keep this BZ open for now. :)
-- Dee'Kej --
Comment 17David Kaferad // Dee'Kej
2018-03-05 14:21:36 UTC
After a discussion with Lukas we have decided to close this BZ as WONTFIX. The HPE bug is already closed, and upstream no longer supports (or cares) about readahead, so there's high chance it won't be in next major RHEL releases.