Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1357058 - identifying block devices by persistent identifiers in journal entries [NEEDINFO]
Summary: identifying block devices by persistent identifiers in journal entries
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.0
Hardware: All
OS: Linux
Target Milestone: beta
: 7.0
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
Depends On:
Blocks: 947660
TreeView+ depends on / blocked
Reported: 2016-07-15 15:22 UTC by mulhern
Modified: 2019-01-02 17:08 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 947636
Last Closed:
Target Upstream Version:
amulhern: needinfo? (hhoyer)

Attachments (Terms of Use)

Comment 2 mulhern 2016-07-15 18:07:43 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.