1 <?xml version="1.0" encoding="utf-8"?>
2 <chapter xmlns="http://docbook.org/ns/docbook"
3 xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US"
4 xmlns:xi="http://www.w3.org/2001/XInclude" xml:id="userutilities">
5 <title xml:id="userutilities.title">User Utilities</title>
6 <para>This chapter describes user utilities.</para>
7 <section xml:id="userutilities.lfs">
10 <primary>lfs</primary>
12 <literal>lfs</literal>
15 <literal>lfs</literal> utility can be used for user configuration routines
16 and monitoring.</para>
18 <title>Synopsis</title>
21 lfs changelog [--follow] <replaceable>mdt_name</replaceable> [startrec [endrec]]
22 lfs changelog_clear <replaceable>mdt_name id endrec</replaceable>
23 lfs check <replaceable>mds|osts|servers</replaceable>
24 lfs data_version [-nrw] <replaceable>filename</replaceable>
25 lfs df [-i] [-h] [--pool]-p <replaceable>fsname</replaceable>[.<replaceable>pool</replaceable>] [<replaceable>path</replaceable>] [--lazy]
26 lfs find [[!] --atime|-A [-+]N] [[!] --mtime|-M [-+]N]
27 [[!] --ctime|-C [-+]N] [--maxdepth|-D N] [--name|-n <replaceable>pattern</replaceable>]
28 [--print|-p] [--print0|-P] [[!] --obd|-O <replaceable>ost_name</replaceable>[,<replaceable>ost_name...</replaceable>]]
29 [[!] --size|-S [+-]N[kMGTPE]] --type |-t {bcdflpsD}]
30 [[!] --gid|-g|--group|-G <replaceable>gname|gid</replaceable>]
31 [[!] --uid|-u|--user|-U <replaceable>uname|uid</replaceable>]
32 <replaceable>dirname|filename</replaceable>
33 lfs getname [-h]|[path...]
34 lfs getstripe [--obd|-O <replaceable>ost_name</replaceable>] [--quiet|-q] [--verbose|-v]
35 [--stripe-count|-c] [--stripe-index|-i]
36 [--stripe-size|-s] [--pool|-p] [--directory|-d]
37 [--mdt-index|-M] [--recursive|-r] [--raw|-R]
39 <replaceable>dirname|filename</replaceable> ...
40 lfs setstripe [--size|-s stripe_size] [--stripe-count|-c <replaceable>stripe_count</replaceable>]
41 [--overstripe-count|-C <replaceable>stripe_count</replaceable>]
42 [--stripe-index|-i <replaceable>start_ost_index</replaceable>]
43 [--ost-list|-o <replaceable>ost_indicies</replaceable>]
44 [--pool|-p <replaceable>pool</replaceable>]
45 <replaceable>dirname|filename</replaceable>
46 lfs setstripe -d <replaceable>dir</replaceable>
48 lfs pool_list <replaceable>filesystem</replaceable>[.<replaceable>pool</replaceable>]| <replaceable>pathname</replaceable>
49 lfs quota [-q] [-v] [-h] [-o <replaceable>obd_uuid</replaceable>|-I <replaceable>ost_idx</replaceable>|-i <replaceable>mdt_idx</replaceable>]
50 [-u <replaceable>username|uid|-g</replaceable> <replaceable>group|gid</replaceable>|-p <replaceable>projid</replaceable>] <replaceable>/mount_point</replaceable>
51 lfs quota -t -u|-g|-p <replaceable>/mount_point</replaceable>
52 lfs setquota {-u|--user|-g|--group|-p|--project} <replaceable>uname|uid|gname|gid|projid</replaceable>
53 [--block-softlimit <replaceable>block_softlimit</replaceable>]
54 [--block-hardlimit <replaceable>block_hardlimit</replaceable>]
55 [--inode-softlimit <replaceable>inode_softlimit</replaceable>]
56 [--inode-hardlimit <replaceable>inode_hardlimit</replaceable>]
57 <replaceable>/mount_point</replaceable>
58 lfs setquota -u|--user|-g|--group|-p|--project <replaceable>uname|uid|gname|gid|projid</replaceable>
59 [-b <replaceable>block_softlimit</replaceable>] [-B <replaceable>block_hardlimit</replaceable>]
60 [-i <replaceable>inode-softlimit</replaceable>] [-I <replaceable>inode_hardlimit</replaceable>]
61 <replaceable>/mount_point</replaceable>
62 lfs setquota -t -u|-g|-p [--block-grace <replaceable>block_grace</replaceable>]
63 [--inode-grace <replaceable>inode_grace</replaceable>]
64 <replaceable>/mount_point</replaceable>
65 lfs setquota -t -u|-g|-p [-b <replaceable>block_grace</replaceable>] [-i <replaceable>inode_grace</replaceable>]
66 <replaceable>/mount_point</replaceable>
70 <para>In the above example, the
72 <replaceable>/mount_point</replaceable>
73 </literal> parameter refers to the mount point of the Lustre file
77 <para>The old lfs quota output was very detailed and contained
78 cluster-wide quota statistics (including cluster-wide limits for a
79 user/group and cluster-wide usage for a user/group), as well as
80 statistics for each MDS/OST. Now,
81 <literal>lfs quota</literal> has been updated to provide only
82 cluster-wide statistics, by default. To obtain the full report of
83 cluster-wide limits, usage and statistics, use the
84 <literal>-v</literal> option with
85 <literal>lfs quota</literal>.</para>
87 <para condition="l28">
88 The <literal>quotacheck</literal>, <literal>quotaon</literal> and
89 <literal>quotaoff</literal> sub-commands were deprecated in the
90 Lustre 2.4 release, and removed completely in the Lustre 2.8 release.
91 See <xref linkend="enabling_disk_quotas"/> for details on
92 configuring and checking quotas.
96 <title>Description</title>
98 <literal>lfs</literal> utility is used to create a new file with a
99 specific striping pattern, determine the default striping pattern, gather
100 the extended attributes (object numbers and location) for a specific
101 file, find files with specific attributes, list OST information or set
102 quota limits. It can be invoked interactively without any arguments or in
103 a non-interactive mode with one of the supported arguments.</para>
106 <title>Options</title>
108 <literal>lfs</literal> options are listed and described below. For a
109 complete list of available options, type help at the
110 <literal>lfs</literal> prompt.</para>
111 <informaltable frame="all">
113 <colspec colname="c1" colwidth="20*" />
114 <colspec colname="c2" colwidth="30*" />
115 <colspec colname="c3" colwidth="50*" />
118 <entry nameend="c2" namest="c1">
120 <emphasis role="bold">Option</emphasis>
125 <emphasis role="bold">Description</emphasis>
132 <entry nameend="c2" namest="c1">
134 <literal>changelog</literal>
138 <para>Shows the metadata changes on an MDT. Start and end
139 points are optional. The
140 <literal>--follow</literal> option blocks on new changes; this
141 option is only valid when run directly on the MDT node.</para>
145 <entry nameend="c2" namest="c1">
147 <literal>changelog_clear</literal>
151 <para>Indicates that changelog records previous to
153 <replaceable>endrec</replaceable>
154 </literal> are no longer of interest to a particular consumer
156 <replaceable>id</replaceable>
157 </literal>, potentially allowing the MDT to free up disk space.
160 <replaceable>endrec</replaceable>
161 </literal> of 0 indicates the current last record. Changelog
162 consumers must be registered on the MDT node using
163 <literal>lctl</literal>.</para>
167 <entry nameend="c2" namest="c1">
168 <literal>check</literal>
171 <para>Displays the status of MDS or OSTs (as specified in the
172 command) or all servers (MDS and OSTs).</para>
176 <entry nameend="c2" namest="c1">
178 <literal>data_version [-nrw]
179 <replaceable>filename</replaceable></literal>
183 <para>Displays the current version of file data. If
184 <literal>-n</literal> is specified, the data version is read
185 without taking a lock. As a consequence, the data version could
186 be outdated if there are dirty caches on filesystem clients, but
187 this option will not force data flushes and has less of an
188 impact on the filesystem. If <literal>-r</literal> is specified,
189 the data version is read after dirty pages on clients are
190 flushed. If <literal>-w</literal> is specified, the data version
191 is read after all caching pages on clients are flushed.
194 Even with <literal>-r</literal> or <literal>-w</literal>, race
195 conditions are possible and the data version should be checked
196 before and after an operation to be confident the data did not
200 The data version is the sum of the last committed transaction
201 numbers of all data objects of a file. It is used by HSM policy
202 engines for verifying that file data has not been changed during
203 an archive operation or before a release operation, and by OST
204 migration, primarily for verifying that file data has not been
205 changed during a data copy, when done in non-blocking mode.
210 <entry nameend="c2" namest="c1">
211 <literal>df [-i] [-h] [--pool|-p
212 <replaceable>fsname</replaceable>[.
213 <replaceable>pool</replaceable>] [
214 <replaceable>path</replaceable>] [--lazy]</literal>
218 <literal>-i</literal> to report file system disk space usage or
219 inode usage of each MDT or OST or, if a pool is specified with
221 <literal>-p</literal> option, a subset of OSTs.</para>
222 <para>By default, the usage of all mounted Lustre file systems
224 <literal>path</literal> option is included, only the usage for
225 the specified file system is reported. If the
226 <literal>-h</literal> option is included, the output is printed
227 in human-readable format, using SI base-2 suffixes for
228 <emphasis role="bold">M</emphasis>ega-,
229 <emphasis role="bold">G</emphasis>iga-,
230 <emphasis role="bold">T</emphasis>era-,
231 <emphasis role="bold">P</emphasis>eta-, or
232 <emphasis role="bold">E</emphasis>xabytes.</para>
234 <literal>--lazy</literal> option is specified, any OST that is
235 currently disconnected from the client will be skipped. Using
237 <literal>--lazy</literal> option prevents the
238 <literal>df</literal> output from being blocked when an OST is
239 offline. Only the space on the OSTs that can currently be
240 accessed are returned. The
241 <literal>llite.*.lazystatfs</literal> tunable can be enabled to
242 make this the default behaviour for all
243 <literal>statfs()</literal> operations.</para>
247 <entry nameend="c2" namest="c1">
249 <literal>find</literal>
253 <para>Searches the directory tree rooted at the given
254 directory/filename for files that match the given
257 <literal>!</literal> before an option negates its meaning (files
258 NOT matching the parameter). Using
259 <literal>+</literal> before a numeric value means files with the
260 parameter OR MORE. Using
261 <literal>-</literal> before a numeric value means files with the
262 parameter OR LESS.</para>
268 <literal>--atime</literal>
271 <para>File was last accessed N*24 hours ago. (There is no
273 <literal>atime</literal> is kept coherent across the
275 <para>OSTs by default only hold a transient
276 <literal>atime</literal> that is updated when clients do read
278 <literal>atime</literal> is written to the MDT when the file is
279 closed. However, on-disk atime is only updated if it is more
280 than 60 seconds old (
281 <literal>mdd.*.atime_diff</literal>).
283 <para condition='l2D'>In Lustre 2.14, it is possible to set
284 the OSTs to persistently store atime with each object, in
285 order to get more accurate persistent atime updates for files
286 that are open for a long time via the similarly-named
287 <literal>obdfilter.*.atime_diff</literal> parameter.
290 The client considers the latest <literal>atime</literal> from
291 all OSTs and MDTs. If a
292 <literal>setattr</literal> is set by user, then it is updated on
293 both the MDT and OST, allowing the
294 <literal>atime</literal> to go backward.</para>
303 <literal>--ctime</literal>
307 <para>File status was last changed N*24 hours ago.</para>
316 <literal>--mtime</literal>
320 <para>File data was last modified N*24 hours ago.</para>
329 <literal>--obd</literal>
333 <para>File has an object on a specific OST(s).</para>
342 <literal>--size</literal>
346 <para>File has a size in bytes, or kilo-, Mega-, Giga-, Tera-,
347 Peta- or Exabytes if a suffix is given.</para>
356 <literal>--type</literal>
360 <para>File has the type - block, character, directory, pipe,
361 file, symlink, socket or door (used in Solaris operating
371 <literal>--uid</literal>
375 <para>File has a specific numeric user ID.</para>
384 <literal>--user</literal>
388 <para>File owned by a specific user (numeric user ID
398 <literal>--gid</literal>
402 <para>File has a specific group ID.</para>
411 <literal>--group</literal>
415 <para>File belongs to a specific group (numeric group ID
425 <literal>-maxdepth</literal></para>
428 <para>Limits find to descend at most N levels of the directory
438 <literal>--print</literal>/
439 <literal>--print0</literal></para>
442 <para>Prints the full filename, followed by a new line or NULL
443 character correspondingly.</para>
447 <entry nameend="c2" namest="c1">
449 <literal>osts [path]</literal>
453 <para>Lists all OSTs for the file system. If a path located on
454 a mounted Lustre file system is specified, then only OSTs
455 belonging to this file system are displayed.</para>
459 <entry nameend="c2" namest="c1">
461 <literal>getname [path...]</literal>
465 <para>List each Lustre file system instance associated with
466 each Lustre mount point. If no path is specified, all Lustre
467 mount points are interrogated. If a list of paths is provided,
468 the instance of each path is provided. If the path is not a
469 Lustre instance 'No such device' is returned.</para>
473 <entry nameend="c2" namest="c1">
475 <literal>getstripe</literal>
479 <para>Lists striping information for a given filename or
480 directory. By default, the stripe count, stripe size and offset
482 <para>If you only want specific striping information, then the
484 <literal>--stripe-count</literal>,
485 <literal>--stripe-size</literal>,
486 <literal>--stripe-index</literal>,
487 <literal>--layout</literal>, or
488 <literal>--pool</literal> plus various combinations of these
489 options can be used to retrieve specific information.</para>
491 <literal>--raw</literal> option is specified, the stripe
492 information is printed without substituting the file system
493 default values for unspecified fields. If the striping EA is
494 not set, 0, 0, and -1 will be printed for the stripe count,
495 size, and offset respectively.</para>
496 <para>The <literal>--mdt-index</literal> prints the index of
497 the MDT for a given directory. See
498 <xref linkend="lustremaint.rmremotedir" />.</para>
508 <replaceable>ost_name</replaceable></literal>
512 <para>Lists files that have an object on a specific OST.</para>
521 <literal>--quiet</literal>
525 <para>Lists details about the file's object ID
535 <literal>--verbose</literal>
539 <para>Prints additional striping information.</para>
548 <literal>--stripe-count</literal>
552 <para>Lists the stripe count (how many OSTs to use).</para>
561 <literal>--index</literal>
565 <para>Lists the index for each OST in the file system.</para>
574 <literal>--offset</literal>
578 <para>Lists the OST index on which file striping starts.</para>
587 <literal>--pool</literal>
591 <para>Lists the pools to which a file belongs.</para>
600 <literal>--size</literal>
604 <para>Lists the stripe size (how much data to write to one OST
605 before moving to the next OST).</para>
614 <literal>--directory</literal>
618 <para>Lists entries about a specified directory instead of its
619 contents (in the same manner as
620 <literal>ls -d</literal>).</para>
629 <literal>--recursive</literal>
633 <para>Recurses into all sub-directories.</para>
637 <entry nameend="c2" namest="c1">
639 <literal>setstripe</literal>
643 <para>Create new files with a specific file layout (stripe
644 pattern) configuration.
646 <para>The file cannot exist prior to using
647 <literal>setstripe</literal>. A directory must exist prior to
649 <literal>setstripe</literal>.</para>
659 <literal>--stripe-count stripe_cnt</literal>
663 <para>Number of OSTs over which to stripe a file. A
664 <literal>stripe_cnt</literal> of 0 uses the file system-wide
665 default stripe count (default is 1). A
666 <literal>stripe_cnt</literal> of -1 stripes over all available
676 <literal>--overstripe-count stripe_cnt</literal>
680 <para>The same as --stripe-count, but allows overstriping,
681 which will place more than one stripe per OST if
682 <literal>stripe_cnt</literal> is greater than the number of
683 OSTs. Overstriping is useful for matching the number of stripes
684 to the number of processes, or with very fast OSTs, where one
685 stripe per OST is not enough to get full performance.</para>
694 <literal>--size stripe_size</literal>
696 <para>The default stripe-size is 0. The default start-ost is
697 -1. Do NOT confuse them! If you set start-ost to 0, all new
698 file creations occur on OST 0 (seldom a good idea).</para>
699 </footnote> </para>
702 <para>Number of bytes to store on an OST before moving to the
703 next OST. A stripe_size of 0 uses the file system's default
704 stripe size, (default is 1 MB). Can be specified with
705 <emphasis role="bold">k</emphasis>(KB),
706 <emphasis role="bold">m</emphasis>(MB), or
707 <emphasis role="bold">g</emphasis>(GB), respectively.</para>
716 <literal>--stripe-index start_ost_index</literal>
720 <para>The OST index (base 10, starting at 0) on which to start
721 striping for this file. A start_ost_index value of -1 allows
722 the MDS to choose the starting index. This is the default
723 value, and it means that the MDS selects the starting OST as it
724 wants. We strongly recommend selecting this default, as it
725 allows space and load balancing to be done by the MDS as
727 <literal>start_ost_index</literal> value has no relevance on
728 whether the MDS will use round-robin or QoS weighted allocation
729 for the remaining stripes in the file.</para>
738 <literal>--ost-index ost_indices</literal>
742 <para>This option is used to specify the exact stripe
743 layout on the the file system. <literal>ost_indices</literal>
744 is a list of OSTs referenced by their indices and index ranges
745 separated by commas, e.g. <literal>1,2-4,7</literal>.</para>
755 <replaceable>pool</replaceable></literal>
759 <para>Name of the pre-defined pool of OSTs (see
760 <xref linkend="dbdoclet.50438219_38274" />) that will be used
762 <literal>stripe_cnt</literal>,
763 <literal>stripe_size</literal> and
764 <literal>start_ost</literal> values are used as well. The
765 start-ost value must be part of the pool or an error is
770 <entry nameend="c2" namest="c1">
772 <literal>setstripe -d</literal>
776 <para>Deletes default striping on the specified
781 <entry nameend="c2" namest="c1">
783 <literal>pool_list {filesystem}[.poolname]|{pathname}</literal>
787 <para>Lists pools in the file system or pathname, or OSTs in
788 the file system's pool.</para>
792 <entry nameend="c2" namest="c1">
794 <literal>quota [-q] [-v] [-o
795 <replaceable>obd_uuid</replaceable>|-i
796 <replaceable>mdt_idx</replaceable>|-I
797 <replaceable>ost_idx</replaceable>] [-u|-g|-p
798 <replaceable>uname|uid|gname|gid|projid]</replaceable>
799 <replaceable>/mount_point</replaceable></literal>
804 <para>Displays disk usage and limits, either for the full file
805 system or for objects on a specific OBD. A user or group name
806 or an usr, group and project ID can be specified. If all user,
807 group project ID are omitted, quotas for the current UID/GID
808 are shown. The <literal>-q</literal> option disables printing
809 of additional descriptions (including column titles). It fills
810 in blank spaces in the
811 <literal>grace</literal> column with zeros (when there is no
812 grace period set), to ensure that the number of columns is
814 <literal>-v</literal> option provides more verbose (per-OBD
815 statistics) output.</para>
819 <entry nameend="c2" namest="c1">
822 <replaceable>-u|-g|-p</replaceable>
823 <replaceable>/mount_point</replaceable></literal>
827 <para>Displays block and inode grace times for user (
828 <literal>-u</literal>) or group (
829 <literal>-g</literal>) or project (
830 <literal>-p</literal>) quotas.</para>
834 <entry nameend="c2" namest="c1">
836 <literal>setquota {-u|-g|-p
837 <replaceable>uname|uid|gname|gid|projid}</replaceable>
839 <replaceable>block_softlimit</replaceable>]
841 <replaceable>block_hardlimit</replaceable>]
843 <replaceable>inode_softlimit</replaceable>]
845 <replaceable>inode_hardlimit</replaceable>]
846 <replaceable>/mount_point</replaceable></literal>
850 <para>Sets file system quotas for users, groups or one project.
851 Limits can be specified with
852 <literal>--{block|inode}-{softlimit|hardlimit}</literal> or
853 their short equivalents
854 <literal>-b</literal>,
855 <literal>-B</literal>,
856 <literal>-i</literal>,
857 <literal>-I</literal>. Users can set 1, 2, 3 or 4 limits.
860 <literal>setquota</literal> interface is supported, but it may
861 be removed in a future Lustre software release.</para>
862 </footnote>Also, limits can be specified with special suffixes,
863 -b, -k, -m, -g, -t, and -p to indicate units of 1, 2^10, 2^20,
864 2^30, 2^40 and 2^50, respectively. By default, the block limits
865 unit is 1 kilobyte (1,024), and block limits are always
866 kilobyte-grained (even if specified in bytes). See
867 <xref linkend="dbdoclet.50438206_11903" />.</para>
871 <entry nameend="c2" namest="c1">
873 <literal>setquota -t -u|-g|-p [--block-grace
874 <replaceable>block_grace</replaceable>] [--inode-grace
875 <replaceable>inode_grace</replaceable>]
876 <replaceable>/mount_point</replaceable></literal>
880 <para>Sets the file system quota grace times for users or
881 groups. Grace time is specified in '
882 <literal>XXwXXdXXhXXmXXs</literal>' format or as an integer
884 <xref linkend="dbdoclet.50438206_11903" />.</para>
888 <entry nameend="c2" namest="c1">
890 <literal>help</literal>
894 <para>Provides brief help on various
895 <literal>lfs</literal> arguments.</para>
899 <entry nameend="c2" namest="c1">
901 <literal>exit/quit</literal>
905 <para>Quits the interactive
906 <literal>lfs</literal> session.</para>
913 <section remap="h5" xml:id="dbdoclet.50438206_11903">
914 <title>Examples</title>
915 <para>Creates a file striped on two OSTs with 128 KB on each
918 $ lfs setstripe -s 128k -c 2 /mnt/lustre/file1
920 <para>Deletes a default stripe pattern on a given directory. New files
921 use the default striping pattern.</para>
923 $ lfs setstripe -d /mnt/lustre/dir
925 <para>Lists the detailed object allocation of a given file.</para>
927 $ lfs getstripe -v /mnt/lustre/file1
929 <para>List all the mounted Lustre file systems and corresponding Lustre
934 <para>Efficiently lists all files in a given directory and its
935 subdirectories.</para>
937 $ lfs find /mnt/lustre
939 <para>Recursively lists all regular files in a given directory more than
942 $ lfs find /mnt/lustre -mtime +30 -type f -print
944 <para>Recursively lists all files in a given directory that have objects
945 on OST2-UUID. The lfs check servers command checks the status of all
946 servers (MDT and OSTs).</para>
948 $ lfs find --obd OST2-UUID /mnt/lustre/
950 <para>Lists all OSTs in the file system.</para>
954 <para>Lists space usage per OST and MDT in human-readable format.</para>
958 <para>Lists inode usage per OST and MDT.</para>
962 <para>List space or inode usage for a specific OST pool.</para>
965 <replaceable>filesystem</replaceable>[.
966 <replaceable>pool</replaceable>] |
967 <replaceable>pathname</replaceable>
969 <para>List quotas of user 'bob'.</para>
971 $ lfs quota -u bob /mnt/lustre
973 <para>List quotas of project ID '1'.</para>
975 $ lfs quota -p 1 /mnt/lustre
977 <para>Show grace times for user quotas on
978 <literal>/mnt/lustre</literal>.</para>
980 $ lfs quota -t -u /mnt/lustre
982 <para>Sets quotas of user 'bob', with a 1 GB block quota hardlimit and a
983 2 GB block quota softlimit.</para>
985 $ lfs setquota -u bob --block-softlimit 2000000 --block-hardlimit 1000000
988 <para>Sets grace times for user quotas: 1000 seconds for block quotas, 1
989 week and 4 days for inode quotas.</para>
991 $ lfs setquota -t -u --block-grace 1000 --inode-grace 1w4d /mnt/lustre
993 <para>Checks the status of all servers (MDT, OST)</para>
997 <para>Creates a file striped on two OSTs from the pool
998 <literal>my_pool</literal></para>
1000 $ lfs setstripe --pool my_pool -c 2 /mnt/lustre/file
1002 <para>Lists the pools defined for the mounted Lustre file system
1003 <literal>/mnt/lustre</literal></para>
1005 $ lfs pool_list /mnt/lustre/
1007 <para>Lists the OSTs which are members of the pool
1008 <literal>my_pool</literal> in file system
1009 <literal>my_fs</literal></para>
1011 $ lfs pool_list my_fs.my_pool
1013 <para>Finds all directories/files associated with
1014 <literal>poolA</literal>.</para>
1016 $ lfs find /mnt/lustre --pool poolA
1018 <para>Finds all directories/files not associated with a pool.</para>
1020 $ lfs find /mnt//lustre --pool ""
1022 <para>Finds all directories/files associated with pool.</para>
1024 $ lfs find /mnt/lustre ! --pool ""
1026 <para>Associates a directory with the pool
1027 <literal>my_pool</literal>, so all new files and directories are created
1030 $ lfs setstripe --pool my_pool /mnt/lustre/dir
1033 <section remap="h5">
1034 <title>See Also</title>
1036 <xref linkend="dbdoclet.50438219_38274" />
1040 <section xml:id="dbdoclet.lfs_migrate">
1043 <primary>lfs_migrate</primary>
1045 <literal>lfs_migrate</literal>
1048 <literal>lfs_migrate</literal> utility is a simple to migrate file
1049 <emphasis>data</emphasis> between OSTs.</para>
1050 <section remap="h5">
1051 <title>Synopsis</title>
1053 lfs_migrate [<replaceable>lfs_setstripe_options</replaceable>]
1054 [-h] [-n] [-q] [-R] [-s] [-y] [-0] [file|directory ...]
1057 <section remap="h5">
1058 <title>Description</title>
1060 <literal>lfs_migrate</literal> utility is a tool to assist migration
1061 of file data between Lustre OSTs. The utility copies each specified
1062 file to a temporary file using supplied <literal>lfs setstripe</literal>
1063 options, if any, optionally verifies the file contents have not changed,
1064 and then swaps the layout (OST objects) from the temporary file and the
1065 original file (for Lustre 2.5 and later), or renames the temporary file
1066 to the original filename. This allows the user/administrator to balance
1067 space usage between OSTs, or move files off OSTs that are starting to show
1068 hardware problems (though are still functional) or will be removed.</para>
1070 <para>For versions of Lustre before 2.5,
1071 <literal>lfs_migrate</literal> was not integrated with the MDS at all.
1072 That made it UNSAFE for use on files that were being modified by other
1073 applications, since the file was migrated through a copy and rename of
1074 the file. With Lustre 2.5 and later, the new file layout is swapped
1075 with the existing file layout, which ensures that the user-visible
1076 inode number is kept, and open file handles and locks on the file are
1079 <para>Files to be migrated can be specified as command-line arguments. If
1080 a directory is specified on the command-line then all files within the
1081 directory are migrated. If no files are specified on the command-line,
1082 then a list of files is read from the standard input, making
1083 <literal>lfs_migrate</literal> suitable for use with
1084 <literal>lfs find</literal> to locate files on specific OSTs and/or
1085 matching other file attributes, and other tools that generate a list
1086 of files on standard output.</para>
1087 <para>Unless otherwise specified through command-line options, the
1088 file allocation policies on the MDS dictate where the new files
1089 are placed, taking into account whether specific OSTs have been
1090 disabled on the MDS via <literal>lctl</literal> (preventing new
1091 files from being allocated there), whether some OSTs are overly full
1092 (reducing the number of files placed on those OSTs), or if there is
1093 a specific default file striping for the parent directory (potentially
1094 changing the stripe count, stripe size, OST pool, or OST index of a
1098 <literal>lfs_migrate</literal> utility can also be used in some cases to
1101 <primary>fragmentation</primary>
1102 </indexterm>fragmentation. File fragmentation will typically reduce
1103 Lustre file system performance. File fragmentation may be observed on
1104 an aged file system and will commonly occur if the file was written by
1105 many threads. Provided there is sufficient free space (or if it was
1106 written when the file system was nearly full) that is less fragmented
1107 than the file being copied, re-writing a file with
1108 <literal>lfs_migrate</literal> will result in a migrated file with
1109 reduced fragmentation. The tool
1110 <literal>filefrag</literal> can be used to report file fragmentation.
1112 <xref linkend="dbdoclet.50438206_75125" /></para>
1115 <para>As long as a file has extent lengths of tens of megabytes (
1116 <replaceable>read_bandwidth * seek_time</replaceable>) or more, the
1117 read performance for the file will not be significantly impacted by
1118 fragmentation, since the read pipeline can be filled by large reads
1119 from disk even with an occasional disk seek.</para>
1122 <section remap="h5">
1123 <title>Options</title>
1124 <para>Options supporting
1125 <literal>lfs_migrate</literal> are described below.</para>
1126 <informaltable frame="all">
1128 <colspec colname="c1" colwidth="50*" />
1129 <colspec colname="c2" colwidth="50*" />
1134 <emphasis role="bold">Option</emphasis>
1139 <emphasis role="bold">Description</emphasis>
1149 <replaceable>stripecount</replaceable></literal>
1153 <para>Restripe file using the specified stripe count. This
1154 option may not be specified at the same time as the
1155 <literal>-R</literal> option.</para>
1161 <literal>-h</literal>
1165 <para>Display help information.</para>
1170 <literal>-l</literal>
1173 <para>Migrate files with hard links (skips, by default). Files
1174 with multiple hard links are split into multiple separate files
1176 <literal>lfs_migrate</literal>, so they are skipped, by
1177 default, to avoid breaking the hard links.</para>
1182 <literal>-n</literal>
1185 <para>Only print the names of files to be migrated.</para>
1191 <literal>-q</literal>
1195 <para>Run quietly (does not print filenames or status).</para>
1200 <literal>-R</literal>
1202 <entry>Restripe file using default directory striping instead of
1203 keeping striping. This option may not be specified at the same
1205 <literal>-c</literal> option.</entry>
1209 <literal>-s</literal>
1211 <entry>Skip file data comparison after migrate. Default is to
1212 compare migrated file against original to verify
1213 correctness.</entry>
1218 <literal>-y</literal>
1223 <literal>y</literal>' to usage warning without prompting (for
1224 scripts, use with caution).</para>
1229 <literal>-0</literal>
1231 <entry>Expect NUL-terminated filenames on standard input, as
1232 generated by <literal>lfs find -print0</literal> or
1233 <literal>find -print0</literal>. This allows filenames with
1234 embedded newlines to be handled correctly.
1241 <section remap="h5">
1242 <title>Examples</title>
1243 <para>Rebalance all files in
1244 <literal>/mnt/lustre/dir</literal>:</para>
1246 $ lfs_migrate /mnt/lustre/dir
1248 <para>Migrate files in /test filesystem on OST0004 larger than 4 GB in
1249 size and older than a day old:</para>
1251 $ lfs find /test -obd test-OST0004 -size +4G -mtime +1 | lfs_migrate -y
1254 <section remap="h5">
1255 <title>See Also</title>
1257 <xref linkend="userutilities.lfs" />
1261 <section xml:id="dbdoclet.50438206_75125">
1264 <primary>filefrag</primary>
1266 <literal>filefrag</literal>
1269 <literal>e2fsprogs</literal> package contains the
1270 <literal>filefrag</literal> tool which reports the extent of file
1271 fragmentation.</para>
1272 <section remap="h5">
1273 <title>Synopsis</title>
1275 filefrag [ -belsv ] [ files... ]
1278 <section remap="h5">
1279 <title>Description</title>
1281 <literal>filefrag</literal> utility reports the extent of fragmentation in
1283 <literal>filefrag</literal> utility obtains the extent information from
1284 Lustre files using the
1285 <literal>FIEMAP ioctl</literal>, which is efficient and fast, even for
1286 very large files.</para>
1287 <para>In default mode
1289 <para>The default mode is faster than the verbose/extent mode since it
1290 only counts the number of extents.</para>
1292 <literal>filefrag</literal> prints the number of physically discontiguous
1293 extents in the file. In extent or verbose mode, each extent is printed
1294 with details such as the blocks allocated on each OST. For a Lustre file
1295 system, the extents are printed in device offset order (i.e. all of the
1296 extents for one OST first, then the next OST, etc.), not file logical
1297 offset order. If the file logical offset order was used, the Lustre
1298 striping would make the output very verbose and difficult to see if there
1299 was file fragmentation or not.</para>
1301 <para>Note that as long as a file has extent lengths of tens of
1302 megabytes or more (i.e.
1303 <replaceable>read_bandwidth * seek_time >
1304 extent_length</replaceable>), the read performance for the file will
1305 not be significantly impacted by fragmentation, since file readahead
1306 can fully utilize the disk disk bandwidth even with occasional
1309 <para>In default mode
1311 <para>The default mode is faster than the verbose/extent mode.</para>
1313 <literal>filefrag</literal> returns the number of physically discontiguous
1314 extents in the file. In extent or verbose mode, each extent is printed
1315 with details. For a Lustre file system, the extents are printed in device
1316 offset order, not logical offset order.</para>
1318 <section remap="h5">
1319 <title>Options</title>
1320 <para>The options and descriptions for the
1321 <literal>filefrag</literal> utility are listed below.</para>
1322 <informaltable frame="all">
1324 <colspec colname="c1" colwidth="50*" />
1325 <colspec colname="c2" colwidth="50*" />
1330 <emphasis role="bold">Option</emphasis>
1335 <emphasis role="bold">Description</emphasis>
1344 <literal>-b</literal>
1348 <para>Uses the 1024-byte blocksize for the output. By default,
1349 this blocksize is used by the Lustre file system, since OSTs
1350 may use different block sizes.</para>
1356 <literal>-e</literal>
1360 <para>Uses the extent mode when printing the output. This is
1361 the default for Lustre files in verbose mode.</para>
1367 <literal>-l</literal>
1371 <para>Displays extents in LUN offset order. This is the only
1372 available mode for Lustre.</para>
1378 <literal>-s</literal>
1382 <para>Synchronizes any unwritten file data to disk before
1383 requesting the mapping.</para>
1389 <literal>-v</literal>
1393 <para>Prints the file's layout in verbose mode when checking
1394 file fragmentation, including the logical to physical mapping
1395 for each extent in the file and the OST index.</para>
1402 <section remap="h5">
1403 <title>Examples</title>
1404 <para>Lists default output.</para>
1406 $ filefrag /mnt/lustre/foo
1407 /mnt/lustre/foo: 13 extents found
1409 <para>Lists verbose output in extent format.</para>
1411 $ filefrag -v /mnt/lustre/foo
1412 Filesystem type is: bd00bd0
1413 File size of /mnt/lustre/foo is 1468297786 (1433888 blocks of 1024 bytes)
1414 ext: device_logical: physical_offset: length: dev: flags:
1415 0: 0.. 122879: 2804679680..2804802559: 122880: 0002: network
1416 1: 122880.. 245759: 2804817920..2804940799: 122880: 0002: network
1417 2: 245760.. 278527: 2804948992..2804981759: 32768: 0002: network
1418 3: 278528.. 360447: 2804982784..2805064703: 81920: 0002: network
1419 4: 360448.. 483327: 2805080064..2805202943: 122880: 0002: network
1420 5: 483328.. 606207: 2805211136..2805334015: 122880: 0002: network
1421 6: 606208.. 729087: 2805342208..2805465087: 122880: 0002: network
1422 7: 729088.. 851967: 2805473280..2805596159: 122880: 0002: network
1423 8: 851968.. 974847: 2805604352..2805727231: 122880: 0002: network
1424 9: 974848.. 1097727: 2805735424..2805858303: 122880: 0002: network
1425 10: 1097728.. 1220607: 2805866496..2805989375: 122880: 0002: network
1426 11: 1220608.. 1343487: 2805997568..2806120447: 122880: 0002: network
1427 12: 1343488.. 1433599: 2806128640..2806218751: 90112: 0002: network
1428 /mnt/lustre/foo: 13 extents found
1432 <section xml:id="dbdoclet.50438206_86244">
1435 <primary>mount</primary>
1437 <literal>mount</literal>
1440 <literal>mount(8)</literal> Linux command is used to mount a Lustre file
1441 system. When mounting a Lustre file system, mount(8) executes the
1442 <literal>/sbin/mount.lustre</literal> command to complete the mount. The
1443 mount command supports these options specific to a Lustre file
1445 <informaltable frame="all">
1447 <colspec colname="c1" colwidth="50*" />
1448 <colspec colname="c2" colwidth="50*" />
1453 <emphasis role="bold">Server options</emphasis>
1458 <emphasis role="bold">Description</emphasis>
1467 <literal>abort_recov</literal>
1471 <para>Aborts recovery when starting a target</para>
1477 <literal>nosvc</literal>
1481 <para>Starts only MGS/MGC servers</para>
1487 <literal>nomgs</literal>
1491 <para>Start a MDT with a co-located MGS without starting the
1498 <literal>exclude</literal>
1502 <para>Starts with a dead OST</para>
1508 <literal>md_stripe_cache_size</literal>
1512 <para>Sets the stripe cache size for server side disk with a
1513 striped raid configuration</para>
1519 <informaltable frame="all">
1521 <colspec colname="c1" colwidth="50*" />
1522 <colspec colname="c2" colwidth="50*" />
1527 <emphasis role="bold">Client options</emphasis>
1532 <emphasis role="bold">Description</emphasis>
1541 <literal>flock/noflock/localflock</literal>
1545 <para>Enables/disables global flock or local flock support</para>
1551 <literal>user_xattr/nouser_xattr</literal>
1555 <para>Enables/disables user-extended attributes</para>
1561 <literal>user_fid2path/nouser_fid2path</literal>
1565 <para>Enables/disables FID to path translation by
1566 regular users</para>
1572 <literal>retry=</literal>
1576 <para>Number of times a client will retry to mount the file
1584 <section xml:id="dbdoclet.50438206_56217">
1585 <title>Handling Timeouts</title>
1586 <para>Timeouts are the most common cause of hung applications. After a
1587 timeout involving an MDS or failover OST, applications attempting to access
1588 the disconnected resource wait until the connection gets
1590 <para>When a client performs any remote operation, it gives the server a
1591 reasonable amount of time to respond. If a server does not reply either due
1592 to a down network, hung server, or any other reason, a timeout occurs which
1593 requires a recovery.</para>
1594 <para>If a timeout occurs, a message (similar to this one), appears on the
1595 console of the client, and in
1596 <literal>/var/log/messages</literal>:</para>
1598 LustreError: 26597:(client.c:810:ptlrpc_expire_one_request()) @@@ timeout
1600 req@a2d45200 x5886/t0 o38->mds_svc_UUID@NID_mds_UUID:12 lens 168/64 ref 1 fl
1607 vim:expandtab:shiftwidth=2:tabstop=8: