1 .TH lctl 8 "2017 Jan 12" Lustre "configuration utilities"
3 lctl \- Low level Lustre filesystem configuration utility
8 .B lctl --device <devno> <command [args]>
12 .B lctl --list-commands
16 is used to directly control Lustre via an ioctl interface, allowing
17 various configuration, maintenance, and debugging features to be accessed.
20 can be invoked in interactive mode by issuing lctl command. After that, commands are issued as below. The most common commands in lctl are
32 To get a complete listing of available commands, type
34 at the lctl prompt. To get basic help on the meaning and syntax of a
38 . Command completion is activated with the TAB key, and command history is available via the up- and down-arrow keys.
40 For non-interactive use, one uses the second invocation, which runs command after connecting to the device.
42 .SS Network Configuration
44 .BR network " <" up / down >|< tcp / o2ib >
45 Start or stop LNET, or select a network type for other
50 Print all Network Identifiers on the local node. LNET must be running.
52 .BI which_nid " <nidlist>"
53 From a list of nids for a remote node, show which interface communication
56 .BI replace_nids " <devicename> <nid1>[,nid2,nid3 ...]"
57 Replace the LNET Network Identifiers for a given device,
58 as when the server's IP address has changed.
59 This command must be run on the MGS node.
60 Only MGS server should be started (command execution returns error
61 in another cases). To start the MGS service only:
62 mount -t lustre <MDT partition> -o nosvc <mount point>
63 Note the replace_nids command skips any invalidated records in the configuration log.
64 The previous log is backed up with the suffix '.bak'.
66 .BI ping " <nid> timeout"
67 Check LNET connectivity via an LNET ping. This will use the fabric
68 appropriate to the specified NID. By default lctl will attempt to
69 reach the remote node up to 120 seconds and then timeout. To disable
70 the timeout just specify an negative timeout value.
73 Print the network interface information for a given
78 Print the known peers for a given
83 Print all the connected remote NIDs for a given
88 Print the complete routing table.
92 .BI device " <devname> "
93 This will select the specified OBD device. All other commands depend on the device being set.
96 Show all the local Lustre OBDs. AKA
101 .BI list_param " [-F|-R] <param_search ...>"
102 List the Lustre or LNet parameter name
104 Add '/', '@' or '=' for dirs, symlinks and writeable files, respectively.
107 Recursively list all parameters under the specified parameter search string. If
109 is unspecified, all the parameters will be shown.
114 # lctl list_param ost.*
121 # lctl list_param -F ost.* debug
130 # lctl list_param -R mdt
136 mdt.lustre-MDT0000.capa
138 mdt.lustre-MDT0000.capa_count
140 mdt.lustre-MDT0000.capa_key_timeout
142 mdt.lustre-MDT0000.capa_timeout
144 mdt.lustre-MDT0000.commit_on_sharing
146 mdt.lustre-MDT0000.evict_client
150 .BI get_param " [-F|-n|-N|-R] <parameter ...>"
151 Get the value of Lustre or LNET parameter.
154 When -N specified, add '/', '@' or '=' for directories, symlinks and writeable files, respectively.
158 Print only the value and not parameter name.
161 Print only matched parameter names and not the values. (Especially useful when using patterns.)
164 Print all of the parameter names below the specified name.
169 # lctl get_param ost.*
176 # lctl get_param -n debug timeout
178 super warning dlmtrace error emerg ha rpctrace vfstrace config console
183 # lctl get_param -N ost.* debug
191 lctl "get_param -NF" is equivalent to "list_param -F".
193 .BI set_param " [-n] [-P] [-d] <parameter=value ...>"
194 Set the value of Lustre or LNET parameter.
197 Disable printing of the key name when printing values.
200 Set the parameter permanently, filesystem-wide.
201 This parameters are only visible to 2.5.0 and later clients, older clients will not see these parameters.
204 Remove the permanent setting (only with -P option)
209 # lctl set_param fail_loc=0 timeout=20
216 # lctl set_param -n fail_loc=0 timeout=20
223 # lctl set_param -P osc.*.max_dirty_mb=32
226 .BI conf_param " [-d] <device|fsname>.<parameter>=<value>"
227 Set a permanent configuration parameter for any device via the MGS. This
228 command must be run on the MGS node.
230 .B -d <device|fsname>.<parameter>
231 Delete a parameter setting (use the default value at the next restart). A null value for <value> also deletes the parameter setting.
235 All of the writable parameters under
238 .I lctl list_param -F osc.*.* | grep =
239 ) can be permanently set using
241 , but the format is slightly different. For conf_param, the device is specified first, then the obdtype. (See examples below.) Wildcards are not supported.
243 Additionally, failover nodes may be added (or removed), and some system-wide parameters may be set as well (sys.at_max, sys.at_min, sys.at_extra, sys.at_early_margin, sys.at_history, sys.timeout, sys.ldlm_timeout.) <device> is ignored for system wide parameters.
247 # lctl conf_param testfs.sys.at_max=1200
249 # lctl conf_param testfs.llite.max_read_ahead_mb=16
251 # lctl conf_param testfs-MDT0000.lov.stripesize=2M
253 # lctl conf_param lustre-OST0001.osc.active=0
255 # lctl conf_param testfs-OST0000.osc.max_dirty_mb=29.15
257 # lctl conf_param testfs-OST0000.ost.client_cache_seconds=15
259 # lctl conf_param testfs-OST0000.failover.node=1.2.3.4@tcp1
262 Reactivate an import after deactivating, below. This setting is only effective until the next restart (see
267 Deactivate an import, in particular meaning do not assign new file stripes
268 to an OSC. This command should be used on the OSC in the MDT LOV
269 corresponding to a failed OST device, to prevent further attempts at
270 communication with the failed OST.
273 Abort the recovery process on a restarting MDT or OST device
277 .BI changelog_register " [-n]"
278 Register a new changelog user for a particular device. Changelog entries
279 will not be purged beyond any registered users' set point. (See lfs changelog_clear.)
282 Print only the ID of the newly registered user.
284 .BI changelog_deregister " <id>"
285 Unregister an existing changelog user. If the user's "clear" record number
286 is the minimum for the device, changelog records will be purged until the
290 An identity mapping feature that facilitates mapping of client UIDs and GIDs to
291 local file system UIDs and GIDs, while maintaining POSIX ownership, permissions,
294 While the nodemap feature is enabled, all client file system access is subject
295 to the nodemap identity mapping policy, which consists of the 'default' catchall
296 nodemap, and any user-defined nodemaps. The 'default' nodemap maps all client
297 identities to 99:99 (nobody:nobody). Administrators can define nodemaps for a
298 range of client NIDs which map identities, and these nodemaps can be flagged as
299 'trusted' so identities are accepted without translation, as well as flagged
300 as 'admin' meaning that root is not squashed for these nodes.
302 Note: In the current phase of implementation, to use the nodemap functionality
303 you only need to enable and define nodemaps on the MDS. The MDSes must also be
304 in a nodemap with the admin and trusted flags set. To use quotas with nodemaps,
305 you must also use set_param to enable and define nodemaps on the OSS (matching
306 what is defined on the MDS). Nodemaps do not currently persist, unless you
307 define them with set_param and use the -P flag. Note that there is a hard limit
308 to the number of changes you can persist over the lifetime of the file system.
313 \fBlctl-nodemap-activate\fR(8)
315 Activate/deactivate the nodemap feature.
318 \fBlctl-nodemap-add\fR(8)
320 Add a new nodemap, to which NID ranges, identities, and properties can be added.
323 \fBlctl-nodemap-del\fR(8)
325 Delete an existing nodemap.
328 \fBlctl-nodemap-add-range\fR(8)
330 Define a range of NIDs for a nodemap.
333 \fBlctl-nodemap-del-range\fR(8)
335 Delete an existing NID range from a nodemap.
338 \fBlctl-nodemap-add-idmap\fR(8)
340 Add a UID or GID mapping to a nodemap.
343 \fBlctl-nodemap-del-idmap\fR(8)
345 Delete an existing UID or GID mapping from a nodemap.
348 \fBlctl-nodemap-modify\fR(8)
350 Modify a nodemap property.
354 An on-line Lustre consistency check and repair tool. It is used for totally
355 replacing the old lfsck tool for kinds of Lustre inconsistency verification,
356 including: corrupted or lost OI mapping, corrupted or lost link EA, corrupted
357 or lost FID in name entry, dangling name entry, multiple referenced name entry,
358 unmatched MDT-object and name entry pairs, orphan MDT-object, incorrect
359 MDT-object links count, corrupted namespace, corrupted or lost lov EA, lost
360 OST-object, multiple referenced OST-object, unmatched MDT-object and OST-object
361 pairs, orphan OST-object, and so on.
366 \fBlctl-lfsck-start\fR(8)
368 Start LFSCK on the specified MDT or OST device with specified parameters.
371 \fBlctl-lfsck-stop\fR(8)
373 Stop LFSCK on the specified MDT or OST device.
376 \fBlctl-lfsck-query\fR(8)
378 Get the LFSCK global status via the specified MDT device.
383 Start and stop the debug daemon, and control the output filename and size.
385 .BI debug_kernel " [file] [raw]"
386 Dump the kernel debug buffer to stdout or file.
388 .BI debug_file " <input> [output]"
389 Convert kernel-dumped debug log from binary to plain text format.
392 Clear the kernel debug buffer.
395 Insert marker text in the kernel debug buffer.
397 .BI filter " <subsystem id/debug mask>"
398 Filter kernel debug messages by subsystem or mask.
400 .BI show " <subsystem id/debug mask>"
401 Show specific type of messages.
403 .BI debug_list " <subs/types>"
404 List all the subsystem and debug types.
406 .BI modules " <path>"
407 Provide gdb-friendly module information.
410 The following options can be used to invoke lctl.
413 The device to be used for the operation. This can be specified by name or
417 .B --ignore_errors | ignore_errors
418 Ignore errors during script processing
420 .B lustre_build_version
421 Output the build version of the Lustre kernel modules
424 Output the build version of the lctl utility
427 Output a list of the commands supported by the lctl utility
430 Provides brief help on the various arguments
433 Quit the interactive lctl session
439 0 UP mgc MGC192.168.0.20@tcp bfbb24e3-7deb-2ffa-eab0-44dffe00f692 5
440 1 UP ost OSS OSS_uuid 3
441 2 UP obdfilter testfs-OST0000 testfs-OST0000_UUID 3
444 Debug log: 87 lines, 87 kept, 0 dropped.
456 .BR mount.lustre (8),
458 .BR lctl-lfsck-start (8),
459 .BR lctl-lfsck-stop (8),
460 .BR lctl-lfsck-query (8),
461 .BR lctl-network (8),
462 .BR lctl-nodemap-activate (8),
463 .BR lctl-nodemap-add-idmap (8),
464 .BR lctl-nodemap-add-range (8),
465 .BR lctl-nodemap-add (8),
466 .BR lctl-nodemap-del-idmap (8),
467 .BR lctl-nodemap-del-range (8),
468 .BR lctl-nodemap-del (8),
469 .BR lctl-nodemap-modify (8),