.B lfs getstripe [--obd|-O <uuid>] [--quiet|-q] [--verbose|-v]
\fB[--stripe-count|-c ] [--stripe-index|-i] [--mdt-index|-M]
\fB[--stripe-size|-S] [--directory|-d]
- \fB[--layout|-L]
+ \fB[--layout|-L]
\fB[--pool|-p] [--recursive|-r] [--raw|-R] <dirname|filename> ...\fR
.br
.B lfs setstripe [--stripe-size|-S stripe_size] [--stripe-count|-c stripe_count]
- \fB[--stripe-index|-i start_ost_index
] [--pool|-p <poolname>]
- \fB<directory|filename>\fR
+ \fB[--stripe-index|-i start_ost_index] [--pool|-p <poolname>]
+ \fB[--ost-list|-o <ost_indices>] <directory|filename>\fR
.br
.B lfs setstripe -d <dir>
.br
.B lfs osts
.RB [ path ]
.br
+.B
lfs path2fid [--parents] <path> ...
.br
.B lfs pool_list <filesystem>[.<pool>] | <pathname>
.br
.br
.B lfs data_version [-n] \fB<filename>\fR
.br
-.B lfs mkdir <--index|-i mdt_index> <dir>
+.B lfs --version
.br
.B lfs help
.SH DESCRIPTION
.B lfs
can be used to create a new file with a specific striping pattern, determine the default striping pattern, gather the extended attributes (object numbers and location) for a specific file. It can be invoked interactively without any arguments or in a non-interactive mode with one of the arguements supported.
.SH OPTIONS
-The various options supported by lctl are listed and explained below:
+The various options supported by lfs are listed and explained below:
.TP
.B changelog
Show the metadata changes on an MDT. Start and end points are optional. The --follow option will block on new changes; this option is only valid when run direclty on the MDT node.
.B getstripe [--obd|-O <uuid>] [--quiet|-q] [--verbose|-v]
\fB[--count | -c ] [--index | -i | --offset | -o ]
\fB[--pool | -p ] [--size | -s ] [--directory | -d ]
- \fB[--layout | -L]
+ \fB[--layout | -L]
\fB[--recursive | -r ] [--raw | -R ] <dirname|filename>\fR
.br
List the striping information for a given filename or directory tree.
.TP
.B setstripe [--stripe-count|-c stripe_count] [--stripe-size|-S stripe_size]
\fB[--stripe-index|-i start_ost_index] [--pool <poolname>]
- \fB<dirname|filename>\fR
+ \fB[--ost-index|-o <ost_indices>] <dirname|filename>\fR
.br
-To create a new file, or set the directory default, with the specified striping parameters. The
+To create a new file, or set the directory default, with the specified striping
+parameters. The
.I stripe_count
is the number of OSTs to stripe a file over. A
.I stripe_count
.I start_ost_index
is the OST index (starting at 0) on which to start striping for this file. A
.I start_ost_index
-of -1 allows the MDS to choose the starting index and it is strongly recommended, as this allows space and load balancing to be done by the MDS as needed. The
+of -1 allows the MDS to choose the starting index and it is strongly
+recommended, as this allows space and load balancing to be done by the MDS as
+needed. The
+.B -o
+option is used to specify the exact stripe layout on the file system.
+.I ost_indices
+is a list of OSTs referenced by their indices, which are specified in decimal
+or hex form and can be obtained using the
+.B lfs osts
+command. The list format consists of individual OST indices and index ranges
+separated by commas, e.g. 1,2-4,7. The
+.B -o
+option may be specified multiple times to stripe across the union of all listed
+OSTs. If the
+.B -c
+option is combined with
+.B -o
+the
+.I stripe_count
+must agree with the number of OSTs in
+.IR ost_indices .
+If the
+.B -i
+option is combined with
+.B -o
+the
+.I start_ost_index
+must be in the OST list, and it will be used as the index on which to start
+striping the file. Otherwise the striping will occur in the order specified in
+.IR ost_indices .
+The
.I poolname
-is the name of a predefined pool of OSTs (see
-.B lctl
-) that will be used for striping. The
+is the name of a predefined pool of OSTs (see
+.BR lctl (8))
+that will be used for striping. The
.IR stripe_count ,
.IR stripe_size ,
and
.I start_ost_index
-will be used as well; the
+will be used as well; the
.I start_ost_index
-must be part of the pool or an error will be returned.
+must be part of the pool or an error will be returned.
.TP
.B setstripe -d
Delete the default striping on the specified directory.
at 0, in no particular order). If multiple fids are specified, but only a
single pathname is needed for each file, use \fB--link 0\fR.
.TP
-.B path2fid <path> ...
+.B path2fid
[--parents] <path> ...
Print out the FIDs for the specified \fBpath(s)\fR. If multiple pathnames
are given, then they will be printed one per line with the path as prefix.
+The \fB--parents\fR switch makes it output the parent FID and name(s) of the
+given entries. If an entry has multiple links, these are displayed on a single
+line, tab-separated.
.TP
.B pool_list
.RI { filesystem }[ .poolname "] | {" pathname }
intermediate path components on a series different MDTs and become unavailable
if any of the intermediate MDTs are offline.
.TP
+.B --version
+Output the build version of the lfs utility. Use "lctl lustre_build_version" to get the version of the Lustre kernel modules
+.TP
.B help
Provides brief help on the various arguments
.TP
.B $ lfs setquota -t -u --block-grace 1000 --inode-grace 1w4d /mnt/lustre
Set grace times for user quotas: 1000 seconds for block quotas, 1 week and 4 days for inode quotas
.TP
-.B $ lfs mkdir -i 1 new_directory
-Create directory 'new_directory' on the mdt with index 1.
.SH BUGS
The \fBlfs find\fR command isn't as comprehensive as \fBfind\fR(1).
.SH AUTHOR
The lfs command is part of the Lustre filesystem.
.SH SEE ALSO
.BR lfs-hsm (1),
+.BR lfs-setdirstripe (1),
+.BR lfs-getdirstripe (1),
+.BR lfs-mkdir (1),
.BR lctl (8),
.BR lustre (7)
git://git.whamcloud.com / fs / lustre-release.git / blobdiff