Actions
Bug #58060
closedavoid EUCLEAN error after "rbd rm" is interrupted
% Done:
90%
Source:
Community (dev)
Tags:
backport_processed
Backport:
pacific,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
rbd
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
If rbd rm process is interrupted (for example, rbd client killed, or ceph_assert fault injection in rbd code), rbd state in trash stays in cls::rbd::TRASH_IMAGE_STATE_MOVING.
Then continue to rbd rm, throw error -EUCLEAN.
[root@node build]# ./bin/rbd rm test_pool/test_rbd
Removing image: 0% complete...failed.
rbd: delete error: 2022-11-22T11:30:41.361+0800 7f9bf12a74c0 -1 librbd::api::Trash: remove: error: image is pending moving to the trash.
(117) Structure needs cleaning
<pre><code class="go">
</code></pre>
Updated by Ilya Dryomov over 1 year ago
- Project changed from Ceph to rbd
- Category deleted (
librbd) - Status changed from New to Fix Under Review
- Assignee set to xinwei wei
- Target version deleted (
v16.2.11) - Backport set to pacific,quincy
Updated by xinwei wei over 1 year ago
- Status changed from Fix Under Review to Resolved
- % Done changed from 0 to 90
Updated by Ilya Dryomov over 1 year ago
- Status changed from Resolved to Fix Under Review
The ticket should be marked as Resolved only after the PR is merged and optionally backported.
Updated by Ilya Dryomov over 1 year ago
- Status changed from Fix Under Review to Pending Backport
Updated by Ilya Dryomov over 1 year ago
- Subject changed from EUCLEAN error in rbd rm to avoid EUCLEAN error after "rbd rm" is interrupted
Updated by Backport Bot over 1 year ago
- Copied to Backport #58358: quincy: avoid EUCLEAN error after "rbd rm" is interrupted added
Updated by Backport Bot over 1 year ago
- Copied to Backport #58359: pacific: avoid EUCLEAN error after "rbd rm" is interrupted added
Updated by Backport Bot about 1 year 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