Project

General

Profile

Bug #20168

IO work queue does not process failed lock request

Added by Jason Dillaman almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Target version:
-
Start date:
06/02/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

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

Copied to rbd - Backport #20515: jewel: IO work queue does not process failed lock request Resolved

History

#1 Updated by Jason Dillaman almost 2 years ago

  • Description updated (diff)

#2 Updated by Jason Dillaman over 1 year ago

  • Status changed from In Progress to Need Review

#3 Updated by Mykola Golub over 1 year ago

  • Status changed from Need Review to Pending Backport

#4 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #20514: kraken: IO work queue does not process failed lock request added

#5 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #20515: jewel: IO work queue does not process failed lock request added

#6 Updated by Jason Dillaman over 1 year ago

  • Backport changed from kraken,jewel to jewel

#7 Updated by Nathan Cutler over 1 year ago

  • Copied to deleted (Backport #20514: kraken: IO work queue does not process failed lock request)

#8 Updated by Nathan Cutler over 1 year ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF