Lustre 1.6 Operations Manual

Currently (v1.4.5) the Voltaire IB module (kvibnal) will _not work on the Altix
system. This is due to hardware differences in the Altix system.
To build Silverstorm with Lustre, configure Lustre with:
--with-iib=
Can the same Lustre filesystem be mounted at multiple mount points on
the same client system?
Yes, this is perfectly safe.
How do I identify files affected by a missing OST?
If an OST is missing for any reason, you may need to know what files are affected.
The filesystem should still be operational, even though one OST is missing, so from
any mounted client node it is possible to generate a list of files that reside on that
OST.
In such situations it is advisable to mark the missing OST unavailable so clients and
the MDS do not time out trying to contact it. On MDS+client nodes:
# lctl dl # to generate a list of devices, find the OST device number
# lctl --device N deactivate # N will be different between the MDS
and clients
If the OST later becomes available it needs to be reactivated:
# lctl --device N activate
Determine all the files striped over the missing OST:
# lfs find -R -o {OST_UUID} /mountpoint
This returns a simple list of filenames from the affected filesystem.
It is possible to read the valid parts of a striped file (if necessary):
# dd if=filename of=new_filename bs=4k conv=sync,noerror
Otherwise, it is possible to delete these files with "unlink" or "munlink".
If you need to need to know specifically which parts of the file are missing data you
first need to determine the file layout (striping pattern), which includes the index of
the missing OST:
# lfs getstripe -v {filename}
Appendix D Lustre Knowledge Base D-21