Bug 1251250

Summary:	blkid outputs nothing for some partitions (e.g. sun label)
Product:	Red Hat Enterprise Linux 7	Reporter:	Ben Marzinski <bmarzins>
Component:	util-linux	Assignee:	Karel Zak <kzak>
Status:	CLOSED ERRATA	QA Contact:	Tomas Dolezal <todoleza>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1	CC:	agk, bmarzins, heinzm, mmatsuya, msnitzer, pbokoc, prajnoha, storage-qe, todoleza
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	util-linux-2.23.2-25.el7	Doc Type:	Bug Fix
Doc Text:	* The libblkid library was incorrectly evaluating internal return codes from probing functions, which caused blkid to ignore some partition types such as Sun disk label. With this update, libblkid evaluates return codes correctly and blkid provides information about all valid partitions.	Story Points:	---
Clone Of:	1241774	Environment:
Last Closed:	2015-11-19 12:20:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1241774, 1299589
Bug Blocks:

Comment 1 Ben Marzinski 2015-08-06 19:47:29 UTC

This clone is for dealing with

# blkid -po udev /dev/sdX

not returning anything for some partitions.

Comment 3 Karel Zak 2015-08-11 12:17:18 UTC

I'm able to reproduce the problem on scsi_debug with sun label.

Device      Start     End Sectors   Size Id Type         Flags
/dev/sdc1       0  920753  920754 449.6M 83 Linux native      
/dev/sdc2  920754 1023059  102306    50M 82 Linux swap      u 
/dev/sdc3       0 1023059 1023060 499.6M  5 Whole disk        

fedora 22:

# blkid -po udev /dev/sdc2
ID_PART_ENTRY_SCHEME=sun
ID_PART_ENTRY_TYPE=0x82
ID_PART_ENTRY_FLAGS=0x1
ID_PART_ENTRY_NUMBER=2
ID_PART_ENTRY_OFFSET=920754
ID_PART_ENTRY_SIZE=102306
ID_PART_ENTRY_DISK=8:32

rhel7:
# blkid -po udev /dev/sdc2
<nothing>

Comment 9 errata-xmlrpc 2015-11-19 12:20:12 UTC

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/RHBA-2015-2093.html

Comment 10 Ben Marzinski 2016-01-18 17:14:59 UTC

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