LU-930 doc: document no_create mount option

Add the "-o no_create" mount option to the mount.lustre.8 man page.

Test-Parameters: trivial
Fixes: 1dbcd0bab8 ("LU-12998 mds: add no_create parameter to stop creates")
Signed-off-by: Andreas Dilger <adilger@whamcloud.com>
Change-Id: I143f46f71fdcff8ce320861e7ade0f7a9a1f96f7
Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/55503
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Maximilian Dilger <mdilger@whamcloud.com>
Reviewed-by: Arshad Hussain <arshad.hussain@aeoncomputing.com>
Reviewed-by: Nathaniel Clark <nclark@whamcloud.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>

diff --git a/lustre/doc/mount.lustre.8 b/lustre/doc/mount.lustre.8
index a95c05b..ea4bf5e 100644 (file)
--- a/lustre/doc/mount.lustre.8
+++ b/lustre/doc/mount.lustre.8
@@ -241,18 +241,21 @@ Enable POSIX Access Control List support for all clients.  See the
 .BR acl (5)
 manual page.
 .TP
-.BI no_precreate
-Do not allow objects to be created on the OST after mounting.  This
-allows a (potentially newly-formatted) OST to be started without
-clients starting to use it immediately.  To allow the MDS to create
-objects on the OST mount without this option, or run
-.BI "lctl set_param obdfilter." fsname -OST nnnn .no_precreate=0
-on the OSS to re-enable object creation.
+.BI no_create
+Do not allow objects to be created on an OST, or new directories
+on an MDT after mounting.  This allows a (potentially newly-formatted)
+MDT or OST to be started without clients starting to use it immediately.
+To allow the new target to be used for allocation, unmount and mount the
+target again without this option, or run
+.BI "lctl set_param mdt." fsname -OST nnnn .no_create=0
+or
+.BI "lctl set_param obdfilter." fsname -MDT nnnn .no_create=0
+on the server node.
 .BR NOTE :
-this does not start the OST read-only, it only disables the
-creation of new objects on the OST.  This means existing objects
-can be read, modified, or deleted, but if the OST is new then it
-will not have any such objects.
+this does not start the OST or MDT read-only, it only disables the
+creation of new objects there.  This means existing objects can be
+be read, modified, or deleted.  If the OST or MDT is new then
+it will not have any objects on it yet.
 .TP
 .BI nosvc
 Only start the MGC (and MGS, if co-located) for a target service,