> > when you enable the "exclusive-lock" feature, only one RBD client is able
> > to modify the image while the lock is held.
>
> means
>
> rbd_lock_exclusive
>
> > However, that won't stop other RBD clients from *requesting* that
> > maintenance operations be performed on the image (e.g. snap
mage (e.g. snapshot, resize).
means
rbd_lock_shared
Correct?
- Shinobu
- Original Message -
From: "Jason Dillaman"
To: "Corin Langosch"
Cc: ceph-users@lists.ceph.com
Sent: Tuesday, September 22, 2015 9:37:56 PM
Subject: Re: [ceph-users] rbd and exclusive lock feat
sage -
> From: "Corin Langosch"
> To: ceph-users@lists.ceph.com
> Sent: Tuesday, September 22, 2015 8:11:38 AM
> Subject: [ceph-users] rbd and exclusive lock feature
>
> Hi guys,
>
> when creating an rbd with feature "exclusive-lock" (and object-map,
&
Hi guys,
when creating an rbd with feature "exclusive-lock" (and object-map, fast-diff,
..), do I have to pass any special
arguments to qemu to activate it?
How does this feature work with resize, snapshot creation, etc.? Form my work
on ceph-ruby I know you have to call
"rbd_open" and then pas
