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:
Request to add "journalctl --disk-usage" output in sosreport
Version-Release number of selected component (if applicable):
sos-3.2-35.el7.noarch
Currently, the sosreport doesn't collect "journalctl --disk-usage".
It would be good to collect the data in sosreport.
Could you please elaborate why this information would be valuable to collect?
Can't be the same information extracted from current data, e.g. from size of
sos_commands/logs/journalctl_--all_--this-boot_--no-pager_-o_verbose
(though not sure how --this-boot can affect it - with default journald settings, these values match before and also after reboot)?
> Can't be the same information extracted from current data, e.g. from size of
>
> sos_commands/logs/journalctl_--all_--this-boot_--no-pager_-o_verbose
No: that is a text rendering of the journal contents. The journal itself is stored in a binary format with additional metadata. Although the size of journal logs approximates the size of the journal they do not measure the same thing.
http://www.freedesktop.org/wiki/Software/systemd/journal-files/
This is also useful since it presents a global summary of disk usage rather than piecemeal per-file, e.g. (Fedora 23):
# journalctl --disk-usage
Archived and active journals take up 640.1M on disk.
With all that said on RHEL7 it is slightly less interesting/accurate:
# journalctl --disk-usage
Journals take up 96.0M on disk.
Although it is true that there are 96.0M of journal files present on this system:
# du -ch /run/log/journal/
96M /run/log/journal/8f1a41c7c31a4575bd21b465748f123c
96M /run/log/journal/
96M total
These are all on the non-persistent (in-memory) /run file system - RHEL7 does not use persistent journald logs at all by default so this will only ever measure the size of the logs from the current boot.
That said I don't see any reason to not collect this & it is then available for other distributions (like Fedora) that do already offer persistent journald logs by default.