Actions
Bug #20168
closedIO work queue does not process failed lock request
Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
If the attempt to request the exclusive lock fails, the IO work queue will not attempt to recover. For example, in Jewel, if a -EPERM or -EBLACKLISTED error is encountered when attempting to acquire the lock, it will stop attempting to acquire the lock and will bubble the error back to the lock requester. However, AioImageRequestWQ does not register a callback to receive this notice.
Updated by Jason Dillaman almost 7 years ago
- Status changed from In Progress to Fix Under Review
Updated by Mykola Golub almost 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 7 years ago
- Copied to Backport #20514: kraken: IO work queue does not process failed lock request added
Updated by Nathan Cutler almost 7 years ago
- Copied to Backport #20515: jewel: IO work queue does not process failed lock request added
Updated by Jason Dillaman over 6 years ago
- Backport changed from kraken,jewel to jewel
Updated by Nathan Cutler over 6 years ago
- Copied to deleted (Backport #20514: kraken: IO work queue does not process failed lock request)
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions