From: "Sridharan Ramaswamy \(srramasw\)" <[EMAIL PROTECTED]>
Date: Thu, 7 Dec 2006 13:39:51 -0800
by this you mean to include Lustre modules that typically gets loaded
during lconf, right?
It's been long enough since I used lconf that I can't speak to that. The
short answer is "any module which is needed in order to be a client should be
copied into the initrd".
> get them loaded from the init script, mount the fs in question,
> pivot root, and off you go.
I was not aware of this "pivot_root" until now. This is perfect!!
Again, if you have this basic recipe described in more detailed, it will
great.
See the script I just posted.
Mine's got a bit of extra magic in it because we wanted to maintain several
rootfs images, which meant we wanted them in subdirs. Sadly, there appears to
be no way to mount a subdir of a lustrefs, only the top level (perhaps that
could be taken as a feature request, hint, hint) so we have to play the mount
bind game. It's a hack, but it works.
Oh sure. I too was thinking that nodes shouldn't share dirs like /etc,
/var/log, etc.
Right.
Think of it as a mostly read-only fs. There are a small number of parts which
can't be read-only, such as /tmp, /var, perhaps parts of /usr etc. Those
parts must have something else mounted on them.
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
