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
Signed-off-by: Avan Thakkar <[email protected]>
Fixes some doc lint and also fixed qa tests for having both 3 & 4 protocols
by default in expot config.
* RBD: The output of `rbd snap ls --all` command now includes the original
262
262
type for trashed snapshots.
263
263
264
-
* NFS: The export create/apply of CephFS based exports will now have a additional parameter `cmount_path` under FSAL block,
264
+
* NFS: The export create/apply of CephFS based exports will now have a additional parameter `cmount_path` under the FSAL block,
265
265
which specifies the path within the CephFS to mount this export on. If this and the other
266
266
`EXPORT { FSAL {} }` options are the same between multiple exports, those exports will share a single CephFS client. If not specified, the default is `/`.
Copy file name to clipboardExpand all lines: doc/mgr/nfs.rst
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -318,10 +318,11 @@ values may be separated by a comma (example: ``--sectype krb5p,krb5i``). The
318
318
server will negotatiate a supported security type with the client preferring
319
319
the supplied methods left-to-right.
320
320
321
-
``<cmount_path>`` specifies the path within the ceph filesystem to mount this export on. It is
321
+
``<cmount_path>`` specifies the path within the CephFS to mount this export on. It is
322
322
allowed to be any complete path hierarchy between ``/`` and the ``EXPORT {path}``. (i.e. if ``EXPORT { Path }`` parameter is ``/foo/bar`` then cmount_path could be ``/``, ``/foo`` or ``/foo/bar``).
323
-
!! If this and the other ``EXPORT { FSAL {} }`` options are the same between multiple exports, those exports will share a single cephfs client.
324
-
If not specified, the default is ``/``.
323
+
324
+
.. note:: If this and the other ``EXPORT { FSAL {} }`` options are the same between multiple exports, those exports will share a single CephFS client.
325
+
If not specified, the default is ``/``.
325
326
326
327
.. note:: Specifying values for sectype that require Kerberos will only function on servers
327
328
that are configured to support Kerberos. Setting up NFS-Ganesha to support Kerberos
@@ -498,7 +499,8 @@ provided JSON should fully describe the new state of the export (just
498
499
as when creating a new export), with the exception of the
499
500
authentication credentials, which will be carried over from the
500
501
previous state of the export where possible.
501
-
The ``user_id`` in the ``fsal`` block should not be modified or mentioned in the JSON file as it is auto-generated for CephFS exports.
502
+
503
+
!! NOTE: The ``user_id`` in the ``fsal`` block should not be modified or mentioned in the JSON file as it is auto-generated for CephFS exports.
502
504
It's auto-generated in the format ``nfs.<cluster_id>.<fs_name>.<hash_id>``.
0 commit comments