Comment 1 for bug 1971546

maybe it's because we don't (can't?) send the md5 of the reconstructing fragment along with the PUT to the restored node? Like *that* (invalid) frag would think it's correct.

It could be the reconstructor is missing an oppertunity to check the etag of the fragments it's recieving (by the end it could have noticed same as the object-server quarantine) - but since there's no two phase ec commit in ssync I don't see how it could notify the reciever.

A future roadmap could include rebuilds moving off the ssync protocol.