Project

General

Profile

Actions

Bug #14953

closed

can add 'rbd lock' to format 1 images

Added by Vasu Kulkarni about 8 years ago. Updated about 8 years ago.

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

0%

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

Description

this is on hammer 0.94.5, i think its deprecated now recently but still want to document it

1) 2 node ceph cluster, with 2 clients
2) imported animage from qcow2 to rbd:, by default the import is a format 1 image in rbd,
3) from 1 client, add a lock using 'rbd lock add', this is successful, this creates an impression the image is locked by this node and should be readonly on other clients
4) I was able to start the vm using qemu-kvm from the same rbd image on 2 nodes and was able to write from both vm's, this works but i believe since
the image is format 1 its not a valid case, and by default we should disable the 'rbd lock add' to the image if its format 1?

Actions #1

Updated by Loïc Dachary about 8 years ago

  • Project changed from Ceph to rbd
  • Category deleted (librbd)
Actions #2

Updated by Jason Dillaman about 8 years ago

@Vasu Kulkarni, the "rbd lock"-related commands are to be considered as advisory locks. There is no enforcement within librbd / krbd for these locks. See #14700 for an example use case.

Actions #3

Updated by Jason Dillaman about 8 years ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF