From c966ea99bc5d6fb6e4a3dc41becedb62efa4dd74 Mon Sep 17 00:00:00 2001 From: Ilya Dryomov Date: Wed, 18 Jan 2023 20:20:19 +0100 Subject: [PATCH] doc/rbd/rbd-exclusive-locks: don't mention "profile rbd" requirement twice It's (much better) described in the Blocklisting section. Signed-off-by: Ilya Dryomov --- doc/rbd/rbd-exclusive-locks.rst | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/doc/rbd/rbd-exclusive-locks.rst b/doc/rbd/rbd-exclusive-locks.rst index aad81dd01fa..5e4b4ac87f2 100644 --- a/doc/rbd/rbd-exclusive-locks.rst +++ b/doc/rbd/rbd-exclusive-locks.rst @@ -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 ` 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 ` using RBD. .. _fencing: https://en.wikipedia.org/wiki/Fencing_(computing)