Actions
Bug #50668
closed[pwl] cache can't be opened after a crash or power failure
% Done:
0%
Source:
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Opening the cache after a crash or power failure always fails with EINVAL because ImageCacheState::create_image_cache_state() misparses cache_type. This renders the image completely unusable -- it can't even be removed with "rbd rm":
$ rbd rm foo 2021-05-05T18:04:01.067-0400 7f9f8d9d9700 -1 librbd::exclusive_lock::PostAcquireRequest: 0x7f9f8801f000 handle_process_plugin_acquire_lock: failed to process plugins: (22) Invalid argument 2021-05-05T18:04:01.087-0400 7f9f8d9d9700 -1 librbd::image::PreRemoveRequest: 0x55b3ee054ba0 handle_exclusive_lock: cannot obtain exclusive lock - not removing Removing image: 0% complete...failed.
Since the bug is in ImageCacheState, both ssd and rwl modes are affected.
Updated by Ilya Dryomov about 3 years ago
- Related to Bug #50669: [pwl ssd] multiple crash / power failure recovery issues added
Updated by Ilya Dryomov about 3 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 41185
Updated by Ilya Dryomov about 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot about 3 years ago
- Copied to Backport #50718: pacific: [pwl] cache can't be opened after a crash or power failure added
Updated by Loïc Dachary almost 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