Bug 1261071 - Reproducible LVM errors on a few systems when .cache file contains a device that is no longer on the system
Reproducible LVM errors on a few systems when .cache file contains a device t...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2 (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: LVM and device-mapper development team
: ZStream
Depends On: 1260194
  Show dependency treegraph
Reported: 2015-09-08 10:07 EDT by Jan Kurik
Modified: 2015-09-22 10:03 EDT (History)
11 users (show)

See Also:
Fixed In Version: lvm2-2.02.118-3.el6_7.3
Doc Type: Bug Fix
Doc Text:
When the /etc/lvm/cache/.cache file contained an entry that no longer existed, the code read an uninitialised structure which lead to unreliable behaviour. This bug exposed itself as messages with undefined major and minor numbers. For example: /dev/nonexistent_device: stat failed: No such file or directory Path /dev/nonexistent_device no longer valid for device(0,1) This has been fixed and nonexistent devices are handled correctly while reading the .cache file. The messages referencing undefined (major,minor) pair are not generated and unitialized structures are not used anymore.
Story Points: ---
Clone Of: 1260194
Last Closed: 2015-09-22 10:03:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Kurik 2015-09-08 10:07:34 EDT
This bug has been copied from bug #1260194 and has been proposed
to be backported to 6.7 z-stream (EUS).
Comment 6 errata-xmlrpc 2015-09-22 10:03:18 EDT
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.


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