Bug 461498
Summary: | RHEL5 cmirror tracker: log failure on 3-way mirror leads to I/O errors | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Corey Marthaler <cmarthal> | ||||
Component: | cmirror | Assignee: | Jonathan Earl Brassow <jbrassow> | ||||
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.3 | CC: | agk, bstevens, ccaulfie, dwysocha, edamato, heinzm, mbroz, syeghiay | ||||
Target Milestone: | beta | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-01-20 21:26:11 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
Corey Marthaler
2008-09-08 16:01:21 UTC
Created attachment 316097 [details]
log from taft-01
Modified by the following check-in: commit 85d1423ec47e48ab844088ebaf4157327b928ae9 Author: Jonathan Brassow <jbrassow> Date: Fri Sep 19 16:19:02 2008 -0500 dm-log-clustered/clogd: Fix off-by-one error and compilation errors Needed to tweek included header files to make dm-log-clustered compile again. Found an off-by-one error that was causing mirror corruption in the case where the primary mirror device was killed in a mirror. This off-by-one error will manifest itself anytime you are doing I/O while the mirror is sync'ing. This could be during the initial sync or a resync after a failure. Another reason to suspect that the above is the appropriate fix, is the timing of the last log I/O error and the GFS corruption message that followed - they happen in the same second. If the log fails, no write I/O will be allowed until a new 'core log' mirror is in place. So, the write I/O that caused the corruption must have happened previously... leading me to believe the above is correct. Another possibility would be that the last error message is from one mirror, while the GFS error is from another entirely. In this event, there could be a small chance of the error being somewhere else. Have not seen this issue since the fix was checked in. Marking verified, will reopen if seen again. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-0158.html |