Bug 200341
Summary: | possible bad interaction between pvmove and mysqld | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Mark Tinberg <mtinberg> | ||||||||||
Component: | lvm2 | Assignee: | Milan Broz <mbroz> | ||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | |||||||||||
Severity: | high | Docs Contact: | |||||||||||
Priority: | medium | ||||||||||||
Version: | 4.0 | CC: | agk, dwysocha, mbroz, pvrabec | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2008-01-14 14:19:40 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: | |||||||||||||
Attachments: |
|
Description
Mark Tinberg
2006-07-27 00:22:29 UTC
Created attachment 133120 [details]
sysreport from affected system
Created attachment 133121 [details]
vgdisplay verbose output
Created attachment 133122 [details]
mysql configuration for affected database
this config includes the force_recovery option added during db recovery
Created attachment 133123 [details]
mysql error log from affected database
this has sensitive and redundant data removed
Well, there is not too much information about physical volumes used during pvmove operation but I guess that this could be another demonstration of bug 179201 (not with kernel oops - but only with temporary structure corruption in-memory). From log I see there are many PV used in usagelog VG with mysqlold and myql LV, so there are multisegmented LVs - and exactly this triggers kernel bug during pvmove operation. Closing as duplicate of recently fixed bug. *** This bug has been marked as a duplicate of 179201 *** |