Bug 1340503 - [rbd-mirror] possible inconsistent replay after client crash
Summary: [rbd-mirror] possible inconsistent replay after client crash
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RBD
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 2.0
Assignee: Jason Dillaman
QA Contact: Tanay Ganguly
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-27 15:06 UTC by Jason Dillaman
Modified: 2022-02-21 18:17 UTC (History)
7 users (show)

Fixed In Version: RHEL: ceph-10.2.1-12.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-23 19:40:01 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 15955 0 None None None 2016-05-27 15:06:13 UTC
Red Hat Product Errata RHBA-2016:1755 0 normal SHIPPED_LIVE Red Hat Ceph Storage 2.0 bug fix and enhancement update 2016-08-23 23:23:52 UTC

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


Note You need to log in before you can comment on or make changes to this bug.