From 2486c888f37c9efc590bebccffe7eca9817268aa Mon Sep 17 00:00:00 2001 From: Joseph Gmitter Date: Fri, 30 Aug 2019 14:37:35 -0400 Subject: [PATCH] LUDOC-11 misc: Update the xml ids in LustreMaintenance.xml This patch updates the xml:id for each section to be a meaningful name. Other pages using those ids were also updated accordingly. Signed-off-by: Joseph Gmitter Change-Id: I643500b38f213117ff29aeb8ef1270431672e38a Reviewed-on: https://review.whamcloud.com/36015 Tested-by: jenkins Reviewed-by: Andreas Dilger --- BackupAndRestore.xml | 4 +-- ConfiguringFailover.xml | 2 +- LustreMaintenance.xml | 83 ++++++++++++++++++++++--------------------- LustreOperations.xml | 4 +-- LustreTroubleshooting.xml | 2 +- ManagingFileSystemIO.xml | 2 +- ManagingStripingFreeSpace.xml | 2 +- SettingUpLustreSystem.xml | 4 +-- UserUtilities.xml | 2 +- 9 files changed, 54 insertions(+), 51 deletions(-) diff --git a/BackupAndRestore.xml b/BackupAndRestore.xml index 7b34f55..614e8a9 100644 --- a/BackupAndRestore.xml +++ b/BackupAndRestore.xml @@ -769,7 +769,7 @@ trusted.fid= \ [oss]# umount /mnt/ost If the restored system has a different NID from the backup system, please change the NID. For detail, please refer to - . For example: + . For example: [oss]# mount -t lustre -o nosvc ${fsname}-ost/ost /mnt/ost [oss]# lctl replace_nids ${fsname}-OSTxxxx $new_nids [oss]# umount /mnt/ost @@ -1085,7 +1085,7 @@ fstab passwds lfs find/lfs_migrate to empty out an OST while the filesystem is in use and then reformat it with the new fstype. For instructions on removing the OST, please see - . + .
<indexterm> diff --git a/ConfiguringFailover.xml b/ConfiguringFailover.xml index 171bf78..f1e1b63 100644 --- a/ConfiguringFailover.xml +++ b/ConfiguringFailover.xml @@ -180,7 +180,7 @@ /></para> </listitem> <listitem> - <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="dbdoclet.50438199_62333" + <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="lustremaint.ChangeAddrFailoverNode" /></para> </listitem> <listitem> diff --git a/LustreMaintenance.xml b/LustreMaintenance.xml index 4082661..766084b 100644 --- a/LustreMaintenance.xml +++ b/LustreMaintenance.xml @@ -3,61 +3,64 @@ <para>Once you have the Lustre file system up and running, you can use the procedures in this section to perform these basic Lustre maintenance tasks:</para> <itemizedlist> <listitem> - <para><xref linkend="dbdoclet.50438199_42877"/></para> + <para><xref linkend="lustremaint.inactiveOST"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.50438199_15240"/></para> + <para><xref linkend="lustremaint.findingNodes"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.50438199_26070"/></para> + <para><xref linkend="lustremaint.mountingServerWithoutLustre"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.50438199_54623"/></para> + <para><xref linkend="lustremaint.regenerateConfigLogs"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.changingservernid"/></para> + <para><xref linkend="lustremaint.changingservernid"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.adding_new_mdt"/></para> + <para><xref linkend="lustremaint.clear_conf"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.adding_new_ost"/></para> + <para><xref linkend="lustremaint.adding_new_mdt"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.deactivating_mdt_ost"/></para> + <para><xref linkend="lustremaint.adding_new_ost"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.rmremotedir"/></para> + <para><xref linkend="lustremaint.deactivating_mdt_ost"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.inactivemdt"/></para> + <para><xref linkend="lustremaint.rmremotedir"/></para> </listitem> <listitem> - <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="section_remove_ost"/></para> + <para><xref linkend="lustremaint.inactivemdt"/></para> </listitem> <listitem> - <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="section_ydg_pgt_tl"/></para> + <para><xref linkend="lustremaint.remove_ost"/></para> </listitem> <listitem> - <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="section_restore_ost"/></para> + <para><xref linkend="lustremaint.ydg_pgt_tl"/></para> </listitem> <listitem> - <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="section_ucf_qgt_tl"/></para> + <para><xref linkend="lustremaint.restore_ost"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.50438199_77819"/></para> + <para><xref linkend="lustremaint.ucf_qgt_tl"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.50438199_12607"/></para> + <para><xref linkend="lustremaint.abortRecovery"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.50438199_62333"/></para> + <para><xref linkend="lustremaint.determineOST"/></para> </listitem> <listitem> - <para><xref linkend="dbdoclet.50438199_62545"/></para> + <para><xref linkend="lustremaint.ChangeAddrFailoverNode"/></para> + </listitem> + <listitem> + <para><xref linkend="lustremaint.seperateCombinedMGSMDT"/></para> </listitem> </itemizedlist> - <section xml:id="dbdoclet.50438199_42877"> + <section xml:id="lustremaint.inactiveOST"> <title> <indexterm><primary>maintenance</primary></indexterm> <indexterm><primary>maintenance</primary><secondary>inactive OSTs</secondary></indexterm> @@ -74,7 +77,7 @@ <literal>exclude=testfs-OST0000:testfs-OST0001</literal>.</para> </note> </section> - <section xml:id="dbdoclet.50438199_15240"> + <section xml:id="lustremaint.findingNodes"> <title><indexterm><primary>maintenance</primary><secondary>finding nodes</secondary></indexterm> Finding Nodes in the Lustre File System There may be situations in which you need to find all nodes in @@ -105,7 +108,7 @@ Finding Nodes in the Lustre File System 0: testfs-OST0000_UUID ACTIVE 1: testfs-OST0001_UUID ACTIVE
-
+
<indexterm><primary>maintenance</primary><secondary>mounting a server</secondary></indexterm> Mounting a Server Without Lustre Service If you are using a combined MGS/MDT, but you only want to start the MGS and not the MDT, run this command: @@ -114,7 +117,7 @@ Mounting a Server Without Lustre Service In this example, the combined MGS/MDT is testfs-MDT0000 and the mount point is /mnt/test/mdt. $ mount -t lustre -L testfs-MDT0000 -o nosvc /mnt/test/mdt
-
+
<indexterm><primary>maintenance</primary><secondary>regenerating config logs</secondary></indexterm> Regenerating Lustre Configuration Logs If the Lustre file system configuration logs are in a state where @@ -221,7 +224,7 @@ mgs# lctl --device MGS llog_print fsname-OST0000 run, the configuration logs are re-generated as servers connect to the MGS.
-
+
<indexterm><primary>maintenance</primary><secondary>changing a NID</secondary></indexterm> Changing a Server NID In Lustre software release 2.3 or earlier, the tunefs.lustre @@ -287,7 +290,7 @@ Changing a Server NID The previous configuration log is backed up on the MGS disk with the suffix '.bak'.
-
+
<indexterm> <primary>maintenance</primary> <secondary>Clearing a config</secondary> @@ -338,7 +341,7 @@ Changing a Server NID
-
+
<indexterm> <primary>maintenance</primary> <secondary>adding an MDT</secondary> @@ -391,7 +394,7 @@ client# lfs mkdir -c 4 /mnt/testfs/new_directory_striped_across_4_mdts </listitem> </orderedlist> </section> - <section xml:id="dbdoclet.adding_new_ost"> + <section xml:id="lustremaint.adding_new_ost"> <title><indexterm><primary>maintenance</primary><secondary>adding a OST</secondary></indexterm> Adding a New OST to a Lustre File System A new OST can be added to existing Lustre file system on either @@ -435,7 +438,7 @@ oss# mount -t lustre /dev/sda /mnt/testfs/ost12
-
+
<indexterm><primary>maintenance</primary><secondary>restoring an OST</secondary></indexterm> <indexterm><primary>maintenance</primary><secondary>removing an OST</secondary></indexterm> Removing and Restoring MDTs and OSTs @@ -477,7 +480,7 @@ Removing and Restoring MDTs and OSTs desire to continue using the filesystem before it is repaired. -
+
<indexterm><primary>maintenance</primary><secondary>removing an MDT</secondary></indexterm>Removing an MDT from the File System If the MDT is permanently inaccessible, lfs rm_entry {directory} can be used to delete the @@ -499,7 +502,7 @@ client$ lfs getstripe --mdt-index /mnt/lustre/local_dir0 The lfs getstripe --mdt-index command returns the index of the MDT that is serving the given directory.
-
+
<indexterm><primary>maintenance</primary></indexterm> <indexterm><primary>maintenance</primary><secondary>inactive MDTs</secondary></indexterm>Working with Inactive MDTs @@ -507,7 +510,7 @@ client$ lfs getstripe --mdt-index /mnt/lustre/local_dir0 the MDT is activated again. Clients accessing an inactive MDT will receive an EIO error.
-
+
<indexterm> <primary>maintenance</primary> <secondary>removing an OST</secondary> @@ -616,14 +619,14 @@ client$ lfs getstripe --mdt-index /mnt/lustre/local_dir0 <note><para>A deactivated OST still appears in the file system configuration, though a replacement OST can be created using the <literal>mkfs.lustre --replace</literal> option, see - <xref linkend="section_restore_ost"/>. + <xref linkend="lustremaint.restore_ost"/>. </para></note> </listitem> </orderedlist> </listitem> </orderedlist> </section> - <section remap="h3" xml:id="section_ydg_pgt_tl"> + <section remap="h3" xml:id="lustremaint.ydg_pgt_tl"> <title><indexterm> <primary>maintenance</primary> <secondary>backing up OST config</secondary> @@ -659,7 +662,7 @@ oss# mount -t ldiskfs <replaceable>/dev/ost_device</replaceable> /mnt/ost</scree </listitem> </orderedlist> </section> - <section xml:id="section_restore_ost"> + <section xml:id="lustremaint.restore_ost"> <title><indexterm> <primary>maintenance</primary> <secondary>restoring OST config</secondary> @@ -731,7 +734,7 @@ oss0# dd if=/tmp/mountdata of=/mnt/ost/CONFIGS/mountdata bs=4 count=1 seek=5 ski </listitem> </orderedlist> </section> - <section xml:id="section_ucf_qgt_tl"> + <section xml:id="lustremaint.ucf_qgt_tl"> <title><indexterm> <primary>maintenance</primary> <secondary>reintroducing an OSTs</secondary> @@ -745,7 +748,7 @@ oss0# dd if=/tmp/mountdata of=/mnt/ost/CONFIGS/mountdata bs=4 count=1 seek=5 ski client# lctl set_param osc.<replaceable>fsname</replaceable>-OST<replaceable>number</replaceable>-*.active=1</screen></para> </section> </section> - <section xml:id="dbdoclet.50438199_77819"> + <section xml:id="lustremaint.abortRecovery"> <title><indexterm><primary>maintenance</primary><secondary>aborting recovery</secondary></indexterm> <indexterm><primary>backup</primary><secondary>aborting recovery</secondary></indexterm> Aborting Recovery @@ -754,7 +757,7 @@ Aborting Recovery The recovery process is blocked until all OSTs are available.
-
+
<indexterm><primary>maintenance</primary><secondary>identifying OST host</secondary></indexterm> Determining Which Machine is Serving an OST In the course of administering a Lustre file system, you may need to determine which @@ -775,7 +778,7 @@ osc.testfs-OST0002-osc-f1579000.ost_conn_uuid=192.168.20.1@tcp osc.testfs-OST0003-osc-f1579000.ost_conn_uuid=192.168.20.1@tcp osc.testfs-OST0004-osc-f1579000.ost_conn_uuid=192.168.20.1@tcp
-
+
<indexterm><primary>maintenance</primary><secondary>changing failover node address</secondary></indexterm> Changing the Address of a Failover Node To change the address of a failover node (e.g, to use node X instead of node Y), run @@ -788,13 +791,13 @@ Changing the Address of a Failover Node --failnode options, see .
-
+
<indexterm><primary>maintenance</primary><secondary>separate a combined MGS/MDT</secondary></indexterm> Separate a combined MGS/MDT These instructions assume the MGS node will be the same as the MDS node. For instructions on how to move MGS to a different node, see - . + . These instructions are for doing the split without shutting down other servers and clients. @@ -814,7 +817,7 @@ Changing the Address of a Failover Node mds# cp -r /mdt_mount_point/CONFIGS/filesystem_name-* /mgs_mount_point/CONFIGS/. mds# umount /mgs_mount_point mds# umount /mdt_mount_point - See for alternative method. + See for alternative method. Start the MGS. diff --git a/LustreOperations.xml b/LustreOperations.xml index 51daff3..55f4bc0 100644 --- a/LustreOperations.xml +++ b/LustreOperations.xml @@ -499,7 +499,7 @@ client# lfs mkdir –i The Lustre 2.8 DNE feature enables individual files in a given directory to store their metadata on separate MDTs (a striped directory) once additional MDTs have been added to the - filesystem, see . + filesystem, see . 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 @@ -924,7 +924,7 @@ tune2fs [-m reserved_blocks_percent] /dev/ or . For more information on removing a MDT, see - . + .
diff --git a/LustreTroubleshooting.xml b/LustreTroubleshooting.xml index 566937b..69cffe4 100644 --- a/LustreTroubleshooting.xml +++ b/LustreTroubleshooting.xml @@ -541,7 +541,7 @@ filesystem_summary: 21.6T 17.8T 3.2T 85% /myth <para>To address this issue, you can expand the disk space on the OST, or use the <literal>lfs_migrate</literal> command to migrate (move) files to a less full OST. For details on both of these options - see <xref linkend="dbdoclet.adding_new_ost" /></para> + see <xref linkend="lustremaint.adding_new_ost" /></para> <para condition='l26'>In some cases, there may be processes holding files open that are consuming a significant amount of space (e.g. runaway process writing lots of data to an open file that has been diff --git a/ManagingFileSystemIO.xml b/ManagingFileSystemIO.xml index 7d0f9be..c80d3dd 100644 --- a/ManagingFileSystemIO.xml +++ b/ManagingFileSystemIO.xml @@ -106,7 +106,7 @@ mds# lctl set_param osp.<replaceable>fsname</replaceable>-OST<replaceable>nnnn</ OST(s) to new OST(s), the data must be migrated (copied) to the new location. The simplest way to do this is to use the <literal>lfs_migrate</literal> command, as described in - <xref linkend="dbdoclet.adding_new_ost" />.</para> + <xref linkend="lustremaint.adding_new_ost" />.</para> </section> <section remap="h3"> <title> diff --git a/ManagingStripingFreeSpace.xml b/ManagingStripingFreeSpace.xml index 6a10225..55f7ae2 100644 --- a/ManagingStripingFreeSpace.xml +++ b/ManagingStripingFreeSpace.xml @@ -377,7 +377,7 @@ osc.lustre-OST0002-osc.ost_conn_uuid=192.168.20.1@tcp</screen></para> different MDT. To identify on which MDT a given subdirectory is located, pass the <literal>getstripe [--mdt-index|-M]</literal> parameters to <literal>lfs</literal>. An example of this command is - provided in the section <xref linkend="dbdoclet.rmremotedir"/>.</para> + provided in the section <xref linkend="lustremaint.rmremotedir"/>.</para> </section> </section> <section xml:id="pfl" condition='l2A'> diff --git a/SettingUpLustreSystem.xml b/SettingUpLustreSystem.xml index 773f82a..4585367 100644 --- a/SettingUpLustreSystem.xml +++ b/SettingUpLustreSystem.xml @@ -98,7 +98,7 @@ <para condition='l24'>If multiple MDTs are going to be present in the system, each MDT should be specified for the anticipated usage and load. For details on how to add additional MDTs to the filesystem, see - <xref linkend="dbdoclet.adding_new_mdt"/>.</para> + <xref linkend="lustremaint.adding_new_mdt"/>.</para> <warning condition='l24'><para>MDT0 contains the root of the Lustre file system. If MDT0 is unavailable for any reason, the file system cannot be used.</para></warning> @@ -299,7 +299,7 @@ it is possible to increase the total number of inodes of a Lustre filesystem, as well as increasing the aggregate metadata performance, by configuring additional MDTs into the filesystem, see - <xref linkend="dbdoclet.adding_new_mdt"/> for details. + <xref linkend="lustremaint.adding_new_mdt"/> for details. </para> </note> </section> diff --git a/UserUtilities.xml b/UserUtilities.xml index 4fce6bb..9c19dfa 100644 --- a/UserUtilities.xml +++ b/UserUtilities.xml @@ -487,7 +487,7 @@ lfs help <para condition="l24">The <literal>--mdt-index</literal> prints the index of the MDT for a given directory. See - <xref linkend="dbdoclet.rmremotedir" />.</para> + <xref linkend="lustremaint.rmremotedir" />.</para> </entry> </row> <row> -- 1.8.3.1