Bug 1261071
| Summary: | Reproducible LVM errors on a few systems when .cache file contains a device that is no longer on the system | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
| lvm2 sub component: | Devices, Filtering and Stacking (RHEL6) | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | agk, alex.wang, cmarthal, heinzm, jbrassow, mjuricek, msnitzer, prajnoha, prockai, tlavigne, zkabelac |
| Version: | 6.6 | Keywords: | ZStream |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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 | Environment: | |
| Last Closed: | 2015-09-22 14:03:18 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: | |||
| Bug Depends On: | 1260194 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2015-09-08 14:07:34 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-1823.html |