Bug 146696
Summary: | possible metadata coruption trying to active VG | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Corey Marthaler <cmarthal> |
Component: | lvm2-cluster | Assignee: | Alasdair Kergon <agk> |
Status: | CLOSED WORKSFORME | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | agk, kanderso |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-01 16:24:42 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
Corey Marthaler
2005-01-31 20:48:55 UTC
Adding to release blocker list I can't reproduce this, the LVM errors at the top of the bug report look quite nasty though - Alasdair ?? Not enough info, but the usual cause of those memory errors is corrupt lvm1 metadata. Need -vvvv (or lvm2 logfile) output from the command giving the memory error, or a dump of the data at the start of the device which it read causing it. Removing from blocker list. If it is recreatable, then will get back on the list at that time. Added more discriptive summary. This issue was only seen that one time. A year has passed without seeing this again, so closing it for now. |