On Fri, 1 Dec 2006, Syed Haider wrote:
-What is the proper order in which this type of config should booted? I
should also mention that we also have a "head node" which I believe is
no more than a client itself.
Start the MDS first, then the OSSes.
When the systems are up, I start the services for lustre and the status
shows that lustre is running, but I still have to tell lustre where my
xml file is so it loads (lconf --node client /lustre/config.xml). Why?
AFAICS the service script expects the XML to be /etc/lustre/config.xml,
unless LUSTRE_CONFIG_XML is set in /etc/sysconfig/lustre.
And finally, we've had plenty of I/O errors which (storage interconnect
vi infiniband over IP) we believe may be due to timeout issues. What are
the "best practices" for setting ldlm timeouts and timeouts for such a
config? and can I set those permanently in the configuration rather than
having to use sysctl, maybe through lcm or lctl?
Your distro probably has /etc/sysctl.conf for this purpose.
Bull has also released Lustre administration tools, which are useful to
set up and start Lustre systems from a single admin node. Not sure the
current (and old) released patch applies cleanly to 1.4.7, but you could
try. See: http://www.bullopensource.org/lustre/
--
Jean-Marc Saffroy - [EMAIL PROTECTED]
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
