1 .TH LCTL-POOL_ADD 8 "2018-12-12" Lustre "configuration utilities"
3 lctl-pool_add \- add OSTs to a named pool
5 .BR "lctl pool_add" " [" --nowait | -n "] "
6 .IR <fsname> . <pool> " " <ost_index> " " ...
8 .BR "lctl pool_add" " [" --nowait | -n "] "
9 .IR <fsname> . <pool> " " <ost_range> " "...
12 Add one or more OSTs to the pool named
14 in the filesystem named
16 There are several formats that the OSTs can be specified. Simplest is
17 to just specify a list of
19 numbers or OST names. It is also possible to specify an
21 expression of the form
24 .BI [ start - end / step ]
25 that adds multiple OSTs with index numbers in the range from
29 (inclusive), optionally skipping every
34 After updating the MGS configuration, this command tries to wait and
35 check if pools are updated on a client.
36 If the MGS is on a separate node from the MDS, a Lustre client must
37 be mounted on the MGS node while the
39 commands are being run for this. Otherwise, the client check is
42 The OST pool can be used by
44 to specify the OSTs on which new files can be created, and
46 to locate files that were initially created on the specified
48 Note however, that the OSTs that make up a specific pool may change
49 over time, and it is the
51 used at creation time that is stored on each file, not necessarily
52 OSTs that are in the current pool. As well,
54 can show only the free space or inodes in a named pool.
59 Do not wait and check if pool is updated on a client. This is useful
60 when calling a lot of "
62 pool_*" in a row. This avoids revoking the clients "CONFIG" lock for each
63 command (by default clients retake their lock and update their configurations
64 in a delay between 5-10s).
68 .B # lfs pool_new testfs.local
75 .B # lfs pool_add testfs.local 12 13 14
76 Add OSTs numbered 12, 13, and 14 to the
82 .BR lctl-pool_new (8),
85 .BR lfs-setstripe (1),