From: Linda Bebernes Date: Mon, 10 Jun 2013 18:14:53 +0000 (-0700) Subject: LUDOC-19 bug: Updated Reporting Lustre Bug section X-Git-Tag: 2.5.0~49 X-Git-Url: https://git.whamcloud.com/?a=commitdiff_plain;h=10fea9cb3c08b2781559849ccf4278265095aeff;p=doc%2Fmanual.git LUDOC-19 bug: Updated Reporting Lustre Bug section Updated procedure with new content and several links. Signed-off-by: Linda Bebernes Change-Id: I2aed9e4cbbcd6e7a26f1c516c6f40ae538035e6d Reviewed-on: http://review.whamcloud.com/6545 Tested-by: Hudson Reviewed-by: James Nunez Reviewed-by: Cliff White Reviewed-by: Andreas Dilger Reviewed-by: Richard Henwood --- diff --git a/LustreDebugging.xml b/LustreDebugging.xml index b875a4d..ad61059 100644 --- a/LustreDebugging.xml +++ b/LustreDebugging.xml @@ -17,21 +17,31 @@ <indexterm><primary>debugging</primary></indexterm> Diagnostic and Debugging Tools A variety of diagnostic and analysis tools are available to debug issues with the Lustre software. Some of these are provided in Linux distributions, while others have been developed and are made available by the Lustre project. -
- <indexterm><primary>debugging</primary><secondary>tools</secondary></indexterm> -Lustre Debugging Tools - The following in-kernel debug mechanisms are incorporated into the Lustre software: +
+ <indexterm> + <primary>debugging</primary> + <secondary>tools</secondary> + </indexterm> Lustre Debugging Tools + The following in-kernel debug mechanisms are incorporated into the Lustre + software: - Debug logs - A circular debug buffer to which Lustre internal debug messages are written (in contrast to error messages, which are printed to the syslog or console). Entries to the Lustre debug log are controlled by the mask set by /proc/sys/lnet/debug. The log size defaults to 5 MB per CPU but can be increased as a busy system will quickly overwrite 5 MB. When the buffer fills, the oldest information is discarded. + Debug logs - A circular + debug buffer to which Lustre internal debug messages are written (in contrast to error + messages, which are printed to the syslog or console). Entries to the Lustre debug log + are controlled by the mask set by /proc/sys/lnet/debug. The log size + defaults to 5 MB per CPU but can be increased as a busy system will quickly overwrite 5 + MB. When the buffer fills, the oldest information is discarded. - Debug daemon - The debug daemon controls logging of debug messages. + Debug daemon - The debug daemon controls logging of + debug messages. /proc/sys/lnet/debug - - This file contains a mask that can be used to delimit the debugging information written out to the kernel debug logs. + - This file contains a mask that can be used to delimit the debugging + information written out to the kernel debug logs. The following tools are also provided with the Lustre software: @@ -39,17 +49,25 @@ Lustre Debugging Tools lctl - - 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 . + - 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 . + 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 information about lfs, see . + - This utility provides access to the extended attributes (EAs) of a Lustre + file (along with other information). For more information about lfs, see .
diff --git a/LustreTroubleshooting.xml b/LustreTroubleshooting.xml index 2c31b8e..b00a6da 100644 --- a/LustreTroubleshooting.xml +++ b/LustreTroubleshooting.xml @@ -203,14 +203,99 @@
<indexterm><primary>troubleshooting</primary><secondary>reporting bugs</secondary></indexterm><indexterm><primary>reporting bugs</primary><see>troubleshooting</see></indexterm> Reporting a Lustre Bug - If, after troubleshooting your Lustre system, you cannot resolve the problem, consider reporting a Lustre bug. The process for reporting a bug is described in the Lustre wiki topic Reporting Bugs. - You can also post a question to the lustre-discuss mailing list or search the lustre-discuss Archives for information about your issue. - A Lustre diagnostics tool is available for downloading at: http://downloads.whamcloud.com/public/tools/ - You can run this tool to capture diagnostics output to include in the reported bug. To run this tool, enter one of these commands: - # lustre-diagnostics -t bug_number -# lustre-diagnostics. - - Output is sent directly to the terminal. Use normal file redirection to send the output to a file, and then manually attach the file to the bug you are submitting. + If you cannot resolve a problem by troubleshooting your Lustre file system, other options are: + + Post a question to the hppd-discuss + email list or search the archives for information about your issue. + + + Submit a Jira ticket. The Jira project + tracker is the 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 Sign up on the Welcome page. + + To submit a Jira ticket, follow these steps: + + To avoid filing a duplicate ticket, search for existing tickets for your issue. + For search tips, see . + + + To create a ticket, click +Create Issue in the + upper right corner. Create a separate ticket for each issue you + wish to submit. + + + In the form displayed, enter the following information: + + Project - Select Lustre or Lustre Documentation or + an appropriate project. + + + Issue type - Select Bug. + + + Summary - Enter a short description of the + issue. Use terms that would be useful for someone searching for a similar issue. A + LustreError or ASSERT/panic message often makes a good summary. + + + Affects version(s) - Select your Lustre + version. + + + Environment - Enter your kernel with + version number. + + + Description - Include a detailed + description of visible symptoms and, if + possible, how the problem is produced. Other + useful information may include the behavior you expect to + see and what you have tried so far to + diagnose the problem. + + + Attachments - Attach log sources such as + Lustre debug log dumps (see ), syslogs, or console logs. Note: Lustre debug + logs must be processed using lctl df prior to attaching to a Jira + ticket. For more information, see . + + 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. + + +
+ Searching Jira for Duplicate Tickets + Before submitting a ticket, always search Jira for an existing ticket for your + issue.This avoids duplicating effort and may immediately provide you with a solution to your + problem. + To do a search in Jira, select the Issues tab and click + on New filter. Use the filters provided to select criteria + for your search. To search for specific text, enter the text in the "Contains text" field + and click the magnifying glass icon. + When searching for text such as an ASSERTION or LustreError message, you can remove NIDS + and other installation-specific text from your search string by following the example + below. + Original error message: + "(filter_io_26.c:791:filter_commitrw_write()) ASSERTION(oti->oti_transno + <=obd->obd_last_committed) failed: oti_transno 752 + last_committed 750" + Optimized search string : + "(filter_io_26.c:" AND + ":filter_commitrw_write()) ASSERTION(oti->oti_transno + <=obd->obd_last_committed) failed: +
<indexterm><primary>troubleshooting</primary><secondary>common problems</secondary></indexterm>Common Lustre Problems