From bbfa96f408cdf3ccd772fcb16e7f7a719bd2ad2a Mon Sep 17 00:00:00 2001 From: Guillermo Ramos Date: Thu, 19 Dec 2024 21:15:55 +0100 Subject: [PATCH] Wording Signed-off-by: Guillermo Ramos --- source/open_cluster_deployment/storage_setup/nas_ds.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/open_cluster_deployment/storage_setup/nas_ds.rst b/source/open_cluster_deployment/storage_setup/nas_ds.rst index 1a2972524..f7e76b0c3 100644 --- a/source/open_cluster_deployment/storage_setup/nas_ds.rst +++ b/source/open_cluster_deployment/storage_setup/nas_ds.rst @@ -35,7 +35,7 @@ Automatic Setup Automatic NFS setup is is available since OpenNebula version 6.10.3 as an opt-in feature. It's controlled via the ``NFS_AUTO_*`` family of datastore attributes documented :ref:`below `. If enabled, OpenNebula will lazily mount the NFS share on demand (either on hosts or the frontend) before an operation requires it. Also, for the transfer operations where it makes sense (for example, when deploying a VM which uses a NFS-backed system image) the mounting information is persisted to the host's ``/etc/fstab``. -Also, for the moment, umounting/fstab cleanup is performed in a lazy way, similar to mounting. So, rutine operations will check whether the current machine has mounted a datastore which either has ``NFS_AUTO_ENABLE`` set to ``no``, or does not exist anymore, and clean it up. +Also, for the moment, unmounting/fstab cleanup is performed in a lazy way, similar to mounting. So, routine operations will check whether the current machine has mounted a datastore which either has ``NFS_AUTO_ENABLE`` set to ``no``, or does not exist anymore, and clean it up. .. warning:: This also means that the user must be careful not to delete the filesystem from the NFS server until being sure that there are no hosts still having it mounted.