X-Git-Url: https://git.whamcloud.com/?a=blobdiff_plain;f=LustreOperations.xml;h=51daff3308c3b0b2d34a3c6e9ddf7a9c88aa4b1b;hb=1d0c79a707d20d2bf034a6fe4eb1d48adf5e74de;hp=64ddbb4bbe1a9fa709dd8552424fe756862a81a3;hpb=7d1f65c497503390e592ee71f95ac310f0054a16;p=doc%2Fmanual.git diff --git a/LustreOperations.xml b/LustreOperations.xml index 64ddbb4..51daff3 100644 --- a/LustreOperations.xml +++ b/LustreOperations.xml @@ -134,22 +134,87 @@ LABEL=testfs-OST0000 /mnt/test/ost0 lustre defaults,_netdev,noauto 0 0 environment. -
+
+ + <indexterm> + <primary>operations</primary> + <secondary>shutdownLustre</secondary> + </indexterm>Stopping the Filesystem + A complete Lustre filesystem shutdown occurs by unmounting all + clients and servers in the order shown below. Please note that unmounting + a block device causes the Lustre software to be shut down on that node. + + Please note that the -a -t lustre in the + commands below is not the name of a filesystem, but rather is + specifying to unmount all entries in /etc/mtab that are of type + lustre + + Unmount the clients + On each client node, unmount the filesystem on that client + using the umount command: + umount -a -t lustre + The example below shows the unmount of the + testfs filesystem on a client node: + [root@client1 ~]# mount |grep testfs +XXX.XXX.0.11@tcp:/testfs on /mnt/testfs type lustre (rw,lazystatfs) + +[root@client1 ~]# umount -a -t lustre +[154523.177714] Lustre: Unmounted testfs-client + + Unmount the MDT and MGT + On the MGS and MDS node(s), use the umount + command: + umount -a -t lustre + The example below shows the unmount of the MDT and MGT for + the testfs filesystem on a combined MGS/MDS: + + [root@mds1 ~]# mount |grep lustre +/dev/sda on /mnt/mgt type lustre (ro) +/dev/sdb on /mnt/mdt type lustre (ro) + +[root@mds1 ~]# umount -a -t lustre +[155263.566230] Lustre: Failing over testfs-MDT0000 +[155263.775355] Lustre: server umount testfs-MDT0000 complete +[155269.843862] Lustre: server umount MGS complete + For a seperate MGS and MDS, the same command is used, first on + the MDS and then followed by the MGS. + + Unmount all the OSTs + On each OSS node, use the umount command: + + umount -a -t lustre + The example below shows the unmount of all OSTs for the + testfs filesystem on server + OSS1: + + [root@oss1 ~]# mount |grep lustre +/dev/sda on /mnt/ost0 type lustre (ro) +/dev/sdb on /mnt/ost1 type lustre (ro) +/dev/sdc on /mnt/ost2 type lustre (ro) + +[root@oss1 ~]# umount -a -t lustre +[155336.491445] Lustre: Failing over testfs-OST0002 +[155336.556752] Lustre: server umount testfs-OST0002 complete + + + For unmount command syntax for a single OST, MDT, or MGT target + please refer to +
+
<indexterm> <primary>operations</primary> <secondary>unmounting</secondary> - </indexterm>Unmounting a Server - To stop a Lustre server, use the + Unmounting a Specific Target on a Server + To stop a Lustre OST, MDT, or MGT , use the umount - /mount - point command. - For example, to stop - ost0 on mount point - /mnt/test, run: - -$ umount /mnt/test - + /mount_point command. + The example below stops an OST, ost0, on mount + point /mnt/ost0 for the testfs + filesystem: + [root@oss1 ~]# umount /mnt/ost0 +[ 385.142264] Lustre: Failing over testfs-OST0000 +[ 385.210810] Lustre: server umount testfs-OST0000 complete Gracefully stopping a server with the umount command preserves the state of the connected clients. The next time the server is started, it waits for clients to @@ -227,7 +292,7 @@ $ tunefs.lustre --param failover.mode=failout
-
+
<indexterm> <primary>operations</primary> @@ -259,7 +324,9 @@ lctl get_param obdfilter.*.degraded resets to <literal>0</literal>.</para> <para>It is recommended that this be implemented by an automated script - that monitors the status of individual RAID devices.</para> + that monitors the status of individual RAID devices, such as MD-RAID's + <literal>mdadm(8)</literal> command with the <literal>--monitor</literal> + option to mark an affected device degraded or restored.</para> </section> <section xml:id="dbdoclet.50438194_88063"> <title> @@ -432,7 +499,7 @@ client# lfs mkdir –i <para>The Lustre 2.8 DNE feature enables individual files in a given directory to store their metadata on separate MDTs (a <emphasis>striped directory</emphasis>) once additional MDTs have been added to the - filesystem, see <xref linkend="dbdoclet.addingamdt"/>. + filesystem, see <xref linkend="dbdoclet.adding_new_mdt"/>. The result of this is that metadata requests for files in a striped directory are serviced by multiple MDTs and metadata service load is distributed over all the MDTs that service a given @@ -512,8 +579,8 @@ mds# tunefs.lustre --erase-params --param= <replaceable>new_parameters</replaceable> </screen> <para>The tunefs.lustre command can be used to set any parameter settable - in a /proc/fs/lustre file and that has its own OBD device, so it can be - specified as + via <literal>lctl conf_param</literal> and that has its own OBD device, + so it can be specified as <literal> <replaceable>obdname|fsname</replaceable>. <replaceable>obdtype</replaceable>. @@ -535,8 +602,8 @@ mds# tunefs.lustre --param mdt.identity_upcall=NONE /dev/sda1 are active as long as the server or client is not shut down. Permanent parameters live through server and client reboots.</para> <note> - <para>The lctl list_param command enables users to list all parameters - that can be set. See + <para>The <literal>lctl list_param</literal> command enables users to + list all parameters that can be set. See <xref linkend="dbdoclet.50438194_88217" />.</para> </note> <para>For more details about the @@ -551,7 +618,7 @@ mds# tunefs.lustre --param mdt.identity_upcall=NONE /dev/sda1 <literal>/proc/{fs,sys}/{lnet,lustre}</literal>. The <literal>lctl set_param</literal> command uses this syntax:</para> <screen> -lctl set_param [-n] +lctl set_param [-n] [-P] <replaceable>obdtype</replaceable>. <replaceable>obdname</replaceable>. <replaceable>proc_file_name</replaceable>= @@ -569,7 +636,7 @@ osc.myth-OST0004-osc.max_dirty_mb=32 </section> <section xml:id="dbdoclet.50438194_64195"> <title>Setting Permanent Parameters - Use the + Use lctl set_param -P or lctl conf_param command to set permanent parameters. In general, the lctl conf_param command can be used to specify any @@ -604,13 +671,12 @@ $ lctl conf_param testfs.sys.timeout=40
Setting Permanent Parameters with lctl set_param -P - Use the - lctl set_param -P to set parameters permanently. This - command must be issued on the MGS. The given parameter is set on every - host using - lctl upcall. Parameters map to items in - /proc/{fs,sys}/{lnet,lustre}. The - lctl set_param command uses this syntax: + The lctl set_param -P command can also + set parameters permanently. This command must be issued on the MGS. + The given parameter is set on every host using + lctl upcall. Parameters map to items in + /proc/{fs,sys}/{lnet,lustre}. The + lctl set_param command uses this syntax: lctl set_param -P obdtype. @@ -856,7 +922,7 @@ tune2fs [-m reserved_blocks_percent] /dev/ To copy the contents of an existing OST to a new OST (or an old MDT to a new MDT), follow the process for either OST/MDT backups in or - . + . For more information on removing a MDT, see .