Project

General

Profile

Actions

Bug #20168

closed

IO work queue does not process failed lock request

Added by Jason Dillaman almost 7 years ago. Updated over 6 years ago.

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.


Related issues 1 (0 open1 closed)

Copied to rbd - Backport #20515: jewel: IO work queue does not process failed lock requestResolvedJason DillamanActions
Actions

Also available in: Atom PDF