Back to bug 749883

Who When What Removed Added
Milan Broz 2011-11-01 09:43:22 UTC Assignee lvm-team jbrassow
Jonathan Earl Brassow 2011-11-22 20:24:32 UTC Status NEW ASSIGNED
Jonathan Earl Brassow 2012-01-12 16:19:49 UTC Attachment #551694 Attachment is obsolete 0 1
Ludek Smid 2012-03-30 15:02:55 UTC Blocks 807971
Milan Broz 2012-05-29 12:30:15 UTC CC mbroz
Libor Miksik 2013-03-28 15:08:49 UTC Blocks 928849
Nenad Peric 2013-04-02 14:07:19 UTC CC nperic
Jonathan Earl Brassow 2013-04-10 21:02:04 UTC Status ASSIGNED POST
Doc Text A mirror logical volume can itself have a mirrored log device. When a device in an image of the mirror and its log failed at the same time, it was possible for I/O errors to appear on the mirror LV when they should have been handled. That is the kernel would not absorb the I/O errors from the failed device by relying on the remaining device. The cause was found to be that the mirror was not suspended for repair using the 'noflush' flag. This flag allows the kernel to requeue I/O requests that need to be retried. Because the kernel was not allowed to requeue the requests, it had no choice but to return the I/O as errored. This issue has been corrected and the mirror is now properly suspended with the 'noflush' flag.
Steven J. Levine 2013-04-17 18:40:33 UTC CC slevine
Nenad Peric 2013-05-16 08:18:30 UTC Fixed In Version lvm2-2.02.88-11.el5
Peter Rajnoha 2013-05-21 08:43:26 UTC Status POST MODIFIED
errata-xmlrpc 2013-05-21 08:48:03 UTC Status MODIFIED ON_QA
Nenad Peric 2013-06-05 11:42:44 UTC Status ON_QA VERIFIED
Marian Csontos 2013-07-25 12:20:23 UTC CC mcsontos
Summary mirrrored filesystem turned read only after leg and log leg device failure mirrored filesystem turned read only after leg and log leg device failure
errata-xmlrpc 2013-10-01 00:27:02 UTC Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2013-09-30 20:27:02 UTC
Emmanuel Segura 2013-12-17 18:56:45 UTC CC emi2fast

Back to bug 749883