Back to bug 732124

Who When What Removed Added
Zdenek Kabelac 2011-08-29 08:42:22 UTC Status NEW ASSIGNED
Assignee lvm-team jbrassow
Jonathan Earl Brassow 2011-10-17 16:40:12 UTC Flags needinfo?(cmarthal)
Corey Marthaler 2011-10-28 19:08:30 UTC Blocks 749883
Tom Coughlan 2011-11-10 13:01:42 UTC CC coughlan
Siddharth Nagar 2011-12-21 23:41:30 UTC Blocks 756082
Corey Marthaler 2012-03-21 19:46:41 UTC Flags needinfo?(cmarthal)
Milan Broz 2012-05-29 12:57:25 UTC CC mbroz
Corey Marthaler 2012-07-13 19:12:41 UTC Depends On 825323
Corey Marthaler 2012-07-13 19:16:24 UTC Summary mirrrored filesystem turned read only after leg and log leg device failure 2-leg mirrored filesystem turned read only after primary image and primary log leg device both fail
Jonathan Earl Brassow 2012-11-14 23:07:08 UTC Status ASSIGNED POST
Peter Rajnoha 2012-12-05 14:53:46 UTC Status POST MODIFIED
Fixed In Version lvm2-2.02.98-4.el6
errata-xmlrpc 2012-12-05 14:59:14 UTC Status MODIFIED ON_QA
releng-rhel 2012-12-11 19:30:14 UTC Blocks 886216
Nenad Peric 2012-12-19 18:05:33 UTC Status ON_QA VERIFIED
CC nperic
Jonathan Earl Brassow 2013-02-07 16:48:20 UTC 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 the mirror LV to leak I/O errors. That is the kernel would not absorb the I/O errors from the failed device by relying on the remaining device. This would then cause file systems built on the device to respond to the I/O errors (turn read-only in the case of the ext3/4 file systems).

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.
Alasdair Kergon 2013-02-07 17:26:32 UTC 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 the mirror LV to leak I/O errors. That is the kernel would not absorb the I/O errors from the failed device by relying on the remaining device. This would then cause file systems built on the device to respond to the I/O errors (turn read-only in the case of the ext3/4 file systems).

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. 		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. This would then cause file systems built on the device to respond to the I/O errors (turn read-only in the case of the ext3/4 file systems).

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.
errata-xmlrpc 2013-02-21 08:03:19 UTC Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2013-02-21 03:03:19 UTC

Back to bug 732124