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.
Bug 656453 - libblkid incorrectly revalidated cache entries
Summary: libblkid incorrectly revalidated cache entries
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: util-linux-ng
Version: 6.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
: 656419 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-23 19:08 UTC by Karel Zak
Modified: 2011-05-19 14:06 UTC (History)
4 users (show)

Fixed In Version: util-linux-ng-2.17.2-9.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 14:06:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0699 0 normal SHIPPED_LIVE util-linux-ng bug fix and enhancement update 2011-05-18 18:10:13 UTC

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


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