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.
DescriptionChristophe Besson
2020-08-28 14:46:21 UTC
Description of problem:
While shutting down or rebooting, some users encounter the issue below:
~~~
<timestamp> <hostname> umount[9681]: umount: /var/log: target is busy.
<timestamp> <hostname> systemd[1]: Failed unmounting /var/log.
~~~
Disabling the persistent fixed the issue for this user.
I tried a drop-in on the systemd-journal-flush service, inspired from:
https://github.com/poettering/systemd/commit/556ec02b76482934c65686025ae4b2102867b1c1
Which is the fix for the following upstream issue:
https://github.com/systemd/systemd/issues/867
But it fails. Indeed the option for journalctl "-smart-relinquish-var" is missing in the version we deliver. It is described as is on freedesktop.org:
~~~
Similar to --relinquish-var but executes no operation if the root file system and /var/log/journal/ reside on the same mount point. This operation is used during system shutdown in order to make the journal daemon stop writing data to /var/log/journal/ in case that directory is located on a mount point that needs to be unmounted.
~~~
a) Could we backport this feature?
b) Could you evaluate if calling this option on journald-flush's ExecStop can help to get it fixed permanently?
Version-Release number of selected component (if applicable):
systemd-239-31.el8_2.2.x86_64
How reproducible:
100% for the customer
Steps to Reproduce:
1. Dedicated /var/log partition
2. Persistent journal (/var/log/journal)
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 (systemd 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-2023:2985