Description of problem: If a client issues a write-after-write and crashes shortly thereafter, there is a possibility the non-primary image will be inconsistent from the primary image where the non-primary image has applied the first write and the primary image did not apply it. Version-Release number of selected component (if applicable): How reproducible: 20% during the automated stress test case Steps to Reproduce: 1. Run rbd bench-write against an image 2. Force-kill rbd bench-write 3. Take a snapshot of the primary image 4. Compare the two snapshots Actual results: Primary and non-primary images differ Expected results: Primary and non-primary images should be identical Additional info:
Marking it as Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1755.html