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.
*** Bug 233031 has been marked as a duplicate of this bug. ***
*** Bug 226815 has been marked as a duplicate of this bug. ***
Did this issue get resolved in the past year? It seems that a read does now trigger a down conversion to a failed mirror.
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.