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.
DescriptionMichal Sekletar
2018-02-14 11:19:59 UTC
Description of problem:
After a client opens the journal with sd_journal_open() it has an open fd to at least one journal file. sd-journal code sets up inotify watch so that it can notice events like addition/removal of journal files. If there is a lot of activity on the journald side and client doesn't process inotify events in a timely manner then inotify queue can overflow. If that happens and we lost some events informing the client about removed files then the client will never close the corresponding fd which keeps the file pinned and a filesystem is unable to free the disk blocks.
Version-Release number of selected component (if applicable):
systemd-219-42.el7_4.7
How reproducible:
sometimes (needs high rate of logging, the low retention time for journal files and slow client)
Steps to Reproduce:
1. See attached reproducer
Actual results:
The client holds references to deleted journal files.
Expected results:
Client notices overflow of inotify queue and reconciles in-memory state with the current state of the log directory.
Additional info:
https://github.com/systemd/systemd/pull/8144