1 .TH lctl 1 "2003 Oct 8" Lustre "configuration utilities"
3 lctl \- Low level Lustre filesystem configuration utility
8 .B lctl --device <devno> <command [args]>
12 is used to directly control Lustre via an ioctl interface, allowing
13 various configuration, maintenance, and debugging features to be accessed.
16 can be invoked in interactive mode by issuing lctl command. After that, commands are issued as below. The most common commands in lctl are
33 To get a complete listing of available commands, type
35 at the lctl prompt. To get basic help on the meaning and syntax of a
39 . Command completion is activated with the TAB key, and command history is available via the up- and down-arrow keys.
41 For non-interactive use, one uses the second invocation, which runs command after connecting to the device.
43 .SS Network Configuration
45 .BI network " <up/down>|<tcp/elan/myrinet>"
46 Start or stop LNET, or select a network type for other
51 Print all Network Identifiers on the local node. LNET must be running.
53 .BI which_nid " <nidlist>"
54 From a list of nids for a remote node, show which interface communication
58 Check LNET connectivity via an LNET ping. This will use the fabric
59 appropriate to the specified NID.
62 Print the network interface information for a given
67 Print the known peers for a given
72 Print all the connected remote NIDs for a given
77 This command should print active transmits, and it is only used for elan network type.
80 Print the complete routing table.
84 .BI device " <devname> "
85 This will select the specified OBD device. All other commands depend on the device being set.
88 Show all the local Lustre OBDs. AKA
93 .BI conf_param " <device> <parameter>"
94 Set a permanent configuration parameter for any device via the MGS. This
95 command must be run on the MGS node.
98 Reactivate an import after deactivating, below.
101 Deactivate an import, in particular meaning do not assign new file stripes
102 to an OSC. This command should be used on the OSC in the MDT LOV
103 corresponding to a failed OST device, to prevent further attempts at
104 communication with the failed OST.
107 Abort the recovery process on a restarting MDT or OST device
112 Start and stop the debug daemon, and control the output filename and size.
114 .BI debug_kernel " [file] [raw]"
115 Dump the kernel debug buffer to stdout or file.
117 .BI debug_file " <input> [output]"
118 Convert kernel-dumped debug log from binary to plain text format.
121 Clear the kernel debug buffer.
124 Insert marker text in the kernel debug buffer.
126 .BI filter " <subsystem id/debug mask>"
127 Filter kernel debug messages by subsystem or mask.
129 .BI show " <subsystem id/debug mask>"
130 Show specific type of messages.
132 .BI debug_list " <subs/types>"
133 List all the subsystem and debug types.
135 .BI modules " <path>"
136 Provide gdb-friendly module information.
139 The following options can be used to invoke lctl.
142 The device to be used for the operation. This can be specified by name or
146 .B --ignore_errors | ignore_errors
147 Ignore errors during script processing
153 0 UP mgc MGC192.168.0.20@tcp bfbb24e3-7deb-2ffa-eab0-44dffe00f692 5
154 1 UP ost OSS OSS_uuid 3
155 2 UP obdfilter testfs-OST0000 testfs-OST0000_UUID 3
158 Debug log: 87 lines, 87 kept, 0 dropped.
162 # lctl conf_param testfs-MDT0000 sys.timeout=40
165 Please report all bugs to ClusterFileSystems, support@clusterfs.com
170 filesystem package and is available from CFS
176 .BR mount.lustre (8),