X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=ceph%2Fdoc%2Frbd%2Frbd-exclusive-locks.rst;fp=ceph%2Fdoc%2Frbd%2Frbd-exclusive-locks.rst;h=f02d6d48f4492afaccd04f0142d5cfa85b5b3630;hb=f67539c23b11f3b8a2ecaeeddf7a403ae1c442a8;hp=f07651d32eda9cf1fb8dc8dd5df0f31323443216;hpb=64a4c04e6850c6d9086e4c37f57c4eada541b05e;p=ceph.git diff --git a/ceph/doc/rbd/rbd-exclusive-locks.rst b/ceph/doc/rbd/rbd-exclusive-locks.rst index f07651d32..f02d6d48f 100644 --- a/ceph/doc/rbd/rbd-exclusive-locks.rst +++ b/ceph/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 @@ -60,8 +62,8 @@ accessing RBD data in an uncoordinated and destructive manner. Thus, in the event that a lock cannot be acquired in the standard graceful manner, the overtaking process not only breaks the lock, but -also blacklists the previous lock holder. This is negotiated between -the new client process and the Ceph Mon: upon receiving the blacklist +also blocklists the previous lock holder. This is negotiated between +the new client process and the Ceph Mon: upon receiving the blocklist request, * the Mon instructs the relevant OSDs to no longer serve requests from @@ -71,10 +73,10 @@ request, * once the new client has acquired the lock, it can commence writing to the image. -Blacklisting is thus a form of storage-level resource `fencing`_. +Blocklisting is thus a form of storage-level resource `fencing`_. -In order for blacklisting to work, the client must have the ``osd -blacklist`` capability. This capability is included in the ``profile +In order for blocklisting to work, the client must have the ``osd +blocklist`` capability. This capability is included in the ``profile rbd`` capability profile, which should generally be set on all Ceph :ref:`client identities ` using RBD.