Description of problem: I had a cmirror which was 14% done being copied, I then rebooted a node in the cluster which didn't have any I/O going to that mirror. The mirror copy then appeared to restart again at 0% and slowly and eventually made it's way to 100% copied. I thought that the whole point of the log volume was to not have to re-copy the whole mirror every time a failure happened. Version-Release number of selected component (if applicable): [root@taft-04 sbin]# rpm -q cmirror-kernel-smp cmirror-kernel-smp-2.6.9-4.2
This was a problem were I was making the complete_resync_work function handle what should have been in the clear_region function for recovery scenarios. The result was that although the clear_region was happening, that bitmap was not properly being written. Fix will be in next rev after cmirror-kernel*-2.6.9-4.2.
This appears to be fixed.
Assuming this VERIFIED fix got released. Closing. Reopen if it's not yet resolved.