From 146caa4a78c2c5db32595556f8915bf77b32c2c9 Mon Sep 17 00:00:00 2001 From: Richard Henwood Date: Fri, 20 May 2011 13:39:59 -0500 Subject: [PATCH] FIX: validation, ulink -> link --- InstallingLustreFromSourceCode.xml | 20 +++++++-------- LustreDebugging.xml | 52 +++++++++++++++++++++----------------- 2 files changed, 39 insertions(+), 33 deletions(-) diff --git a/InstallingLustreFromSourceCode.xml b/InstallingLustreFromSourceCode.xml index 6df8f70..ca11fbd 100644 --- a/InstallingLustreFromSourceCode.xml +++ b/InstallingLustreFromSourceCode.xml @@ -20,7 +20,7 @@
29.1 Overview and Prerequisites - Lustre can be installed from either pre-built binary packages (RPMs) or freely-available source code. Installing from the package release is recommended unless you need to customize the Lustre server kernel or will be using an Linux kernel that has not been tested with Lustre. For a list of supported Linux distributions and architectures, see the topic Lustre_2.0 on the Lustre wiki. The procedure for installing Lustre from RPMs is describe in Chapter 8. + Lustre can be installed from either pre-built binary packages (RPMs) or freely-available source code. Installing from the package release is recommended unless you need to customize the Lustre server kernel or will be using an Linux kernel that has not been tested with Lustre. For a list of supported Linux distributions and architectures, see the topic Lustre_2.0 on the Lustre wiki. The procedure for installing Lustre from RPMs is describe in . To install Lustre from source code, the following are required: @@ -46,7 +46,7 @@ - When using third-party network hardware with Lustre, the third-party modules (typically, the drivers) must be linked against the Linux kernel. The LNET modules in Lustre also need these references. To meet these requirements, a specific process must be followed to install and recompile Lustre. See Installing Lustre with a Third-Party Network Stack, for an example showing how to install Lustre 1.6.6 using the Myricom MX 1.2.7 driver. The same process can be used for other third-party network stacks. + When using third-party network hardware with Lustre, the third-party modules (typically, the drivers) must be linked against the Linux kernel. The LNET modules in Lustre also need these references. To meet these requirements, a specific process must be followed to install and recompile Lustre. See , for an example showing how to install Lustre 1.6.6 using the Myricom MX 1.2.7 driver. The same process can be used for other third-party network stacks.
@@ -90,10 +90,10 @@ For more information on these prerequisites, see: - Hardware requirements in Chapter 5. + Hardware requirements in . - Software and environmental requirements in Preparing to Install the Lustre Software + Software and environmental requirements in @@ -181,7 +181,7 @@ lustre-modules-1.6.5.1-\2.6.18_53.xx.xxel5_lustre.1.6.5.1.custom_20081021.i686.r lustre-source-1.6.5.1-\2.6.18_53.xx.xx.el5_lustre.1.6.5.1.custom_20081021.i686.rpm - If the steps to create the RPMs fail, contact Lustre Support by reporting a bug. See Reporting a Lustre Bug. + If the steps to create the RPMs fail, contact Lustre Support by reporting a bug. See . Several features and packages are available that extend the core functionality of Lustre. These features/packages can be enabled at the build time by issuing appropriate arguments to the configure command. For a list of these features and packages, run ./configure -help in the Lustre source tree. The configs/ directory of the kernel source contains the config files matching each the kernel version. Copy one to .config at the root of the kernel tree. @@ -193,12 +193,12 @@ lustre-source-1.6.5.1-\2.6.18_53.xx.xx.el5_lustre.1.6.5.1.custom_20081021.i686.r Example result: kernel-2.6.95.0.3.EL_lustre.1.6.5.1custom-1.i686.rpm - Step 3 is only valid for RedHat and SuSE kernels. If you are using a stock Linux kernel, you need to get a script to create the kernel RPM. + Step is only valid for RedHat and SuSE kernels. If you are using a stock Linux kernel, you need to get a script to create the kernel RPM. Install the Lustre packages. - Some Lustre packages are installed on servers (MDS and OSSs), and others are installed on Lustre clients. For guidance on where to install specific packages, see TABLE 8-1 that lists required packages and for each package and where to install it. Depending on the selected platform, not all of the packages listed in TABLE 8-1 need to be installed. + Some Lustre packages are installed on servers (MDS and OSSs), and others are installed on Lustre clients. For guidance on where to install specific packages, see that lists required packages and for each package and where to install it. Depending on the selected platform, not all of the packages listed in need to be installed. Running the patched server kernel on the clients is optional. It is not necessary unless the clients will be used for multiple purposes, for example, to run as a client and an OST. @@ -239,7 +239,7 @@ lustre-ldiskfs-<ver> Reboot the servers. - Once all the machines have rebooted, the next steps are to configure Lustre Networking (LNET) and the Lustre file system. See Configuring Lustre. + Once all the machines have rebooted, the next steps are to configure Lustre Networking (LNET) and the Lustre file system. See . @@ -254,7 +254,7 @@ lustre-ldiskfs-<ver> Install the necessary build tools. - GCC and related tools must be installed. For more information, see Required Software. + GCC and related tools must be installed. For more information, see . $ yum install rpm-build redhat-rpm-config $ mkdir -p rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS} $ echo '%_topdir %(echo $HOME)/rpmbuild' > .rpmmacros @@ -349,7 +349,7 @@ options lnet networks=mx0(myri0),tcp0(eth0) Start Lustre. - Once all the machines have rebooted, the next steps are to configure Lustre Networking (LNET) and the Lustre file system. See Chapter 10. + Once all the machines have rebooted, the next steps are to configure Lustre Networking (LNET) and the Lustre file system. See .
diff --git a/LustreDebugging.xml b/LustreDebugging.xml index ddf84bd..a6bee9c 100644 --- a/LustreDebugging.xml +++ b/LustreDebugging.xml @@ -43,18 +43,18 @@ - This tool is used with the debug_kernel option to manually dump the Lustre debugging log or post-process debugging logs that are dumped automatically. For more information about the lctl tool, see and . - Lustre subsystem asserts - A panic-style assertion (LBUG) in the kernel causes Lustre to dump the debug log to the file /tmp/lustre-log.<timestamp> where it can be retrieved after a reboot. For more information, see Viewing Error Messages. + Lustre subsystem asserts - A panic-style assertion (LBUG) in the kernel causes Lustre to dump the debug log to the file /tmp/lustre-log.<timestamp> where it can be retrieved after a reboot. For more information, see . - - lfs - - This utility provides access to the extended attributes (EAs) of a Lustre file (along with other information). For more inforamtion about lfs, see lfs. + + lfs + - This utility provides access to the extended attributes (EAs) of a Lustre file (along with other information). For more inforamtion about lfs, see .
28.1.2 External Debugging Tools - The tools described in this section are provided in the Linux kernel or are available at an external website. For information about using some of these tools for Lustre debugging, see Lustre Debugging Procedures and Lustre Debugging for Developers. + The tools described in this section are provided in the Linux kernel or are available at an external website. For information about using some of these tools for Lustre debugging, see and .
28.1.2.1 Tools for Administrators and Developers Some general debugging tools provided as a part of the standard Linux distro are: @@ -104,7 +104,7 @@ - leak_finder.pl + leak_finder.pl . This program provided with Lustre is useful for finding memory leaks in the code. @@ -466,7 +466,7 @@
28.2.2 Using the lctl Tool to View Debug Messages - The lctl tool allows debug messages to be filtered based on subsystems and message types to extract information useful for troubleshooting from a kernel debug log. For a command reference, see lctl. + The lctl tool allows debug messages to be filtered based on subsystems and message types to extract information useful for troubleshooting from a kernel debug log. For a command reference, see . You can use lctl to: @@ -731,7 +731,7 @@ lctl> debug_kernel [filename] - DEBUG_REQ + DEBUG_REQ @@ -741,7 +741,7 @@ lctl> debug_kernel [filename] - OBD_FAIL_CHECK + OBD_FAIL_CHECK @@ -751,7 +751,7 @@ lctl> debug_kernel [filename] - OBD_FAIL_TIMEOUT + OBD_FAIL_TIMEOUT @@ -761,7 +761,7 @@ lctl> debug_kernel [filename] - OBD_RACE + OBD_RACE @@ -771,7 +771,7 @@ lctl> debug_kernel [filename] - OBD_FAIL_ONCE + OBD_FAIL_ONCE @@ -781,7 +781,7 @@ lctl> debug_kernel [filename] - OBD_FAIL_RAND + OBD_FAIL_RAND @@ -801,7 +801,7 @@ lctl> debug_kernel [filename] - OBD_FAIL_SOME + OBD_FAIL_SOME @@ -832,25 +832,31 @@ lctl> debug_kernel [filename] Request history is accessed and controlled using the following /proc files under the service directory: + - req_buffer_history_len + req_buffer_history_len + Number of request buffers currently in the history + - req_buffer_history_max + req_buffer_history_max + Maximum number of request buffers to keep + - req_history + req_history + The request history @@ -884,7 +890,7 @@ lctl> debug_kernel [filename] - target NID + target NID @@ -894,7 +900,7 @@ lctl> debug_kernel [filename] - client ID + client ID @@ -903,9 +909,9 @@ lctl> debug_kernel [filename] - - xid - + + xid + rq_xid @@ -963,7 +969,7 @@ lctl> debug_kernel [filename] Then complete the following steps: - Dump the log into a user-specified log file using lctl (see Using the lctl Tool to View Debug Messages). + Dump the log into a user-specified log file using lctl (see ). Run the leak finder on the newly-created log dump: -- 1.8.3.1