Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use Jira Cloud for all bug tracking management.

Bug 1340503

Summary: [rbd-mirror] possible inconsistent replay after client crash
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Jason Dillaman <jdillama>
Component: RBDAssignee: Jason Dillaman <jdillama>
Status: CLOSED ERRATA QA Contact: Tanay Ganguly <tganguly>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.0CC: amaredia, ceph-eng-bugs, ceph-qe-bugs, hnallurv, hyelloji, kdreyer, kurs
Target Milestone: rc   
Target Release: 2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-10.2.1-12.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-23 19:40:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jason Dillaman 2016-05-27 15:06:14 UTC 
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:
Comment 5 Tanay Ganguly 2016-07-29 10:10:18 UTC 
Marking it as Verified.
Comment 7 errata-xmlrpc 2016-08-23 19:40:01 UTC 
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