Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 232711 - RFE reads should trigger a down conversion of a failed cmirror
Summary: RFE reads should trigger a down conversion of a failed cmirror
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: cmirror
Version: 4
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: LVM and device-mapper development team
QA Contact: Cluster QE
URL:
Whiteboard:
: 226815 233031 (view as bug list)
Depends On:
Blocks: 233031
TreeView+ depends on / blocked
 
Reported: 2007-03-16 19:23 UTC by Corey Marthaler
Modified: 2010-05-17 21:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-17 21:54:31 UTC


Attachments (Terms of Use)

Description Corey Marthaler 2007-03-16 19:23:55 UTC
Description of problem:
If a user has an application reading off of a failed cmirror (or does a read
before a write in a non-synced cmirror), their mirror wont get auto down
converted, instead the applications will just fail due to I/O errors.

Comment 1 Corey Marthaler 2007-04-12 17:49:48 UTC
*** Bug 233031 has been marked as a duplicate of this bug. ***

Comment 2 Corey Marthaler 2007-04-12 18:19:09 UTC
*** Bug 226815 has been marked as a duplicate of this bug. ***

Comment 3 Corey Marthaler 2009-01-16 14:57:32 UTC
Did this issue get resolved in the past year? It seems that a read does now trigger a down conversion to a failed mirror.

Comment 5 Jonathan Earl Brassow 2010-05-17 21:54:31 UTC
A read still should not be triggering a down convert... but we might want it to issue a restorative write (causing block relocation on the drive).

I'm closing this bug WONTFIX, but a new bug (under a newer rhel version) to add a restorative write attempt after a read failure might be something to consider as a feature request.


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