You can still use the minimal-impact lustre/utils/module_setup.sh script
without having to make install. Additionally, lustre/tests/sanity.sh
also uses test-framework, and so will insmod modules from the local
directory (unless env. variable MODPROBE=true) anyhow.
Further problems with not using the correct kernel modules directory is
that you must use insmod instead of modprobe, which 1. requires a
specific module loading order, and 2. will ignore any settings in
modprobe.conf, e.g. options lnet networks=(anything other than tcp eth0)
Jim Garlick wrote:
One of my tasks for LLNL is to get the 'sanity' tests to work against
packaged and installed modules in our QA environment.
However, I think being able to run the tests on modules located in the
source tree has merit too as building an rpm implies a rebuild from
scratch, and that is a pain when you are making small changes and
testing as you go. (running 'make install' is strictly
verboten here as it is too easy to violate someone elses packaging and
screw up something - like QA results or production!)
So, my $0.02 (for what its worth) is I kinda like Peter's suggestion.
Jim
On Wed, 15 Nov 2006, Nathaniel Rutman wrote:
The appropriate modules are loaded automatically, on demand, when
"mount -t lustre" is given. The only reason llmount (and more
generally the test-framework.sh) tries to load from a local dir is
because certain CFS developers don't like to copy their
in-development modules into the place where they are _supposed_ to
live (/lib/modules/`uname -r`/). No script is needed in the "normal"
case (rpms or 'make install')
Peter J. Braam wrote:
Hi Nathan,
Have we considered making the module loading an option to
mount.lustre -
e.g. mount -t lustre -o moddir=/foo/bar .... To make the shell
script almost go away. I think this would be very nice.
- Peter -
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Nathaniel Rutman
Sent: Wednesday, November 15, 2006 1:26 PM
To: Lin Shen (lshen)
Cc: [email protected]
Subject: Re: [Lustre-discuss] Configure 1.6 beta
The script lustre/tests/llmount.sh will load the modules from the
local build dir and start a small Lustre fs on a single node. You
can change many of options by overriding the values set in
lustre/tests/cfg/local.sh if e.g. you want to use real disks.
But eventually you need to put the modules in the appropriate place
for the kernel to find them if you ever want to do anything else.
lustre/utils/module_setup.sh does this for you, and modifies
/etc/modprobe.conf for a basic tcp LNET setup.
Lin Shen (lshen) wrote:
Hi,
I'm new to Lustre and trying to evaluate 1.6 beta. My first
goal is to
setup a single node system. I'm following the MountConf
manual and a
bit confused by the section "Module setup" (not sure where to find
utils/module_setup, and which "make all" it's talking about). Do I
really need to do anything here? Or can I just run mkfs.lustre and
mount to get the system up and running?
Thanks
lin
----------------------------------------------------------------------
--
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
