Project

General

Profile

Bug #11113

RBD snapshot, created while flattening image, is unremovable

Added by Benjamin Gilbert over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Target version:
-
Start date:
03/16/2015
Due date:
% Done:

0%

Source:
Community (user)
Tags:
Backport:
hammer,firefly
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

Description

The following actions will create an unremovable RBD snapshot:

  1. Clone an image from an origin snapshot
  2. Flatten the clone
  3. While flattening, snapshot the clone
  4. Delete the origin snapshot and image

Result:

  • The new snapshot appears in rbd snap ls, but rbd snap rm fails with rbd: failed to remove snapshot: (2) No such file or directory.
  • rbd ls -l on the pool will segfault.

This bug was previously reported here and is still present in 0.87.1. The attached script demonstrates the problem.

create-broken-rbd-snapshot.sh View - Reproducer (668 Bytes) Benjamin Gilbert, 03/16/2015 03:43 AM

Associated revisions

Revision cf809494 (diff)
Added by Jason Dillaman over 3 years ago

librbd: snap_remove should ignore -ENOENT errors

If the attempt to deregister the snapshot from the parent
image fails with -ENOENT, ignore the error as it is safe
to assume that the child is not associated with the parent.

Fixes: #11113
Signed-off-by: Jason Dillaman <>

Revision b9da6f10 (diff)
Added by Jason Dillaman over 3 years ago

librbd: snap_remove should ignore -ENOENT errors

If the attempt to deregister the snapshot from the parent
image fails with -ENOENT, ignore the error as it is safe
to assume that the child is not associated with the parent.

Fixes: #11113
Signed-off-by: Jason Dillaman <>
(cherry picked from commit cf8094942ccdba831e03e5a79451cfa5d78a135f)

Revision 57d2781d (diff)
Added by Jason Dillaman over 3 years ago

librbd: snap_remove should ignore -ENOENT errors

If the attempt to deregister the snapshot from the parent
image fails with -ENOENT, ignore the error as it is safe
to assume that the child is not associated with the parent.

Fixes: #11113
Signed-off-by: Jason Dillaman <>
(cherry picked from commit cf8094942ccdba831e03e5a79451cfa5d78a135f)

History

#1 Updated by Jason Dillaman over 3 years ago

  • Status changed from New to In Progress

#2 Updated by Jason Dillaman over 3 years ago

  • Status changed from In Progress to Need Review
  • Assignee set to Jason Dillaman
  • Backport set to hammer,firefly,dumpling

#3 Updated by Josh Durgin over 3 years ago

  • Status changed from Need Review to Pending Backport
  • Backport changed from hammer,firefly,dumpling to hammer,firefly

#5 Updated by Loic Dachary over 3 years ago

  • Status changed from Pending Backport to Resolved
  • Regression set to No

Also available in: Atom PDF