1 .TH lmc 1 "2003 Oct 8" Lustre "configuration utilities"
3 lmc \- Lustre configuration maker
7 [options] --add <objecttype> [args]
11 , when invoked, adds configuration data to a configuration file. In future,
12 lmc will also be able to remove configuration data or convert its format.
13 A Lustre cluster consists of several components - MDSs, client mount-points,
14 OSTs, LOVs and networks. A single configuration file would be generated for the complete cluster. In the lmc command line interface, each of these components is associated with an objecttype.
16 The objecttype refers to a collection of related configuration entities and can be one of
31 We describe the arguments required for the addition of each objecttype.
33 To generate configuration data associated with systems in a Lustre cluster:
36 Adds a new node in the cluster configuration.
37 The arguements required are:
40 This will create a new node with the given name if not already present.
43 Timeout before going into recovery
45 --lustre_upcall <path>
46 Set the location of the Lustre upcall scripts used by the client for recovery
48 --portals_upcall <path>
49 Specify the location of the Portals upcall scripts used by the client for recovery
52 Specify the location of both (Lustre and Portals) upcall scripts used by the client for recovery
55 Adds a network device descriptor for the given node, with parameters as indicated.
56 The arguments required are:
59 This will create a new node with the given name if not already present. This is also used to specify a specific node for other elements.
62 This can be tcp, elan, gm, scimac.
65 The network id, e.g. ElanID or IP address as used by Portals. If nid is '*', then the local address of the interface with specified nettype is will be substituted when the node is configured with lconf. An nid of '*' should be used only for the generic client configuration.
70 Optional flag to mark this node as a router
73 Optional arguement to indicate the tcp port. The default is 988.
76 Optional arguement. The default TCP buffer size is 1MB.
79 Optional arguement. Default is 0.
82 Optional arguement since some OSTs might not have the required support. This is turned off by default, value of 1 will turn it ON.
85 Specify the MDS configuration
88 Name of the node on which the MDS resides
91 Common name of the MDS
94 Path of device on local system. If the is a file, then a loop device is created and used as the block device.
97 Optional argument indicating the size (in KB) of the device to be created (used typically for loop devices).
100 Adds an MDS to the specified node. This requires a --node argument, and it must not be a profile node.
103 Optional argument used to specify the file system type. Default is ext3.
105 --journal_size <size>
106 Optional arguement to specify the journal size for the ext2/ext3 file system. The size should be in the units expected by mkfs, so for ext3 it should be in MB. If this is option is not used, the ext2/ext3 filesystem will be configured with the default journal size.
109 Creates an LOV with the specified parameters. The mds_name must already exist in the descriptor.
112 Common name for the LOV
115 Common name for the MDS
121 A value of 0 for this means to stripe on all available OSTs. Default is 0.
123 --stripe_pattern <pattern>
124 Only Pattern 0 (RAID 0) is supported currently.
127 Creates an OBD, OST, and OSC. The OST and OBD are created on the specified node.
130 Assign a name to the OST device.
133 Node on which the OST service is run, can not be a profile node.
136 Path of device on local system. If this is a file, then a loop device is created and used as the block device.
139 Optional argument indicating the size (in KB) of the device to be created (used typically for loop devices).
145 Optional arguement. Name of LOV to which this OSC will be attached.
148 Specify the UUID of the OST device.
151 extN|ext3 Optional arguement used to specify the file system type. Default is ext3.
153 --journal_size <size>
154 Optional arguement to specify the journal size for the ext2/ext3 file system. The size should be in the units expected by mkfs, so for ext3 it should be in MB. If this is option is not used, the ext2/ext3 filesystem will be configured with the default journal size.
157 Creates a mount-point on the specified node. Either an LOV or OSC name can be used.
160 Node that will use the mtpt.
163 The mount-point to use to mount Lustre filesystem
168 --ost ost_name | --lov lov_name
169 OST or LOV name as specified earlier in the configuration
172 Creates a static route through a gateway to a specific nid or a range of nid's.
175 Node to add the route to.
178 The nid of the gateway (must be a local interface or a peer).
181 For a specific route, this is the target nid.
184 For a range route, this is the lo value nid.
187 For a range route, this is the hi value nid.
190 Used for testing purpose only.
193 Name of the node that echo client should run on,
197 One of the following options should be specified.
200 Send output to the file. If the file exists, it will be overwritten.
203 Add the new element to an existing file.
205 Real life examples are given in the Lustre-conf manual page.