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 1232054 - pvdisplay -C -o pv_uuid <device> modifies .cache, preventing system from booting
Summary: pvdisplay -C -o pv_uuid <device> modifies .cache, preventing system from booting
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.6
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Peter Rajnoha
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-16 00:25 UTC by Marcus West
Modified: 2019-08-15 04:43 UTC (History)
10 users (show)

Fixed In Version: lvm2-2.02.111-2.el6_6.5
Doc Type: Bug Fix
Doc Text:
Cause: Regression in calling LVM reporting commands while reporting Physical Volume Label Fields only (see also pvs -o help for the exact list of such fields) and while directly enumerating devices to report. Consequence: Incorrect persistent cache file (/etc/lvm/cache/.cache) was generated which contained entries only for devices which were enumerated on command line, ignoring all the other devices. Subsequent LVM commands used this incorrect persistent cache file causing some devices to be ignored by LVM. Fix: Functionality has been reinstated to original behaviour - the persistent cache file is not updated in case we're just processing devices enumerated on command line to be processed by reporting commands since that would generate persistent cache file with entries only for devices enumerated on command line and ignoring all the others. Result: Persistent cache file is correctly handled even if we use reporting commands where devices to process are enumerated, not causing subsequent commands to fail to see other devices.
Clone Of:
Environment:
Last Closed: 2015-08-24 07:49:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1655 0 normal SHIPPED_LIVE lvm2 bug fix update 2015-09-11 17:01:45 UTC

Description Marcus West 2015-06-16 00:25:07 UTC 
## Description of problem:

pvdisplay -C -o pv_uuid <device> modifies .cache, preventing system from booting

## Version-Release number of selected component (if applicable):

First noticed change of behaviour in lvm2-2.02.100-8.el6.x86_64

## How reproducible:

Always

## Steps to Reproduce:

1. Install RHEL6.4, update to lvm2-2.02.100-8.el6.x86_64
2. ll /etc/lvm/cache/.cache              # note file size
3. pvdisplay -C -o pv_uuid <device>
4. ll /etc/lvm/cache/.cache              # note file size is the same

5. yum update lvm2-2.02.111-2.el6.x86_64
6. pvdisplay -C -o pv_uuid <device>
7. ll /etc/lvm/cache/.cache              # note file size has changed

8. running 'vgscan' returns the cache to normal
9. pvdisplay <device>
7. ll /etc/lvm/cache/.cache              # without -C, .cache seems to not be changed

## Actual results:

.cache is modified

## Expected results:

.cache to stay the same (is this the expected behaviour?  If not, why does 'pvdisplay /vdb' not change .cache in the same way?)


## Additional info:

For the customer, this change prevented the system from booting (could not see root volume group) - however, i could not reproduce the reboot fail.

Customer can get around this by running 'vgscan' after the offending 'pvdisplay' command (so a back .cache is not left there), or removing it (.cache) altoghether
Comment 2 Alasdair Kergon 2015-07-10 13:19:17 UTC 
Upstream fix in 2.02.117:
http://www.redhat.com/archives/lvm-devel/2015-February/msg00242.html
Comment 4 Alasdair Kergon 2015-07-10 13:45:16 UTC 
Fix is already present in RHEL 6.7.
Comment 5 Peter Rajnoha 2015-07-10 14:00:00 UTC 
Scratch build to try: https://brewweb.devel.redhat.com/taskinfo?taskID=9500372.
We reproduced and this build fixes the issue as reported here.
Comment 6 Alasdair Kergon 2015-07-10 14:06:12 UTC 
Test is as stated:

rm .cache
pvdisplay -C -o pv_uuid /dev/whatever
Check that .cache file did NOT get created by the pvdisplay
Comment 11 errata-xmlrpc 2015-08-24 07:49:51 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-1655.html
Note You need to log in before you can comment on or make changes to this bug.