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:
blkid shows devices as /dev/block/$MAJOR:$MINOR.

Version-Release number of selected component (if applicable):
util-linux-2.23.2-4.el7.x86_64
RHEL-7.0-20130912.0 x86_64 Server

How reproducible:
randomly

Steps to Reproduce:
1. On installed system (any partitioning) run blkid

Actual results:
# blkid 
/dev/block/252:2: UUID="wP1zvZ-OBEI-9zpZ-ULoG-esqa-2ug2-4fHmzJ" TYPE="LVM2_member" 
/dev/block/253:1: UUID="7edffcca-af7d-47c8-8cd4-72f2de2f8697" TYPE="xfs" 
/dev/block/252:1: UUID="65242ccc-4c22-41f1-a3d2-5382ac6fe192" TYPE="xfs" 
/dev/block/253:0: UUID="37ed801d-fae8-4632-b2d9-2d83a9d2fcaa" TYPE="swap" 
/dev/sr0: UUID="2013-09-12-05-22-36-00" LABEL="RHEL Server 7.0" TYPE="iso9660" PTTYPE="dos"

Expected results:
This seems to happen only after first boot after installation.

Additional info:

I'm going to clove this report, it seems non-reproducible in normal environment.

*** Bug 1287734 has been marked as a duplicate of this bug. ***

/run is mounted on tmpfs, how is this cache being copied between the installer environment and the first boot?

Wouldn't it be safer if blkid started with a clean cache on each boot? I'm sure that anaconda isn't the only thing using blkid in the initrd (eg. dracut).

Not sure what is asking libblkid for devices by the symlinks, but I have improved libblkid to be more robust and canonicalize the paths to keep the cache without the symlinks.

Upstream commit 924c93d9df118338fd54cd73b4a45ccddc4ac103.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2605.html