23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

To turn off network logging with changing existing flags:<br />

sysctl -w lnet.debug=-net<br />

The various options available to print to kernel debug logs are listed in<br />

lnet/include/libcfs/libcfs.h<br />

23.2.3 The lctl Tool<br />

<strong>Lustre</strong>’s source code includes debug messages which are very useful for<br />

troubleshooting. As described above, debug messages are subdivided into a number<br />

of subsystems and types. This subdivision allows messages to be filtered, so that<br />

only messages of interest to the user are displayed. The lctl tool is useful to enable<br />

this filtering and manipulate the logs to extract the useful information from it. Use<br />

lctl to obtain the necessary debug messages:<br />

1. To obtain a list of all the types and subsystems:<br />

lctl > debug_list <br />

2. To filter the debug log:<br />

lctl > filter <br />

Note – When lctl filters, it removes unwanted lines from the displayed output.<br />

This does not affect the contents of the debug log in the kernel's memory. As a result,<br />

you can print the log many times with different filtering levels without worrying<br />

about losing data.<br />

3. To show debug messages belonging to certain subsystem or type:<br />

lctl > show <br />

debug_kernel pulls the data from the kernel logs, filters it appropriately, and<br />

displays or saves it as per the specified options<br />

lctl > debug_kernel [output filename]<br />

If the debugging is being done on User Mode Linux (UML), it might be useful to<br />

save the logs on the host machine so that they can be used at a later time.<br />

Chapter 23 <strong>Lustre</strong> Debugging 23-7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!