You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/cephfs/fs-volumes.rst
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -299,6 +299,24 @@ The earmarking mechanism ensures that subvolumes are correctly tagged and manage
299
299
helping to avoid conflicts and ensuring that each subvolume is associated
300
300
with the intended service or use case.
301
301
302
+
Valid Earmarks
303
+
~~~~~~~~~~~~~~~~~~~~
304
+
305
+
- **For NFS:**
306
+
- The valid earmark format is the top-level scope: ``'nfs'``.
307
+
308
+
- **For SMB:**
309
+
- The valid earmark formats are:
310
+
- The top-level scope: ``'smb'``.
311
+
- The top-level scope with an intra-module level scope: ``'smb.cluster.{cluster_id}'``, where ``cluster_id`` is a short string uniquely identifying the cluster.
312
+
- Example without intra-module scope: ``smb``
313
+
- Example with intra-module scope: ``smb.cluster.cluster_1``
314
+
315
+
.. note:: If you are changing an earmark from one scope to another (e.g., from nfs to smb or vice versa),
316
+
be aware that user permissions and ACLs associated with the previous scope might still apply. Ensure that
317
+
any necessary permissions are updated as needed to maintain proper access control.
0 commit comments