From: Changcheng Liu Date: Thu, 23 Jul 2020 03:09:46 +0000 (+0800) Subject: doc: specify RBD_LOCK_MODE_EXCLUSIVE for exclusive-lock X-Git-Tag: v16.1.0~1607^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=refs%2Fpull%2F36253%2Fhead;p=ceph.git doc: specify RBD_LOCK_MODE_EXCLUSIVE for exclusive-lock The exclusive-lock could be transited transparently between clients after finishing write operation. To disable "transparent" transition, it needs to acquire the lock with RBD_LOCK_MODE_EXCLUSIVE. Signed-off-by: Changcheng Liu --- diff --git a/doc/rbd/rbd-exclusive-locks.rst b/doc/rbd/rbd-exclusive-locks.rst index f07651d32eda..cedc0d11191a 100644 --- a/doc/rbd/rbd-exclusive-locks.rst +++ b/doc/rbd/rbd-exclusive-locks.rst @@ -36,7 +36,9 @@ Exclusive locking is mostly transparent to the user. Note that it is perfectly possible for two or more concurrently running processes to merely open the image, and also to read from it. The client acquires the exclusive lock only when attempting to -write to the image. +write to the image. To disable transparent lock transitions between +multiple clients, it needs to acquire the lock specifically with +``RBD_LOCK_MODE_EXCLUSIVE``. Blacklisting