It would be desirable to make it possible for a sysadmin to retrospectively examine the history of a specified physical device across boots as it appears in the journal. Currently, no such facility is available. The enhancement in journalctl supplied in response to BZ#947636 does not supply such a facility.
It would be necessary to base such a search on a record which contained a unique identifier for that specific device. Due to the reasons explained in BZ#947636, the _UDEV_DEVLINK field is not much use.
The existing, RHEL-specific solution to this problem is documented in BZ#1032711, but is expensive and not automatic, i.e., a reader of the log must still manually match up the device link information with the particular device node.
In general, and for many uses, it would be preferred if log entries which now only refer to a device node also contained sufficient information so that the physical device referred to could be automatically inferred and shown to the user.
The solution in BZ#1032711 has always been understood to be a temporary one. This BZ is the BZ for an as yet not determined permanent solution.
Comment 6RHEL Program Management
2020-12-15 07:42:58 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.