From: Sebastien Buisson Date: Tue, 22 Jan 2019 13:20:27 +0000 (+0100) Subject: LUDOC-430 nodemap: doc for 'default' nodemap X-Git-Tag: 2.13.0~27 X-Git-Url: https://git.whamcloud.com/?a=commitdiff_plain;h=b962f19e32154b51d5b636ebadac2f1fe2f0db6b;p=doc%2Fmanual.git LUDOC-430 nodemap: doc for 'default' nodemap This patch adds documentation about the 'default' nodemap. This doc is added under the Mapping UIDs and GIDs with Nodemap chapter. Signed-off-by: Sebastien Buisson Change-Id: I9ae21cc4ae321f804f950a9a05e48f1df91c9dc0 Reviewed-on: https://review.whamcloud.com/34089 Tested-by: Jenkins Reviewed-by: James Nunez Reviewed-by: Joseph Gmitter --- diff --git a/LustreNodemap.xml b/LustreNodemap.xml index 0efd877..313ab95 100644 --- a/LustreNodemap.xml +++ b/LustreNodemap.xml @@ -23,6 +23,10 @@ + + + + @@ -363,6 +367,45 @@ oss# lctl set_param nodemap.add_nodemap_idmap='SiteName +
+ <literal>default</literal> Nodemap + + There is a special nodemap called default. As the + name suggests, it is created by default and cannot be removed. It is like + a fallback nodemap, setting the behaviour for Lustre clients that do not + match any other nodemap. + Because of its special role, only some parameters can be set on the + default nodemap: + + + admin + + + trusted + + + squash_uid + + + squash_gid + + + fileset + + + audit_mode + + + In particular, no UID/GID mapping can be defined on the + default nodemap. + + Be careful when altering the admin and + trusted properties of the default + nodemap, especially if your Lustre servers fall into this nodemap. + + +
+
Verifying Settings