following sections:</para>
<itemizedlist>
<listitem>
- <para><xref linkend="dbdoclet.50438198_11171"/></para>
+ <para><xref linkend="lustre_error_messages"/></para>
</listitem>
<listitem>
- <para><xref linkend="dbdoclet.reporting_lustre_problem"/></para>
+ <para><xref linkend="reporting_lustre_problem"/></para>
</listitem>
<listitem>
- <para><xref linkend="dbdoclet.50438198_93109"/></para>
+ <para><xref linkend="common_lustre_problems"/></para>
</listitem>
</itemizedlist>
- <section xml:id="dbdoclet.50438198_11171">
+ <section xml:id="lustre_error_messages">
<title><indexterm><primary>troubleshooting</primary></indexterm>
<indexterm><primary>lustre</primary><secondary>troubleshooting</secondary><see>troubleshooting</see></indexterm>
<indexterm><primary>lustre</primary><secondary>errors</secondary><see>troubleshooting</see></indexterm>
</tgroup>
</informaltable>
</section>
- <section xml:id="dbdoclet.50438198_40669">
+ <section xml:id="troubleshooting">
<title><indexterm><primary>troubleshooting</primary><secondary>error messages</secondary></indexterm>Viewing Error Messages</title>
<para>As Lustre software code runs on the kernel, single-digit error codes display to the
application; these error codes are an indication of the problem. Refer to the kernel console
</note>
</section>
</section>
- <section xml:id="dbdoclet.reporting_lustre_problem">
+ <section xml:id="reporting_lustre_problem">
<title><indexterm>
<primary>troubleshooting</primary>
<secondary>reporting bugs</secondary>
</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
tickets for your issue.
<emphasis role="italic">For search tips, see
<xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="dbdoclet.searching_jira"/>.</emphasis></para>
+ linkend="searching_jira"/>.</emphasis></para>
</listitem>
<listitem>
<para>To create a ticket, click <emphasis role="bold">+Create Issue</emphasis> in the
<listitem>
<para><emphasis role="italic">Attachments</emphasis> - Attach log sources such as
Lustre debug log dumps (see <xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="dbdoclet.50438274_15874"/>), syslogs, or console logs. <emphasis
+ linkend="debugging_tools"/>), syslogs, or console logs. <emphasis
role="italic"><emphasis role="bold">Note:</emphasis></emphasis> Lustre debug
logs must be processed using <code>lctl df</code> prior to attaching to a Jira
ticket. For more information, see <xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="dbdoclet.50438274_62472"/>. </para>
+ linkend="using_lctl_tool"/>. </para>
</listitem>
</itemizedlist>Other fields in the form are used for project tracking and are irrelevant
to reporting an issue. You can leave these in their default state.</para>
</listitem>
</orderedlist></para>
- <section xml:id="dbdoclet.searching_jira">
+ <section xml:id="searching_jira">
<title>Searching Jira<superscript>*</superscript>for Duplicate Tickets</title>
<para>Before submitting a ticket, always search the Jira bug tracker for
an existing ticket for your issue. This avoids duplicating effort and
obd_last_committed failed:</code></para>
</section>
</section>
- <section xml:id="dbdoclet.50438198_93109">
+ <section xml:id="common_lustre_problems">
<title><indexterm>
<primary>troubleshooting</primary>
<secondary>common problems</secondary>
then it is possible that you have discovered a programming error that
allowed the servers to get out of sync.
Please submit a Jira ticket (see <xref xmlns:xlink="http://www.w3.org/1999/xlink"
- linkend="dbdoclet.reporting_lustre_problem"/>).</para>
+ linkend="reporting_lustre_problem"/>).</para>
<para>If the reported error is anything else (such as -5,
"<literal>I/O error</literal>"), it likely indicates a storage
device failure. The low-level file system returns this error if it is
OST in its place or replace it with a newly-formatted OST. In that case,
the missing objects are created and are read as zero-filled.</para>
</section>
- <section xml:id="dbdoclet.repair_ost_lastid">
+ <section xml:id="repair_ost_lastid">
<title>Fixing a Bad LAST_ID on an OST</title>
<para>Each OST contains a <literal>LAST_ID</literal> file, which holds
the last object (pre-)created by the MDS
such as <literal>No space left on device</literal>. The numeric
error message may also appear in the system log.</para>
<para>For more information about the <literal>lfs df</literal> command,
- see <xref linkend="dbdoclet.checking_free_space"/>.</para>
+ see <xref linkend="file_striping.checking_free_space"/>.</para>
<para>You can also use the <literal>lctl get_param</literal> command to
monitor the space and object usage on the OSTs and MDTs from any
client:</para>
</listitem>
</itemizedlist>
<para>For information on determining the MDS memory and OSS memory
- requirements, see <xref linkend="dbdoclet.mds_oss_memory"/>.</para>
+ requirements, see <xref linkend="mds_oss_memory"/>.</para>
</section>
<section remap="h3">
<title>Setting SCSI I/O Sizes</title>
git://git.whamcloud.com / doc / manual.git / blobdiff