Red Hat Bugzilla – Bug 1007734
blkid shows devices as /dev/block/$MAJOR:$MINOR
Last modified: 2016-11-03 17:24:21 EDT
Description of problem:
blkid shows devices as /dev/block/$MAJOR:$MINOR.
Version-Release number of selected component (if applicable):
RHEL-7.0-20130912.0 x86_64 Server
Steps to Reproduce:
1. On installed system (any partitioning) run 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"
This seems to happen only after first boot after installation.
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.