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:

lvm commands do not put any messages into syslog (/var/log/messages) by default.
Important events or changes that the user does not explicitly request should be recorded there by default.  For example, if the metadata on a device has become damaged or out of date and lvm decides to repair it, a message should record which device was repaired and why.  Or, when any sort of automatic LV repair is performed, a message should indicate this.  Some syslog messages are already added by commands run by dmeventd, e.g. full thin pool.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Alasdair had some good suggestions about broadening this idea to include a text log of all metadata changes.

log_metadata() would log a description of a metadata change.  It could be enabled/disabled, and configured to go to an lvm log file / syslog / systemd.  The description of the metadata change could probably be generated in many cases (perhaps not all).  A metadata log entry would generally include, date/time, pid, command, description of change.

IMHO more focus should be thrown into structured log support - so users of journalctl may sensible  use journaled info  - and the existing messages should be simply logged.

I'm not seeing added value in trying to select what important to  be logged for case  A and what is for case  B.

We have already existing tools - so let's use them.

Too late in rhel7 to be adding things like this.