Tim,
Make sure you run mkinitrd and zipl after configuring the LV(s), as well
as adding them to /etc/fstab. If you do not run mkinitrd then the volumes
won't come up on boot. We experienced this just a couple weeks ago.
-----------------------------------------------------------------------------
Michael Krysiak
CSC/GIS, 10 Technology Dr, Wallingford, CT 06492
Office:(203) 949-1407 Mobile: (203) 558-2432
----------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use of
e-mail for such purpose.
----------------------------------------------------------------------------------------
MOEUR TIM C <tcmoeur
@srpnet.com>
Sent by: Linux on 390 Port <LINUX-390
02/09/2006 01:38 PM
Please respond to Linux on 390 Port
To: [email protected]
cc:
Subject: LVM, SLES9 and 64 bit
Hello all,
I've been fighting an LVM problem and searching through the archives and
I stumbled on this from Mark Post from a while back:
Re: /tmp as a logical volume
Post, Mark K
Tue, 21 Jun 2005 21:35:24 -0700
>I'm beginning to have doubts about LVM (version 1 at least) on 64-bit
> systems. I've had two cases where my volume groups have disappeared
after an
> IPL, and hence all my logical volumes. Emails to the linux-lvm mailing
list
> have gone unanswered. I don't know if it's because I'm running
Linux/390,
> LVM 1 or what. Having said that, if you're going to use LVM, using it
for
> /tmp is certainly the safest. According to the FHS, the contents of
/tmp are > not guaranteed across a reboot anyway.
This describes my troubles exactly, I create some LVM volume groups
(and logical volumes), but they don't survive through an IPL. What I
haven't been able to find is any resolution of this problem. What makes
it worse, is that I've done it successfully with other volume groups.
Mark (or anybody else that shares my woes), have you found any more
information about this?
Tim
[EMAIL PROTECTED]
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
