Project

General

Profile

Actions

Bug #18888

closed

rbd_clone_copy_on_read ineffective with exclusive-lock

Added by Venky Shankar about 7 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
kraken,jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

With layering+exclusive-lock feature, rbd_clone_copy_on_read does not trigger object copyups from parent image. This is due to the fact that exclusive-lock is not taken for read operations.

Note that this is not the case when journaling is enabled.


Related issues 2 (0 open2 closed)

Copied to rbd - Backport #19173: kraken: rbd: rbd_clone_copy_on_read ineffective with exclusive-lockResolvedNathan CutlerActions
Copied to rbd - Backport #19174: jewel: rbd_clone_copy_on_read ineffective with exclusive-lockResolvedNathan CutlerActions
Actions #1

Updated by Venky Shankar about 7 years ago

  • Status changed from New to In Progress
Actions #2

Updated by Venky Shankar about 7 years ago

  • Status changed from In Progress to Fix Under Review
Actions #3

Updated by Venky Shankar about 7 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #4

Updated by Nathan Cutler about 7 years ago

  • Copied to Backport #19173: kraken: rbd: rbd_clone_copy_on_read ineffective with exclusive-lock added
Actions #5

Updated by Nathan Cutler about 7 years ago

  • Copied to Backport #19174: jewel: rbd_clone_copy_on_read ineffective with exclusive-lock added
Actions #6

Updated by Nathan Cutler over 6 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF