will still be used for existing files located there or if there are
not enough non-degraded OSTs to make up a widely-striped file.
.TP
-.B N: no-precreate
-The target is configured to deny object precreation by the
-.BI "'lctl set_param obdfilter." TARGET ".no_precreate=1'"
+.B N: no-create
+The target is configured to deny new OST object creation by the
+.BI "'lctl set_param obdfilter." FSNAME -OST XXXX ".no_create=1'"
+option, or new subdirectory creation by the
+.BI "'lctl set_param obdfilter." FSNAME -MDT XXXX ".no_create=1'"
parameter or
-.B '-o no_precreate'
-mount option. This may be done to add an OST to the filesystem without
-allowing objects to be allocated on it yet, or for other reasons.
+.B '-o no_create'
+mount option. This can be used to add an OST or MDT to the filesystem
+without allowing objects to be allocated on it yet, or for other reasons.
.TP
.B R: read-only
The target filesystem is marked read-only due to filesystem
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
+.BI "'lctl set_param obdfilter." FSNAME -OST XXXX ".no_create=0'"
or
-.BI "lctl set_param obdfilter." fsname -MDT nnnn .no_create=0
-on the server node.
+.BI "'lctl set_param mdt." FSNAME -MDT XXXX ".no_create=0'"
+on the appropriate server node.
.BR NOTE :
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