Project

General

Profile

Actions
Copy link

Bug #49037

closed

[rbd-mirror] reported snapshot corruption

Added by Jason Dillaman about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Jason Dillaman
Target version:
-
% Done:

0%

Source:
Community (user)
Tags:
Backport:
octopus,pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
39155
Crash signature (v1):
Crash signature (v2):

Description

I can demote the rbd image on the primary, promote on the secondary and the image looks great.  I can map it, mount it, and it looks just like it should.

However, the rbd snapshots are still unusable on the secondary even when promoted.   I went as far as taking a 2nd snapshot on the rbd before demoting/promoting and that 2nd snapshot still won't work either.  Both snapshots look and work great on the primary.

If I request a resync from the secondary the rbd snapshots start working just like the primary, but only if I request a resync. 

I get the same exact results whether I am using a 15.2.8 or 16.1 client.

Related issues 2 (0 open — 2 closed)

Copied to rbd - Backport #49252: octopus: [rbd-mirror] reported snapshot corruptionResolvedJason DillamanActions
Copied to rbd - Backport #49253: pacific: [rbd-mirror] reported snapshot corruptionResolvedJason DillamanActions
Actions
Copy link
 #1

Updated by Jason Dillaman about 3 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 39155
Actions
Copy link
 #2

Updated by Mykola Golub about 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #3

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49252: octopus: [rbd-mirror] reported snapshot corruption added
Actions
Copy link
 #4

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49253: pacific: [rbd-mirror] reported snapshot corruption added
Actions
Copy link
 #5

Updated by Nathan Cutler about 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions
Copy link

Also available in: Atom PDF