+++ This bug was initially created as a clone of Bug #379961 +++ +++ This bug was initially created as a clone of Bug #379951 +++ Description of problem: dmraid needs to add the 'handle_errors' argument to mapping tables created for mirror mappings in order to take advantage of the resynchronization error handling. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1.Check RAID1 mapping table created via "dmraid -tay" Actual results: Table doesn't contain the handle_errors argument. Expected results: Table does contain it. Additional info:
Created attachment 257681 [details] Patch to add handle_error argument
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
This change completely breaks RAID 1 in 5.2 -- the kernel does not support handle_errors.
I can't get information about this this kernel issue in time so I have to go with reverting the patch. Setting the request flags to reflect that. Ian
This has been addressed in 5.3, closing. The table syntax differs between upstream and RHEL5 kernel because of the differences in error handling processing: upstream kernel takes handle_errors as a mirror argument *whereas* RHEL5 kernel expects block_on_error as a dirty log argument.