On 2/9/06, MOEUR TIM C <[EMAIL PROTECTED]> wrote: > Sorry about that - > > I'm on SLES9 with Linux version 2.6.5-7.244-s390x > > No, I haven't been running mkinitrd and zipl, (forgive me, I'm new at > the Linux on s390 stuff). I was pretty certain that for the successful > LVM that I created that I hadn't done that, but it was some time back, > and I might have done just that while following a cookbook. > > I'm now using YaST to build the LVM volume groups, join the physical > volumes to it, and also to create the logical volumes. Are you saying > that I also need to then exit yast and run mkinitrd and zipl? > > Tim > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > John Schnitzler Jr > Sent: Thursday, February 09, 2006 11:52 AM > To: [email protected] > Subject: Re: LVM, SLES9 and 64 bit > > Tim are you running the mkinird and the zipl after defining the LVM? > You didn't say what version of linux you are using. > > John > > > > 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 > > ---------------------------------------------------------------------- > 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 > yast/yast2 for some reason does not run zipl even when it is supposed to run after creating an lvm. It could be a bug.
---------------------------------------------------------------------- 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
