RepoMirrors/ceph
1
0
Fork 0
mirror of https://github.com/ceph/ceph synced 2024-12-29 15:03:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc/rbd/rbd-exclusive-locks: don't mention "profile rbd" requirement twice

Browse Source 
It's (much better) described in the Blocklisting section.

Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
This commit is contained in:
Ilya Dryomov 2023-01-18 20:20:19 +01:00
parent 728e8ac088
commit c966ea99bc
1 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/rbd/rbd-exclusive-locks.rst
View File

@ -21,10 +21,6 @@ can be overridden via the ``rbd_default_features`` configuration option or the
exclusive locking. Disabling the ``exclusive-lock`` feature will negatively
affect the performance of some operations.
In order to ensure proper exclusive locking operations, any client using an RBD
image whose ``exclusive-lock`` feature is enabled must have a CephX identity
whose capabilities include ``profile rbd``.
Exclusive locking is mostly transparent to the user.
#. Whenever any ``librbd`` client process or kernel RBD client
@ -78,9 +74,10 @@ Ceph Monitor.
Blocklisting is thus a form of storage-level resource `fencing`_.
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 be set generally on all Ceph
:ref:`client identities <user-management>` using RBD.
.. note::
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 be set generally on all Ceph
:ref:`client identities <user-management>` using RBD.
.. _fencing: https://en.wikipedia.org/wiki/Fencing_(computing)