23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

22.1.2 <strong>Lustre</strong> Logs<br />

The error message initiates with "<strong>Lustre</strong>Error" in the console log and provides a<br />

short description of:<br />

■ What the problem is<br />

■ Which process ID had trouble<br />

■ Which server node it was communicating with, and so on.<br />

Collect the first group of messages related to a problem, and any messages that<br />

precede "LBUG" or "assertion failure" errors. Messages that mention server nodes<br />

(OST or MDS) are specific to that server; you must collect similar messages from the<br />

relevant server console logs.<br />

Another <strong>Lustre</strong> debug log holds information for <strong>Lustre</strong> action for a short period of<br />

time which, in turn, depends on the processes on the node to use <strong>Lustre</strong>. Use the<br />

following command to extract these logs on each of the nodes involved, run<br />

$ lctldk <br />

Note – LBUG freezes the thread to allow capture of the panic stack. A system reboot<br />

is needed to clear the thread.<br />

22-2 <strong>Lustre</strong> <strong>1.6</strong> <strong>Operations</strong> <strong>Manual</strong> • September 2008

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

Saved successfully!

Ooh no, something went wrong!