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.

Device <strong>Operations</strong><br />

Option<br />

Description<br />

lctl get_param [-n] <br />

Gets the <strong>Lustre</strong> or LNET parameters from the specified . Use the -n<br />

option to get only the parameter value and skip the pathname in the output.<br />

lctl set_param [-n] <br />

Sets the specified value to the <strong>Lustre</strong> or LNET parameter indicated by the<br />

pathname. Use the -n option to skip the pathname in the output.<br />

conf_param <br />

activate<br />

deactivate<br />

abort_recovery<br />

Sets a permanent configuration parameter for any device via the MGS. This<br />

command must be run on the MGS node.<br />

Re-activates an import after the deactivate operation.<br />

Running lctl deactivate on the MDS stops new objects from being allocated<br />

on the OST. Running lctl deactivate on <strong>Lustre</strong> clients causes them to return -<br />

EIO when accessing objects on the OST instead of waiting for recovery.<br />

Aborts the recovery process on a re-starting MDT or OST device.<br />

Note – <strong>Lustre</strong> tunables are not always accessible using procfs interface, as it is<br />

platform-specific. As a solution, lctl {get,set}_param has been introduced as a<br />

platform-independent interface to the <strong>Lustre</strong> tunables. Avoid direct references to<br />

/proc/{fs,sys}/{lustre,lnet}. For future portability, use lctl {get,set}_param instead.<br />

32-10 <strong>Lustre</strong> 1.7 <strong>Operations</strong> <strong>Manual</strong> • August 2008

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

Saved successfully!

Ooh no, something went wrong!