Thank you all for your responses. I have successfully created our systems
using LVM for the following file systems:
/tmp
/home
/opt
plus our application LVM's.
Regards,
[EMAIL PROTECTED]
NCCI
Boca Raton, Florida
561.893.2415
greetings / avec mes meilleures salutations / Cordialmente
mit freundlichen Grüßen / Med vänlig hälsning
Rick Troth
<[EMAIL PROTECTED]> To:
[email protected]
Sent by: Linux on cc:
390 Port Subject: Re: /tmp /usr /opt:
where do they belong after an IPL?
<[EMAIL PROTECTED]
IST.EDU>
06/27/2005 12:04
PM
Please respond to
Linux on 390 Port
What Mark said.
When the system boots, your root filesystem is mounted
automagically by the kernel. The kernel then tries to run /sbin/init.
INIT then runs the rest of the show and typically requires /bin and
/lib and /etc. So your minimal requirements must reside there.
(the most basic or most common run-time libraries and the
earliest used commands and executables)
Having an INITRD changes things
because in INITRD, there is a /bin and /lib and /etc
which are independent of your true root filesystem.
INITRD then goes away after setting things up.
It's even magicker than the magic of mounting root
without a command (as the kernel does at boot time).
> 1) /boot (124 MB)
> 2) / (5 GB)
> 3) SWAP (1.6+)
Looks just fine.
> Then, we created two LVM, one for sys01 and another for app01.
> Each have 5+ 3390 M9 volumes assigned.
> My question now is regarding /usr, /opt and /tmp. They will probably
> grow quite a bit and might be a good idea to get all or some of those
> directories or subdirectories to /sys01. But how can I do so without
> compromising my IPL's to depend on more than one volume.
This too sounds just fine.
In my experience,
manually moving your /usr and /opt content after install is okay.
It's just cumbersome. And /tmp should be empty.
YOU MUST CHECK the individual start-up scripts to see if any
report problems. If you discover a missing command or library,
you MIGHT put a copy of it into the root-resident /sys01 sub-dir
so that item is available before the real /sys01 is mounted.
But this is messy. BETTER would be to sequence the starting
of whatever subsystems you run until all resources they need
are fully operational. (in this case, LVM content)
When checking these things,
be sure to check BEFORE you make changes as well as after.
If you only check after your change, then you do not know for sure
if the "problem" was something you caused or if it was always there
and was not resolved by the distributor/vendor.
-- R;
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
The information contained in this e-mail message is intended only for
the personal and confidential use of the recipient(s) named above. This
message may be an attorney-client communication and/or work product and
as such is privileged and confidential. If the reader of this message
is not the intended recipient or an agent responsible for delivering it
to the intended recipient, you are hereby notified that you have
received this document in error and that any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you
have received this communication in error, please notify us immediately
by e-mail, and delete the original message.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
