WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Difference between revisions of "Diagnostic and Debugging Tools"

From Obsolete Lustre Wiki
Jump to navigationJump to search
Line 24: Line 24:
 
== External debugging tools ==
 
== External debugging tools ==
 
====Tools for administrators and developers ====
 
====Tools for administrators and developers ====
The tools described in this section are provided in the Linux kernel or are available at an external website. See [[Lustre Debugging Procedures]] for information about usuing some of these tools for Lustre debugging.
+
The tools described in this section are provided in the Linux kernel or are available at an external website. See [[NEW Lustre Debugging Procedures]] for information about usuing some of these tools for Lustre debugging.
  
 
Some general debugging tools are: [[Do we need to provide links to more info for these?]]
 
Some general debugging tools are: [[Do we need to provide links to more info for these?]]

Revision as of 10:56, 1 February 2010

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.

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 daemon. The debug daemon controls logging of debug messages.

For more information about using these tools to debug Lustre issues, see NEW Lustre Debugging Procedures.

These tools are also provided with the Lustre software:

  • Lustre subsystem asserts. A panic-style assertion 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. Cliff review.

External debugging tools

Tools for administrators and developers

The tools described in this section are provided in the Linux kernel or are available at an external website. See NEW Lustre Debugging Procedures for information about usuing some of these tools for Lustre debugging.

Some general debugging tools are: Do we need to provide links to more info for these?

  • strace. This tool allows a system call to be traced.
  • /var/log/messages. syslogd prints fatal or serious messages at this log.
  • Crash dumps. On crash-dump enabled kernels, sysrq c produces a crash dump. Lustre enhances this crash dump with a log dump (the last 64 KB of the log) to the console. same as crash below?
  • debugfs. Interactive file system debugger.

The following logging and data collection tools can be used to collect information for debugging Lustre kernel issues:

  • netconsole. Supports kernel-level network logging over UDP. A system requires (SysRq) allows users to collect relevant data through netconsole. For more information, see Netconsole.

Tools for developers

The tools described in this section may be useful for debugging Lustre™ in a development environment.

Of general interest is:

A virtual machine is often used to create an isolated development and test environment. Some commonly-used virtual machines are:

  • VirtualBox Open Source Edition. Provides enterprise-class virtualization capability for all major platforms and is available free from Sun Microsystems at Get Sun Virtual Box.
  • Xen. 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, see Using Xen with Lustre or go to xen.org]
Parinay is planning to "include KVM here and how lustre can be deployed on it". See BZ 21381

A variety of debuggers and analysis tools are available including:

  • kgdb. The Linux Kernel Source Level Debugger kgdb is used in conjunction with the GNU Debugger gdb for debugging the Linux kernel.
For more information about using kgdb with gdb, see Chapter 6. Running Programs Under gdb in the Red Hat Linux 4 Debugging with GDB guide.
The kgdb debugger also supports the use of User Datagram Protocol (UDP) for remote debugging. For more information, see ipgdb.sourceforge.net. Is this a good link?
KGDB - this page to be deleted - Robert Read says content is generic rather than Lustre specific
Does any of this need to be mentioned? We provide kgdb patches for some kernels like rhel4 with the Lustre patches (these are not patched in by default). Get patches from ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/
  • lcrash. A utility that generates detailed kernel information and provides the ability to generate reports about system crash dumps. For more information, see this man page. Is this a good link?
  • crash. Red Hat Crash Utility?? is used to analyze saved crash dump data when a system had panicked or locked up or appears unresponsive.
keep this? Enter:
crash vmlinux crash_dump 
For more information about using crash to analyze a crash dump, see:
- Red Hat Magazine article A quick overview of Linux kernel crash dump analysis.
- Crash Usage: A Case Study from the white paper Red Hat Crash Utility by David Anderson.
- Kernel Trap forum entry Linux: Kernel Crash Dumps.
- White paper A Quick Overview of Linux Kernel Crash Dump Analysis.

NOTES See Tien's suggestion BZ 21334 [[1]]