<para>Download the Lustre I/O kit (<literal>lustre-iokit</literal>)from:
</para>
<para>
- <link xl:href="http://downloads.whamcloud.com/">http://downloads.whamcloud.com/</link>
+ <link xl:href="https://downloads.whamcloud.com/">https://downloads.whamcloud.com/</link>
</para>
</section>
</section>
<itemizedlist>
<listitem>
<para>
- <xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="dbdoclet.50438188_82389"/></para>
+ <xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="high_availability"/></para>
</listitem>
<listitem>
- <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="dbdoclet.50438188_92688"
+ <para><xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="failover_setup"
/></para>
</listitem>
<listitem>
- <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="section_tnq_kbr_xl"/></para>
+ <para><xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="administering_failover"/></para>
</listitem>
</itemizedlist>
<para>For an overview of failover functionality in a Lustre file system, see <xref
xmlns:xlink="http://www.w3.org/1999/xlink" linkend="understandingfailover"/>.</para>
- <section xml:id="dbdoclet.50438188_82389">
+ <section xml:id="high_availability">
<title><indexterm>
<primary>High availability</primary>
<see>failover</see>
<primary>failover</primary>
<secondary>power control device</secondary>
</indexterm>Selecting Power Equipment</title>
- <para>Failover in a Lustre file system requires the use of a remote power control (RPC)
- mechanism, which comes in different configurations. For example, Lustre server nodes may be
- equipped with IPMI/BMC devices that allow remote power control. In the past, software or
- even “sneakerware” has been used, but these are not recommended. For recommended devices,
- refer to the list of supported RPC devices on the website for the PowerMan cluster power
- management utility:</para>
+ <para>Failover in a Lustre file system requires the use of a remote
+ power control (RPC) mechanism, which comes in different configurations.
+ For example, Lustre server nodes may be equipped with IPMI/BMC devices
+ that allow remote power control. In the past, software or even
+ “sneakerware” has been used, but these are not recommended. For
+ recommended devices, refer to the list of supported RPC devices on the
+ website for the PowerMan cluster power management utility:</para>
<para><link xmlns:xlink="http://www.w3.org/1999/xlink"
- xlink:href="http://code.google.com/p/powerman/wiki/SupportedDevs"
- >http://code.google.com/p/powerman/wiki/SupportedDevs</link></para>
+ xlink:href="https://linux.die.net/man/7/powerman-devices">
+ https://linux.die.net/man/7/powerman-devices</link></para>
</section>
<section remap="h3">
<title><indexterm>
nodes and the risk of unrecoverable data corruption. A variety of power management tools
will work. Two packages that have been commonly used with the Lustre software are PowerMan
and Linux-HA (aka. STONITH ).</para>
- <para>The PowerMan cluster power management utility is used to control RPC devices from a
- central location. PowerMan provides native support for several RPC varieties and Expect-like
- configuration simplifies the addition of new devices. The latest versions of PowerMan are
+ <para>The PowerMan cluster power management utility is used to control
+ RPC devices from a central location. PowerMan provides native support
+ for several RPC varieties and Expect-like configuration simplifies
+ the addition of new devices. The latest versions of PowerMan are
available at: </para>
<para><link xmlns:xlink="http://www.w3.org/1999/xlink"
- xlink:href="http://code.google.com/p/powerman/"
- >http://code.google.com/p/powerman/</link></para>
+ xlink:href="https://github.com/chaos/powerman">
+ https://github.com/chaos/powerman</link></para>
<para>STONITH, or “Shoot The Other Node In The Head”, is a set of power management tools
provided with the Linux-HA package prior to Red Hat Enterprise Linux 6. Linux-HA has native
support for many power control devices, is extensible (uses Expect scripts to automate
up failover with Pacemaker, see:</para>
<itemizedlist>
<listitem>
- <para>Pacemaker Project website: <link xmlns:xlink="http://www.w3.org/1999/xlink"
- xlink:href="http://clusterlabs.org/"><link xlink:href="http://clusterlabs.org/"
- >http://clusterlabs.org/</link></link></para>
+ <para>Pacemaker Project website:
+ <link xmlns:xlink="http://www.w3.org/1999/xlink"
+ xlink:href="https://clusterlabs.org/">https://clusterlabs.org/
+ </link></para>
</listitem>
<listitem>
- <para>Article <emphasis role="italic">Using Pacemaker with a Lustre File
- System</emphasis>: <link xmlns:xlink="http://www.w3.org/1999/xlink"
- xlink:href="https://wiki.whamcloud.com/display/PUB/Using+Pacemaker+with+a+Lustre+File+System"
- ><link
- xlink:href="https://wiki.whamcloud.com/display/PUB/Using+Pacemaker+with+a+Lustre+File+System"
- >https://wiki.whamcloud.com/display/PUB/Using+Pacemaker+with+a+Lustre+File+System</link></link></para>
+ <para>Article
+ <emphasis role="italic">Using Pacemaker with a Lustre File System
+ </emphasis>:
+ <link xmlns:xlink="http://www.w3.org/1999/xlink"
+ xlink:href="https://wiki.whamcloud.com/display/PUB/Using+Pacemaker+with+a+Lustre+File+System">
+ https://wiki.whamcloud.com/display/PUB/Using+Pacemaker+with+a+Lustre+File+System</link></para>
</listitem>
</itemizedlist>
</section>
</section>
- <section xml:id="dbdoclet.50438188_92688">
+ <section xml:id="failover_setup">
<title><indexterm>
<primary>failover</primary>
<secondary>setup</secondary>
/dev/sdb</screen></para>
<para>More than two potential service nodes can be designated for a target. The target can then
be mounted on any of the designated service nodes.</para>
- <para>When HA is configured on a storage target, the Lustre software enables multi-mount
- protection (MMP) on that storage target. MMP prevents multiple nodes from simultaneously
- mounting and thus corrupting the data on the target. For more about MMP, see <xref
- xmlns:xlink="http://www.w3.org/1999/xlink" linkend="managingfailover"/>.</para>
+ <para>When HA is configured on a storage target, the Lustre software
+ enables multi-mount protection (MMP) on that storage target. MMP prevents
+ multiple nodes from simultaneously mounting and thus corrupting the data
+ on the target. For more about MMP, see
+ <xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="managingfailover"/>.</para>
<para>If the MGT has been formatted with multiple service nodes designated, this information
must be conveyed to the Lustre client in the mount command used to mount the file system. In
the example below, NIDs for two MGSs that have been designated as service nodes for the MGT
the client attempts to access data on a target, it will try the NID for each specified service
node until it connects to the target.</para>
</section>
- <section xml:id="section_tnq_kbr_xl">
+ <section xml:id="administering_failover">
<title>Administering Failover in a Lustre File System</title>
<para>For additional information about administering failover features in a Lustre file system, see:<itemizedlist>
<listitem>
- <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="dbdoclet.50438194_57420"
- /></para>
+ <para><xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="failover_ost" /></para>
</listitem>
<listitem>
- <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="dbdoclet.50438194_41817"
+ <para><xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="failover_nids"
/></para>
</listitem>
<listitem>
- <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="lustremaint.ChangeAddrFailoverNode"
+ <para><xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="lustremaint.ChangeAddrFailoverNode"
/></para>
</listitem>
<listitem>
- <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="dbdoclet.50438219_75432"
+ <para><xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="mkfs.lustre"
/></para>
</listitem>
</itemizedlist></para>
(e2fsprogs is not needed with ZFS backend). In general, we recommend
to use the latest e2fsprogs version available on
<link xl:href="https://downloads.whamcloud.com/public/e2fsprogs/">
- http://downloads.whamcloud.com/public/e2fsprogs/</link>.</para>
+ https://downloads.whamcloud.com/public/e2fsprogs/</link>.</para>
<para>The ldiskfs OSD relies on the standard Linux quota to maintain
accounting information on disk. As a consequence, the Linux kernel
running on the Lustre servers using ldiskfs backend must have
to interact with Lustre software features, such as setting or checking
file striping or per-target free space. For more details, see
<xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="dbdoclet.50438206_94597" />.</para>
+ linkend="userutilities.lfs" />.</para>
</glossdef>
</glossentry>
<glossentry xml:id="lfsck">
</tip>
</partintro>
- <xi:include href="LustreMonitoring.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="LustreOperations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="LustreMaintenance.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ManagingLNet.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="LNetMultiRail.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="UpgradingLustre.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="BackupAndRestore.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ManagingStripingFreeSpace.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="DataOnMDT.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="LazySizeOnMDT.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="FileLevelRedundancy.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ManagingFileSystemIO.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ManagingFailover.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ConfiguringQuotas.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="LustreHSM.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="PersistentClientCache.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="LustreNodemap.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="LustreSharedSecretKey.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ManagingSecurity.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ZFSSnapshots.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="LustreMonitoring.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="LustreOperations.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="LustreMaintenance.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ManagingLNet.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="LNetMultiRail.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="UpgradingLustre.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="BackupAndRestore.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ManagingStripingFreeSpace.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="DataOnMDT.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="LazySizeOnMDT.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="FileLevelRedundancy.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ManagingFileSystemIO.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ManagingFailover.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ConfiguringQuotas.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="LustreHSM.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="PersistentClientCache.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="LustreNodemap.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="LustreSharedSecretKey.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ManagingSecurity.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ZFSSnapshots.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
</part>
<!--
</itemizedlist>
</partintro>
-
- <xi:include href="InstallOverview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="SettingUpLustreSystem.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ConfiguringStorage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="SettingUpBonding.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="InstallingLustre.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ConfiguringLNet.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ConfiguringLustre.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="ConfiguringFailover.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
-
+ <xi:include href="InstallOverview.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="SettingUpLustreSystem.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ConfiguringStorage.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="SettingUpBonding.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="InstallingLustre.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ConfiguringLNet.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ConfiguringLustre.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="ConfiguringFailover.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
</part>
<!--
</partintro>
- <xi:include href="LNetSelfTest.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="BenchmarkingTests.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="LustreTuning.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
-
-
-
+ <xi:include href="LNetSelfTest.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="BenchmarkingTests.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="LustreTuning.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
</part>
<!--
<itemizedlist>
<listitem>
<para>
- <xref linkend='understandinglustre' endterm='understandinglustre.title'/>
+ <xref linkend='understandinglustre'
+ endterm='understandinglustre.title'/>
</para>
</listitem>
<listitem>
<para>
- <xref linkend='understandinglustrenetworking' endterm='understandinglustrenetworking.title'/>
+ <xref linkend='understandinglustrenetworking'
+ endterm='understandinglustrenetworking.title'/>
</para>
</listitem>
<listitem>
<para>
- <xref linkend='understandingfailover' endterm='understandingfailover.title'/>
+ <xref linkend='understandingfailover'
+ endterm='understandingfailover.title'/>
</para>
</listitem>
</itemizedlist>
</partintro>
- <xi:include href="UnderstandingLustre.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
- <xi:include href="UnderstandingLustreNetworking.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="UnderstandingFailover.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
-
+ <xi:include href="UnderstandingLustre.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="UnderstandingLustreNetworking.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="UnderstandingFailover.xml"
+ xmlns:xi="http://www.w3.org/2001/XInclude" />
</part>
<!--
<itemizedlist>
<listitem>
<para>
- <xref linkend="dbdoclet.50438261_99193" />
+ <xref linkend="preparing_installation" />
</para>
</listitem>
<listitem>
<para>For hardware and system requirements and hardware configuration
information, see
<xref linkend="settinguplustresystem" />.</para>
- <section xml:id="dbdoclet.50438261_99193">
+ <section xml:id="preparing_installation">
<title>
<indexterm>
<primary>installing</primary>
<emphasis role="bold">
<emphasis role="italic">Lustre server packages</emphasis>
</emphasis>. The required packages for Lustre 2.9 EL7 servers are
- listed in the table below, where
+ listed in the table below, where
<replaceable>ver</replaceable> refers to the Lustre release and
- kernel version (e.g., 2.9.0-1.el7) and
+ kernel version (e.g., 2.9.0-1.el7) and
<replaceable>arch</replaceable> refers to the processor architecture
(e.g., x86_64). These packages are available in the
<link xl:href="https://wiki.whamcloud.com/display/PUB/Lustre+Releases">
Lustre Releases</link> repository, and may differ depending on
- your distro and version.</para>
+ your distro and version.</para>
<para>
- <table frame="all" xml:id="table_cnh_5m3_gk">
+ <table frame="all" xml:id="table.installed_server_pkg">
<title>Packages Installed on Lustre Servers</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="1.18*" />
<link xl:href="https://wiki.whamcloud.com/display/PUB/Lustre+Releases">
Lustre Releases</link> repository.</para>
<para>
- <table frame="all" xml:id="table_j3r_ym3_gk">
+ <table frame="all" xml:id="table.installed_client_pkg">
<title>Packages Installed on Lustre Clients</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="1*" />
see
<xref xmlns:xlink="http://www.w3.org/1999/xlink"
linkend="understandinglustrenetworking" />.</para>
- <table frame="all" xml:id="table_bkx_dn3_gk">
+ <table frame="all" xml:id="supported_network_types">
<title>Network Types Supported by Lustre LNDs</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="1*" />
<emphasis role="italic">High availability software</emphasis>
</emphasis>. If needed, install third party high-availability
software. For more information, see
- <xref linkend="dbdoclet.50438188_92688" />.</para>
+ <xref linkend="failover_setup" />.</para>
</listitem>
<listitem>
<para>
timestamps. We recommend that you use Network Time Protocol (NTP) to
keep client and server clocks in sync with each other. For more
information about NTP, see:
- <link xl:href="http://www.ntp.org/">http://www.ntp.org</link>.</para>
+ <link xl:href="https://www.ntp.org/">https://www.ntp.org</link>.</para>
</listitem>
<listitem>
<para>
<listitem>
<para>For software and environmental requirements, see the section
<xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="dbdoclet.50438261_99193" />above.</para>
+ linkend="preparing_installation" />above.</para>
</listitem>
</itemizedlist>
</listitem>
<link xl:href="https://wiki.whamcloud.com/display/PUB/Lustre+Releases">
Lustre Releases</link> repository. See
<xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="table_cnh_5m3_gk" />for a list of required packages.</para>
+ linkend="table.installed_server_pkg" />for a list of required packages.
+ </para>
</listitem>
<listitem xml:id="dbdoclet.50438261_88296">
<para>Install the Lustre server and
<link xl:href="https://wiki.whamcloud.com/display/PUB/Lustre+Releases">
Lustre Releases</link> repository. See
<xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="table_j3r_ym3_gk" />for a list of required packages.</para>
+ linkend="table.installed_client_pkg" />for a list of required packages.
+ </para>
</listitem>
<listitem>
<para>Install the Lustre client packages on all Lustre clients.
configuration, as are user-defined interface-section policies.</para>
<para>The following link contains a detailed high-level design for the
feature:
- <link xl:href="http://wiki.lustre.org/images/b/bb/Multi-Rail_High-Level_Design_20150119.pdf">
+ <link xl:href="https://wiki.lustre.org/images/b/bb/Multi-Rail_High-Level_Design_20150119.pdf">
Multi-Rail High-Level Design</link></para>
</section>
<section xml:id="dbdoclet.mrconfiguring">
<para>
<literal>
<replaceable>lfs</replaceable>
- </literal> - This utility provides access to the extended attributes (EAs) of a Lustre
- file (along with other information). For more information about lfs, see <xref
- linkend="dbdoclet.50438206_94597"/>.</para>
+ </literal> - This utility provides access to the layout of
+ of a Lustre file, along with other information relevant to users.
+ For more information about lfs, see <xref
+ linkend="userutilities.lfs"/>.</para>
</listitem>
</itemizedlist>
</section>
<para>The following logging and data collection tools can be used to collect information for debugging Lustre kernel issues:</para>
<itemizedlist>
<listitem>
- <para><emphasis role="bold">
- <literal>kdump</literal>
- </emphasis> . A Linux kernel crash utility useful for debugging a system running Red Hat Enterprise Linux. For more information about <literal>kdump</literal>, see the Red Hat knowledge base article <link xl:href="http://kbase.redhat.com/faq/docs/DOC-6039">How do I configure kexec/kdump on Red Hat Enterprise Linux 5?</link>. To download <literal>kdump</literal>, go to the <link xl:href="http://fedoraproject.org/wiki/SystemConfig/kdump#Download">Fedora Project Download</link> site.</para>
+ <para><emphasis role="bold"><literal>kdump</literal></emphasis>.
+ A Linux kernel crash utility useful for debugging a system running
+ Red Hat Enterprise Linux. For more information about
+ <literal>kdump</literal>, see the Red Hat knowledge base article
+ <link xl:href="https://access.redhat.com/solutions/6038">How to
+ troubleshoot kernel crashes, hangs, or reboots with kdump on
+ Red Hat Enterprise Linux</link>. To download
+ <literal>kdump</literal>, install the RPM package via
+ <literal>yum install kexec-tools</literal>.
+ </para>
</listitem>
<listitem>
- <para><emphasis role="bold">
- <literal>netconsole</literal>
- </emphasis>. Enables kernel-level network logging over UDP. A system requires (SysRq) allows users to collect relevant data through <literal>netconsole</literal>.</para>
+ <para><emphasis role="bold"><literal>netconsole</literal></emphasis>.
+ Enables kernel-level network logging over UDP. A system requires
+ (SysRq) allows users to collect relevant data through
+ <literal>netconsole</literal>.</para>
</listitem>
<listitem>
- <para><emphasis role="bold">
- <literal>netdump</literal>
- </emphasis>. A crash dump utility from Red Hat that allows memory images to be dumped
- over a network to a central server for analysis. The <literal>netdump</literal>
- utility was replaced by <literal>kdump</literal> in Red Hat Enterprise Linux 5. For
- more information about <literal>netdump</literal>, see <link
- xl:href="http://www.redhat.com/support/wpapers/redhat/netdump/">Red Hat, Inc.'s
- Network Console and Crash Dump Facility</link>.</para>
+ <para><emphasis><literal>wireshark</literal> </emphasis>. A network
+ packet inspection tool that allows debugging of information that was
+ sent between the various Lustre nodes. This tool is built on top of
+ <literal>tcpdump</literal> and can read packet dumps generated by
+ it. There are plug-ins available to dissassemble the LNet and
+ Lustre protocols. They are included with
+ <literal>wireshark</literal> since version 2.6.0. See also the
+ <link xl:href="https://www.wireshark.org/">Wireshark Website</link>
+ for more details.</para>
</listitem>
- <listitem>
- <para><emphasis><literal>wireshark</literal> </emphasis> . A network
- packet inspection tool that allows debugging of information that was
- sent between the various Lustre nodes. This tool is built on top of
- <literal>tcpdump</literal> and can read packet dumps generated by
- it. There are plug-ins available to dissassemble the LNet and
- Lustre protocols. They are located within the <link
- xl:href="http://git.whamcloud.com/">Lustre git repository</link>
- under <literal>lustre/contrib/wireshark/</literal>. Installation
- instruction are included in that directory. See also <link
- xl:href="http://www.wireshark.org/">Wireshark Website</link> for
- more details.</para>
- </listitem>
</itemizedlist>
</section>
<section remap="h4">
<para>A virtual machine is often used to create an isolated development and test environment. Some commonly-used virtual machines are:</para>
<itemizedlist>
<listitem>
- <para><emphasis role="bold">VirtualBox Open Source Edition</emphasis> . Provides enterprise-class virtualization capability for all major platforms and is available free at <link xl:href="http://www.sun.com/software/products/virtualbox/get.jsp?intcmp=2945">Get Sun VirtualBox</link>.</para>
+ <para>
+ <emphasis role="bold">VirtualBox Open Source Edition</emphasis>.
+ Provides enterprise-class virtualization capability for all major
+ platforms and is available free at
+ <link xl:href="https://www.virtualbox.org/wiki/Downloads">
+ https://www.virtualbox.org/wiki/Downloads</link>.</para>
</listitem>
<listitem>
- <para><emphasis role="bold">VMware Server</emphasis> . Virtualization platform available as free introductory software at <link xl:href="http://downloads.vmware.com/d/info/datacenter_downloads/vmware_server/2_0">Download VMware Server</link>.</para>
+ <para><emphasis role="bold">VMware Server</emphasis>.
+ Virtualization platform available as free introductory software at
+ <link xl:href="https://my.vmware.com/web/vmware/downloads/">
+ https://my.vmware.com/web/vmware/downloads/</link>.</para>
</listitem>
<listitem>
- <para><emphasis role="bold">Xen</emphasis> . A para-virtualized environment with virtualization capabilities similar to VMware Server and Virtual Box. However, Xen allows the use of modified kernels to provide near-native performance and the ability to emulate shared storage. For more information, go to <link xl:href="http://xen.org/">xen.org</link>.</para>
+ <para><emphasis role="bold">Xen</emphasis>. A para-virtualized
+ environment with virtualization capabilities similar to VMware
+ Server and Virtual Box. However, Xen allows the use of modified
+ kernels to provide near-native performance and the ability to
+ emulate shared storage. For more information, go to
+ <link xl:href="https://xen.org/">https://xen.org/</link>.</para>
</listitem>
</itemizedlist>
<para>A variety of debuggers and analysis tools are available including:</para>
<listitem>
<para><emphasis role="bold">
<literal>kgdb</literal>
- </emphasis> . The Linux Kernel Source Level Debugger kgdb is used in conjunction with the GNU Debugger <literal>gdb</literal> for debugging the Linux kernel. For more information about using <literal>kgdb</literal> with <literal>gdb</literal>, see <link xl:href="http://www.linuxtopia.org/online_books/redhat_linux_debugging_with_gdb/running.html">Chapter 6. Running Programs Under gdb</link> in the <emphasis>Red Hat Linux 4 Debugging with GDB</emphasis> guide.</para>
+ </emphasis> . The Linux Kernel Source Level Debugger kgdb is
+ used in conjunction with the GNU Debugger <literal>gdb</literal>
+ for debugging the Linux kernel. For more information about using
+ <literal>kgdb</literal> with <literal>gdb</literal>, see
+ <link xl:href="https://www.linuxtopia.org/online_books/redhat_linux_debugging_with_gdb/running.html">
+ Chapter 6. Running Programs Under gdb</link> in the
+ <emphasis>Red Hat Linux 4 Debugging with GDB</emphasis> guide.
+ </para>
</listitem>
<listitem>
<para><emphasis role="bold">
</emphasis> . Used to analyze saved crash dump data when a system had panicked or locked up or appears unresponsive. For more information about using crash to analyze a crash dump, see:</para>
<itemizedlist>
<listitem>
- <para> Red Hat Magazine article: <link xl:href="http://magazine.redhat.com/2007/08/15/a-quick-overview-of-linux-kernel-crash-dump-analysis/">A quick overview of Linux kernel crash dump analysis</link></para>
- </listitem>
- <listitem>
- <para><link xl:href="http://people.redhat.com/anderson/crash_whitepaper/#EXAMPLES">Crash Usage: A Case Study</link> from the white paper <emphasis>Red Hat Crash Utility</emphasis> by David Anderson</para>
- </listitem>
- <listitem>
- <para> Kernel Trap forum entry: <link xl:href="http://kerneltrap.org/node/5758">Linux: Kernel Crash Dumps</link></para>
- </listitem>
- <listitem>
- <para> White paper: <link xl:href="http://www.google.com/url?sa=t&source=web&ct=res&cd=8&ved=0CCUQFjAH&url=http%3A%2F%2Fwww.kernel.sg%2Fpapers%2Fcrash-dump-analysis.pdf&rct=j&q=redhat+crash+dump&ei=6aQBS-ifK4T8tAPcjdiHCw&usg=AFQjCNEk03E3GDtAsawG3gfpwc1gGNELAg">A Quick Overview of Linux Kernel Crash Dump Analysis</link></para>
+ <para> Overview on how to use crash by the author:
+ <link xl:href="https://crash-utility.github.io/crash_whitepaper.html">
+ White Paper: Red Hat Crash Utility</link>
+ </para>
</listitem>
</itemizedlist>
</listitem>
<primary>monitoring</primary>
<secondary>Lustre Monitoring Tool</secondary>
</indexterm> Lustre Monitoring Tool (LMT)</title>
- <para>The Lustre Monitoring Tool (LMT) is a Python-based, distributed system that provides a
- <literal>top</literal>-like display of activity on server-side nodes (MDS, OSS and portals
- routers) on one or more Lustre file systems. It does not provide support for monitoring
- clients. For more information on LMT, including the setup procedure, see:</para>
- <para><link xl:href="http://code.google.com/p/lmt/"
- >https://github.com/chaos/lmt/wiki</link></para>
- <para>LMT questions can be directed to:</para>
- <para><link xl:href="mailto:lmt-discuss@googlegroups.com">lmt-discuss@googlegroups.com</link></para>
+ <para>The Lustre Monitoring Tool (LMT) is a Python-based, distributed
+ system that provides a <literal>top</literal>-like display of activity
+ on server-side nodes (MDS, OSS and portals routers) on one or more
+ Lustre file systems. It does not provide support for monitoring
+ clients. For more information on LMT, including the setup procedure,
+ see:</para>
+ <para><link xl:href="https://github.com/chaos/lmt/wiki">
+ https://github.com/chaos/lmt/wiki</link></para>
</section>
<section xml:id="dbdoclet.50438273_80593">
<title>
played back at a later time. It can also be converted to a format suitable for
plotting.</para>
<para>For more information about <literal>CollectL</literal>, see:</para>
- <para><link xl:href="http://collectl.sourceforge.net">http://collectl.sourceforge.net</link></para>
+ <para><link xl:href="http://collectl.sourceforge.net">
+ http://collectl.sourceforge.net</link></para>
<para>Lustre-specific documentation is also available. See:</para>
- <para><link xl:href="http://collectl.sourceforge.net/Tutorial-Lustre.html">http://collectl.sourceforge.net/Tutorial-Lustre.html</link></para>
+ <para><link xl:href="http://collectl.sourceforge.net/Tutorial-Lustre.html">
+ http://collectl.sourceforge.net/Tutorial-Lustre.html</link></para>
</section>
<section xml:id="dbdoclet.50438273_44185">
<title><indexterm><primary>monitoring</primary><secondary>additional tools</secondary></indexterm>
always be safely specified.</para>
</note>
</section>
- <section xml:id="dbdoclet.50438194_57420">
+ <section xml:id="failover_ost">
<title>
<indexterm>
<primary>operations</primary>
</section>
</section>
</section>
- <section xml:id="dbdoclet.50438194_41817">
+ <section xml:id="failover_nids">
<title>
<indexterm>
<primary>operations</primary>
<note>
<para>To find the Lustre file from a disk LBA, follow the steps listed in
the document at this URL:
- <link xl:href="http://smartmontools.sourceforge.net/badblockhowto.html">
- http://smartmontools.sourceforge.net/badblockhowto.html</link>. Then,
+ <link xl:href="https://www.smartmontools.org/wiki/BadBlockHowto">
+ https://www.smartmontools.org/wiki/BadBlockHowto</link>. Then,
follow the steps above to resolve the Lustre filename.</para>
</note>
</section>
<xref linkend="metadatereplay"/>. For information on recovering from a
corrupt file system, see <xref linkend="commitonshare"/>. For
information on resolving orphaned objects, a common issue after recovery,
- see <xref linkend="dbdoclet.50438225_13916"/>. For information on
+ see <xref linkend="orphan_objects"/>. For information on
imperative recovery see <xref linkend="imperativerecovery"/>
</para>
<section remap="h3">
</listitem>
<listitem>
<para>Submit a ticket to the <link xmlns:xlink="http://www.w3.org/1999/xlink"
- xlink:href="https://jira.whamcloud.com/secure/Dashboard.jspa">Jira</link><abbrev><superscript>*</superscript></abbrev>
+ xlink:href="https://jira.whamcloud.com/">Jira</link>
+ <abbrev><superscript>*</superscript></abbrev>
bug tracking and project management tool used for the Lustre project.
If you are a first-time user, you'll need to open an account by
clicking on <emphasis role="bold">Sign up</emphasis> on the
</caution>
<para>To create a new pool, run:</para>
<screen>
-mgs# lctl pool_new
-<replaceable>fsname</replaceable>.
-<replaceable>poolname</replaceable>
+mgs# lctl pool_new <replaceable>fsname</replaceable>.<replaceable>poolname</replaceable>
</screen>
<note>
<para>The pool name is an ASCII string up to 15 characters.</para>
</note>
<para>To add the named OST to a pool, run:</para>
<screen>
-mgs# lctl pool_add
-<replaceable>fsname</replaceable>.
-<replaceable>poolname</replaceable>
-<replaceable>ost_list</replaceable>
+mgs# lctl pool_add <replaceable>fsname</replaceable>.<replaceable>poolname</replaceable> <replaceable>ost_list</replaceable>
</screen>
<para>Where:</para>
<itemizedlist>
finer-grained permissions to this model, allowing for more complicated
permission schemes. For a detailed explanation of ACLs on a Linux
operating system, refer to the SUSE Labs article
- <link xl:href="http://wiki.lustre.org/images/5/57/PosixAccessControlInLinux.pdf">
+ <link xl:href="https://www.usenix.org/legacyurl/posix-access-control-lists-linux">
Posix Access Control Lists on Linux</link>.</para>
<para>We have implemented ACLs according to this model. The Lustre
software works with the standard Linux ACL tools, setfacl, getfacl, and
<preface xmlns="http://docbook.org/ns/docbook"
xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US">
<title>Preface</title>
- <para>The <emphasis role="italic">Lustre<superscript>*</superscript>Software Release 2.x
- Operations Manual</emphasis> provides detailed information and procedures to install,
- configure and tune a Lustre file system. The manual covers topics such as failover, quotas,
- striping, and bonding. This manual also contains troubleshooting information and tips to improve
+ <para>The <emphasis role="italic">Lustre<superscript>*</superscript>Software
+ Release 2.x Operations Manual</emphasis> provides detailed information and
+ procedures to install, configure and tune a Lustre file system. The manual
+ covers topics such as failover, quotas, striping, and bonding. This manual
+ also contains troubleshooting information and tips to improve
the operation and performance of a Lustre file system.</para>
<section remap="h2">
<title>About this Document</title>
<para>This document is maintained by Whamcloud in Docbook format. The
canonical version is available at
- <link xl:href="http://wiki.whamcloud.com/display/PUB/Documentation">http://wiki.whamcloud.com/display/PUB/Documentation</link>. </para>
+ <link xl:href="https://wiki.whamcloud.com/display/PUB/Documentation">
+ https://wiki.whamcloud.com/display/PUB/Documentation
+ </link>. </para>
<section remap="h2">
<title>UNIX<superscript>*</superscript> Commands</title>
- <para>This document may not contain information about basic UNIX<superscript>*</superscript>
- operating system commands and procedures such as shutting down the system, booting the
- system, and configuring devices. Refer to the following for this information:</para>
+ <para>This document does not contain information about basic
+ UNIX<superscript>*</superscript> operating system commands and
+ procedures such as shutting down the system, booting the system, and
+ configuring devices. Refer to the following for this information:</para>
<itemizedlist>
<listitem>
- <para> Software documentation that you received with your system</para>
+ <para>Software documentation that you received with your system</para>
</listitem>
<listitem>
- <para> Red Hat<superscript>*</superscript> Enterprise Linux<superscript>*</superscript>
- documentation, which is at: <link xl:href="http://docs.redhat.com/docs/en-US/index.html"
- >http://docs.redhat.com/docs/en-US/index.html</link></para>
- <note><para> The Lustre client module is available for many different Linux<superscript>*</superscript>
- versions and distributions. The Red Hat Enterprise Linux distribution is the best
- supported and tested platform for Lustre servers. </para></note>
+ <para>Red Hat<superscript>*</superscript> Enterprise
+ Linux<superscript>*</superscript> documentation, which is at:
+ <link xl:href="https://docs.redhat.com/docs/en-US/index.html">
+ https://docs.redhat.com/docs/en-US/index.html</link>
+ </para>
+ <note><para>The Lustre client module is available for many different
+ Linux<superscript>*</superscript> versions and distributions. The
+ Red Hat Enterprise Linux distribution is the best supported and
+ tested platform for Lustre servers.</para></note>
</listitem>
</itemizedlist>
</section>
</entry>
<entry>
<para> Online at <link
- xl:href="http://wiki.whamcloud.com/display/PUB/Documentation"
- >http://wiki.whamcloud.com/display/PUB/Documentation</link></para>
+ xl:href="https://wiki.whamcloud.com/display/PUB/Documentation"
+ >https://wiki.whamcloud.com/display/PUB/Documentation</link></para>
</entry>
</row>
<row>
</entry>
<entry>
<para> Online at <link
- xl:href="http://wiki.whamcloud.com/display/PUB/Documentation"
- >http://wiki.whamcloud.com/display/PUB/Documentation</link></para>
+ xl:href="https://wiki.whamcloud.com/display/PUB/Documentation"
+ >https://wiki.whamcloud.com/display/PUB/Documentation</link></para>
</entry>
</row>
</tbody>
<para>These web sites provide additional resources:</para>
<itemizedlist>
<listitem>
- <link xl:href="http://wiki.whamcloud.com/display/PUB/Documentation">
- http://wiki.whamcloud.com/display/PUB/Documentation</link>
- <link xl:href="http://www.lustre.org">
- http://www.lustre.org</link></para>
+ <para> Documentation
+ <link xl:href="https://wiki.whamcloud.com/display/PUB/Documentation">
+ https://wiki.whamcloud.com/display/PUB/Documentation</link>
+ <link xl:href="https://www.lustre.org">https://www.lustre.org</link>
+ </para>
</listitem>
<listitem>
<para> Support <link xl:href="https://jira.whamcloud.com/">https://jira.whamcloud.com/</link></para>
</itemizedlist>
</section>
</section>
- <xi:include href="Revision.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="Revision.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
</preface>
<!--
vim:expandtab:shiftwidth=2:tabstop=8:
version=2.10.5
</screen>
</para></note>
-
+
<para>Only the latest revision of this document is made readily available
because changes are continually arriving. The current and latest revision
of this manual is available from links maintained at:
- <link xl:href="http://lustre.opensfs.org/documentation/">http://lustre.opensfs.org/documentation/</link>.
+ <link xl:href="http://lustre.opensfs.org/documentation/">
+ http://lustre.opensfs.org/documentation/</link>.
<revhistory>
<revision>
below includes detailed instructions for other configuration methods, instructions to use
DHCP with bonding, and other setup details. We strongly recommend you use this
website.</para>
- <para><link xl:href="http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding">http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding</link></para>
+ <para>
+ <link xl:href="https://wiki.linuxfoundation.org/networking/bonding">
+ http://www.linuxfoundation.org/networking/bonding</link></para>
</listitem>
<listitem>
<para>Check /proc/net/bonding to determine status on bonding. There should be a file there for each bond interface.</para>
<literal>documentation/networking/bonding.txt</literal></para>
</listitem>
<listitem>
- <para><link xl:href="http://linux-ip.net/html/ether-bonding.html"
- >http://linux-ip.net/html/ether-bonding.html</link>.</para>
+ <para><link xl:href="http://linux-ip.net/html/ether-bonding.html">
+ http://linux-ip.net/html/ether-bonding.html</link>.</para>
</listitem>
<listitem>
- <para><link xl:href="http://www.sourceforge.net/projects/bonding"
- >http://www.sourceforge.net/projects/bonding</link>.</para>
- </listitem>
- <listitem>
- <para>Linux Foundation bonding website: <link
- xl:href="http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding"
- >http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding</link>. This
- is the most extensive reference and we highly recommend it. This website includes
- explanations of more complicated setups, including the use of DHCP with bonding.</para>
+ <para>Linux Foundation bonding website:
+ <link xl:href="https://www.linuxfoundation.org/networking/bonding">
+ https://www.linuxfoundation.org/networking/bonding</link>. This
+ is the most extensive reference and we highly recommend it. This
+ website includes explanations of more complicated setups, including
+ the use of DHCP with bonding.</para>
</listitem>
</itemizedlist>
</section>
<para><xref linkend="dbdoclet.50438219_63667"/></para>
</listitem>
<listitem>
- <para><xref linkend="dbdoclet.50438219_75432"/></para>
+ <para><xref linkend="mkfs.lustre"/></para>
</listitem>
<listitem>
- <para><xref linkend="dbdoclet.50438219_12635"/></para>
+ <para><xref linkend="mount.lustre"/></para>
</listitem>
<listitem>
<para><xref linkend="dbdoclet.50438219_82679"/></para>
<para><xref linkend="dbdoclet.50438219_51496"/></para>
</listitem>
<listitem>
- <para><xref linkend="dbdoclet.50438219_39574"/></para>
+ <para><xref linkend="tunefs.lustre"/></para>
</listitem>
<listitem>
<para><xref linkend="dbdoclet.50438219_99928"/></para>
</listitem>
</itemizedlist>
<section xml:id="dbdoclet.50438219_55923">
- <title><indexterm><primary>e2scan</primary></indexterm>
- e2scan</title>
+ <title><indexterm><primary>e2scan</primary></indexterm>e2scan</title>
<para>The e2scan utility is an ext2 file system-modified inode scan program. The e2scan program uses libext2fs to find inodes with ctime or mtime newer than a given time and prints out their pathname. Use e2scan to efficiently generate lists of files that have been modified. The e2scan tool is included in the e2fsprogs package, located at:</para>
- <para><link xl:href="http://downloads.whamcloud.com/public/e2fsprogs/latest/">http://downloads.whamcloud.com/public/e2fsprogs/latest/</link></para>
+ <para>
+ <link xl:href="https://downloads.whamcloud.com/public/e2fsprogs/latest/">
+ https://downloads.whamcloud.com/public/e2fsprogs/latest/</link></para>
<section remap="h5">
<title>Synopsis</title>
<screen>e2scan [options] [-f file] block_device</screen>
<title>See Also</title>
<itemizedlist>
<listitem>
- <para> <xref linkend="dbdoclet.50438219_75432"/> </para>
+ <para> <xref linkend="mkfs.lustre"/>
+ </para>
</listitem>
<listitem>
- <para> <xref linkend="dbdoclet.50438219_12635"/> </para>
+ <para> <xref linkend="mount.lustre"/>
+ </para>
</listitem>
<listitem>
<para> <xref linkend="dbdoclet.50438219_38274"/> </para>
</listitem>
<listitem>
- <para> <xref linkend="dbdoclet.50438206_94597"/> </para>
+ <para> <xref linkend="userutilities.lfs"/> </para>
</listitem>
</itemizedlist>
</section>
and is not accessed or modified by Lustre after that time.</para>
<para>The OST object ID (objid) may be useful in case of OST directory
corruption, though LFSCK can normally reconstruct the entire OST object
- directory tree, see <xref linkend="dbdoclet.lfsckadmin" /> for details.
+ directory tree, see <xref linkend="dbdoclet.lfsckadmin" /> for details.
The MDS FID can be useful to determine which MDS inode an OST object
is (or was) used by. The stripe index can be used in conjunction with
other OST objects to reconstruct the layout of a file even if the MDT
</section>
<section remap="h5">
<title>See Also</title>
- <para><xref linkend="dbdoclet.50438219_39574"/></para>
+ <para><xref linkend="tunefs.lustre"/></para>
</section>
</section>
<section xml:id="dbdoclet.50438219_23232">
</section>
<section remap="h5">
<title>See Also</title>
- <para><xref linkend="dbdoclet.50438206_94597"/></para>
+ <para><xref linkend="userutilities.lfs"/></para>
</section>
</section>
- <section xml:id="dbdoclet.50438219_75432">
+ <section xml:id="mkfs.lustre">
<title><indexterm><primary>mkfs.lustre</primary></indexterm>
mkfs.lustre</title>
<para>The <literal>mkfs.lustre</literal> utility formats a disk for a Lustre service.</para>
</entry>
</row>
<row>
- <entry nameend="c2" namest="c1"
- ><literal>--servicenode=<replaceable>nid,...</replaceable></literal></entry>
- <entry>Sets the NID(s) of all service nodes, including primary and failover partner
- service nodes. The <literal>--servicenode</literal> option cannot be used with
- <literal>--failnode</literal> option. See <xref
- xmlns:xlink="http://www.w3.org/1999/xlink" linkend="dbdoclet.50438188_92688"/> for
+ <entry nameend="c2" namest="c1">
+ <literal>--servicenode=<replaceable>nid,...</replaceable></literal>
+ </entry>
+ <entry>Sets the NID(s) of all service nodes, including primary
+ and failover partner service nodes. The
+ <literal>--servicenode</literal> option cannot be used with
+ <literal>--failnode</literal> option. See
+ <xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="failover_setup"/> for
more details.</entry>
</row>
<row>
<para>Sets the NID(s) of a failover service node for a primary server for a target.
The <literal>--failnode</literal> option cannot be used with
<literal>--servicenode</literal> option. See <xref
- xmlns:xlink="http://www.w3.org/1999/xlink" linkend="dbdoclet.50438188_92688"/>
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="failover_setup"/>
for more details.<note>
<para>When the <literal>--failnode</literal> option is used, certain
restrictions apply (see <xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="dbdoclet.50438188_92688"/>).</para>
+ linkend="failover_setup"/>).</para>
</note></para>
</entry>
</row>
<title>See Also</title>
<itemizedlist>
<listitem>
- <para><xref linkend="dbdoclet.50438219_75432"/>mkfs.lustre, </para>
+ <para>
+ <xref linkend="mkfs.lustre"/>
+ mkfs.lustre, </para>
</listitem>
<listitem>
- <para><xref linkend="dbdoclet.50438219_12635"/>mount.lustre, </para>
+ <para>
+ <xref linkend="mount.lustre"/>
+ mount.lustre, </para>
</listitem>
<listitem>
- <para><xref linkend="dbdoclet.50438206_94597"/>lfs</para>
+ <para><xref linkend="userutilities.lfs"/>lfs</para>
</listitem>
</itemizedlist>
</section>
</section>
- <section xml:id="dbdoclet.50438219_12635">
+ <section xml:id="mount.lustre">
<title><indexterm><primary>mount.lustre</primary></indexterm>
mount.lustre</title>
<para>The mount.lustre utility starts a Lustre client or target service.</para>
<title>See Also</title>
<itemizedlist>
<listitem>
- <para> <xref linkend="dbdoclet.50438219_75432"/></para>
+ <para><xref linkend="mkfs.lustre"/>
+ </para>
</listitem>
<listitem>
- <para> <xref linkend="dbdoclet.50438219_39574"/></para>
+ <para> <xref linkend="tunefs.lustre"/></para>
</listitem>
<listitem>
<para> <xref linkend="dbdoclet.50438219_38274"/></para>
</listitem>
<listitem>
- <para> <xref linkend="dbdoclet.50438206_94597"/></para>
+ <para> <xref linkend="userutilities.lfs"/></para>
</listitem>
</itemizedlist>
</section>
<screen>/proc/sys/lnet/stats</screen>
</section>
</section>
- <section xml:id="dbdoclet.50438219_39574">
+ <section xml:id="tunefs.lustre">
<title><indexterm><primary>tunefs.lustre</primary></indexterm>
tunefs.lustre</title>
<para>The tunefs.lustre utility modifies configuration information on a Lustre target disk.</para>
<literal>--servicenode=<replaceable>nid,...</replaceable></literal></entry>
<entry>Sets the NID(s) of all service nodes, including primary and failover partner
service nodes. The <literal>--servicenode</literal> option cannot be used with
- <literal>--failnode</literal> option. See <xref
- xmlns:xlink="http://www.w3.org/1999/xlink" linkend="dbdoclet.50438188_92688"/> for
+ <literal>--failnode</literal> option. See
+ <xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="failover_setup"/> for
more details.</entry>
</row>
<row>
<para> <literal>--failnode=<replaceable>nid,...</replaceable></literal></para>
</entry>
<entry>
- <para>Sets the NID(s) of a failover service node for a primary server for a target.
- The <literal>--failnode</literal> option cannot be used with
- <literal>--servicenode</literal> option. See <xref
- xmlns:xlink="http://www.w3.org/1999/xlink" linkend="dbdoclet.50438188_92688"/>
- for more details.<note>
- <para>When the <literal>--failnode</literal> option is used, certain
- restrictions apply (see <xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="dbdoclet.50438188_92688"/>).</para>
- </note></para>
+ <para>Sets the NID(s) of a failover service node for a primary
+ server for a target. The <literal>--failnode</literal>
+ option cannot be used with <literal>--servicenode</literal>
+ option. See <xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="failover_setup"/> for more details.
+ <note><para>When the <literal>--failnode</literal> option
+ is used, certain restrictions apply (see
+ <xref xmlns:xlink="http://www.w3.org/1999/xlink"
+ linkend="failover_setup"/>).</para></note>
+ </para>
</entry>
</row>
<row>
<title>See Also</title>
<itemizedlist>
<listitem>
- <para><xref linkend="dbdoclet.50438219_75432"/></para>
+ <para><xref linkend="mkfs.lustre"/>
+ </para>
</listitem>
<listitem>
- <para><xref linkend="dbdoclet.50438219_12635"/></para>
+ <para><xref linkend="mount.lustre"/>
+ </para>
</listitem>
<listitem>
<para><xref linkend="dbdoclet.50438219_38274"/></para>
</listitem>
<listitem>
- <para><xref linkend="dbdoclet.50438206_94597"/></para>
+ <para><xref linkend="userutilities.lfs"/></para>
</listitem>
</itemizedlist>
</section>
necessary, to reduce the outage window.</para>
</listitem>
</orderedlist>
- <section xml:id="dbdoclet.50438225_13916">
+ <section xml:id="orphan_objects">
<title>
<indexterm>
<primary>recovery</primary>
below.</para>
<para>There is also a
<literal>noscrub</literal> mount option (see
- <xref linkend="dbdoclet.50438219_12635" />) which can be used to
- disable automatic OI scrub upon detection of a file-level backup at
- mount time. If the
+ <xref linkend="mount.lustre" />) which
+ can be used to disable automatic OI scrub upon detection of a
+ file-level backup at mount time. If the
<literal>noscrub</literal> mount option is specified,
<literal>auto_scrub</literal> will also be disabled, so OI scrub will
not be triggered when an OI inconsistency is detected. Auto scrub can
active (using
<literal>tunefs.lustre</literal>). For explanations of these utilities, see
- <xref linkend="dbdoclet.50438219_75432" />and
- <xref linkend="dbdoclet.50438219_39574" />.</para>
+ <xref linkend="mkfs.lustre" />and
+ <xref linkend="tunefs.lustre" />.</para>
<para>Failover capability in a Lustre file system can be used to upgrade
the Lustre software between successive minor versions without cluster
downtime. For more information, see
<para>Lustre file systems run on a variety of vendor's kernels. For more
details, see the Lustre Test Matrix
<xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="dbdoclet.50438261_99193" />.</para>
+ linkend="preparing_installation" />.</para>
<para>A Lustre installation can be scaled up or down with respect to the
number of client nodes, disk storage and bandwidth. Scalability and
performance are dependent on available disk and network bandwidth and the
<link xl:href="https://wiki.whamcloud.com/display/PUB/Lustre+Releases">
Lustre Releases</link> repository. See
<xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="table_cnh_5m3_gk" /> for a list of required packages.</para>
+ linkend="table.installed_server_pkg" />for a list of required packages.
+ </para>
</listitem>
<listitem>
<para>Install the Lustre server packages on all Lustre servers (MGS,
<link xl:href="https://wiki.whamcloud.com/display/PUB/Lustre+Releases">
Lustre Releases</link> repository. See
<xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="table_j3r_ym3_gk" /> for a list of required packages.</para>
+ linkend="table.installed_client_pkg" /> for a list of required packages.
+ </para>
<note>
<para>The version of the kernel running on a Lustre client must be
the same as the version of the
<link xl:href="https://wiki.whamcloud.com/display/PUB/Lustre+Releases">
Lustre Releases</link> repository. See
<xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="table_cnh_5m3_gk" /> for a list of required packages.</para>
+ linkend="table.installed_server_pkg" /> for a list of required packages.
+ </para>
</listitem>
<listitem>
<para>For a rolling upgrade, complete any procedures required to keep
<link xl:href="https://wiki.whamcloud.com/display/PUB/Lustre+Releases">
Lustre Releases</link> repository. See
<xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="table_j3r_ym3_gk" /> for a list of required packages.</para>
+ linkend="table.installed_client_pkg" /> for a list of required packages.
+ </para>
</listitem>
<listitem>
<para>Install the Lustre client packages on each of the Lustre clients
xmlns:xi="http://www.w3.org/2001/XInclude" xml:id="userutilities">
<title xml:id="userutilities.title">User Utilities</title>
<para>This chapter describes user utilities.</para>
- <section xml:id="dbdoclet.50438206_94597">
+ <section xml:id="userutilities.lfs">
<title>
<indexterm>
<primary>lfs</primary>
<section remap="h5">
<title>See Also</title>
<para>
- <xref linkend="dbdoclet.50438206_94597" />
+ <xref linkend="userutilities.lfs" />
</para>
</section>
</section>
<para>Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.</para>
- <para>Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or go to: http://www.intel.com/design/literature.htm</para>
+ <para>Copies of documents which have an order number and are referenced
+ in this document, or other Intel literature, may be obtained by calling
+ 1-800-548-4725, or go to:
+ https://www.intel.com/content/www/us/en/design/resource-design-center.html
+ </para>
<para>Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries. Lustre is a registered trademark of Oracle Corporation.</para>
<para>The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.</para>
- <para>This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License. To view a copy of this license and obtain more information about Creative Commons licensing, visit Creative Commons Attribution-Share Alike 3.0 United States [http://creativecommons.org/licenses/by-sa/3.0/us] or send a letter to Creative Commons, 171 2nd Street, Suite 300, San Francisco, California 94105, USA.</para>
-
+ <para>This work is licensed under a Creative Commons Attribution-Share
+ Alike 3.0 United States License. To view a copy of this license and
+ obtain more information about Creative Commons licensing, visit
+ <link xl:href="http://creativecommons.org/licenses/by-sa/3.0/us">
+ Creative Commons Attribution-Share Alike 3.0 United States</link>
+ or send a letter to Creative Commons, 171 2nd Street, Suite 300,
+ San Francisco, California 94105, USA.
+ </para>
</legalnotice>
<!--
vim:expandtab:shiftwidth=2:tabstop=8:
git://git.whamcloud.com / doc / manual.git / commitdiff