Bug 656453

Summary: libblkid incorrectly revalidated cache entries
Product: Red Hat Enterprise Linux 6 Reporter: Karel Zak <kzak>
Component: util-linux-ngAssignee: Karel Zak <kzak>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: azelinka, jmarko, lmr, rvokal
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: util-linux-ng-2.17.2-9.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 14:06:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Karel Zak 2010-11-23 19:08:55 UTC
Description of problem:

#!/bin/bash
losetup -d /dev/loop7 &> /dev/null

rm /etc/blkid/blkid.tab
blkid &> /dev/null

dd if=/dev/zero of=tst bs=1M count=64
losetup /dev/loop7 tst

echo "--- Luks ---"
echo "password" | cryptsetup luksFormat /dev/loop7
blkid /dev/loop7

echo "--- PV ---"
pvcreate -ff /dev/loop7
blkid /dev/loop7

echo "--- done ---"
losetup -d /dev/loop7


... this script has to return info about LUKs as well as about LVM.

Old version:

  --- Luks ---
  /dev/loop7: UUID="53b65aab-0b55-480b-ae90-8d773d4686a2" TYPE="crypto_LUKS" 
  --- PV ---
    Physical volume "/dev/loop7" successfully created
  --- done ---

New version:

   --- Luks ---
   /dev/loop7: UUID="53b65aab-0b55-480b-ae90-8d773d4686a2" TYPE="crypto_LUKS" 
   --- PV ---
     Physical volume "/dev/loop7" successfully created
   /dev/loop7: UUID="mmjW2c-NsCh-bE6y-0I7G-oxt1-Yre4-SXVe96" TYPE="LVM2_member"
   --- done ---

The problem is that libblkid incorrectly revalidated cache entries.

Fixed by upstream commit e8fc977aba09ddbd89b25276fd777c3f0eef9299.

Comment 2 Karel Zak 2010-11-24 14:54:19 UTC
*** Bug 656419 has been marked as a duplicate of this bug. ***

Comment 6 errata-xmlrpc 2011-05-19 14:06:38 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0699.html