From e7c70e91537ec213122dfed94966eb53c228ae7a Mon Sep 17 00:00:00 2001 From: Artem Blagodarenko Date: Tue, 27 Aug 2013 13:57:17 +0400 Subject: [PATCH] LUDOC-166 mgs: Document new "lctl set_param -P" option The new "lctl set_param -P" syntax for setting permanent configuration parameters in LU-3155 needs to be added to the Lustre manual. Xyratex-bug-id: MRP-272 Signed-off-by: Artem Blagodarenko Change-Id: I44d89d1219ed865d87368ef958a9f5aa207db49e Reviewed-on: http://review.whamcloud.com/7458 Tested-by: Hudson Reviewed-by: Richard Henwood --- LustreOperations.xml | 16 ++++++++++++++++ SystemConfigurationUtilities.xml | 5 ++++- 2 files changed, 20 insertions(+), 1 deletion(-) diff --git a/LustreOperations.xml b/LustreOperations.xml index 33860d8..89b1a38 100644 --- a/LustreOperations.xml +++ b/LustreOperations.xml @@ -256,6 +256,22 @@ $ lctl conf_param testfs.sys.timeout=40 Parameters specified with the lctl conf_param command are set permanently in the file system's configuration file on the MGS. +
+ Setting Permanent Parameters with lctl set_param -P + Use the lctl set_param -P to set parameters permanently. This command must be issued on the MGS. The given parameter is set on every host using lctl upcall. Parameters map to items in /proc/{fs,sys}/{lnet,lustre}. The lctl set_param command uses this syntax: + lctl set_param -P obdtype.obdname.proc_file_name=value + For example: + # lctl set_param -P osc.*.max_dirty_mb=1024 +osc.myth-OST0000-osc.max_dirty_mb=32 +osc.myth-OST0001-osc.max_dirty_mb=32 +osc.myth-OST0002-osc.max_dirty_mb=32 +osc.myth-OST0003-osc.max_dirty_mb=32 +osc.myth-OST0004-osc.max_dirty_mb=32 + Use -d (only with -P) option to delete permanent parameter. Syntax: + lctl set_param -P -dobdtype.obdname.proc_file_name + For example: + # lctl set_param -P -d osc.*.max_dirty_mb +
Listing Parameters To list Lustre or LNET parameters that are available to set, use the lctl list_param command. For example: diff --git a/SystemConfigurationUtilities.xml b/SystemConfigurationUtilities.xml index 4dd84ff..4080633 100644 --- a/SystemConfigurationUtilities.xml +++ b/SystemConfigurationUtilities.xml @@ -212,9 +212,12 @@ quit Setting Parameters with lctl Lustre parameters are not always accessible using the procfs interface, as it is platform-specific. As a solution, lctl {get,set}_param has been introduced as a platform-independent interface to the Lustre tunables. Avoid direct references to /proc/{fs,sys}/{lustre,lnet}. For future portability, use lctl {get,set}_param . When the file system is running, use the lctl set_param command on the affected node(s) to temporarily set parameters (mapping to items in /proc/{fs,sys}/{lnet,lustre}). The lctl set_param command uses this syntax: - lctl set_param [-n] obdtype.obdname.property=value + lctl set_param [-n] [-P] [-d] obdtype.obdname.property=value For example: mds# lctl set_param mdt.testfs-MDT0000.identity_upcall=NONE + Use -P option to set parameters permanently. Option -d deletes permanent parameters. For example: + mgs# lctl set_param -P mdt.testfs-MDT0000.identity_upcall=NONE +mgs# lctl set_param -P -d mdt.testfs-MDT0000.identity_upcall Many permanent parameters can be set with lctl conf_param. In general, lctl conf_param can be used to specify any OBD device parameter settable in a /proc/fs/lustre file. The lctl conf_param command must be run on the MGS node, and uses this syntax: obd|fsname.obdtype.property=value) For example: -- 1.8.3.1