thanks for the note. i completely mistyped. -----Original Message----- From: Mark Post [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 14, 2004 2:55 PM To: [EMAIL PROTECTED] Subject: Re: LVM woes in SLES 9
Actually, that would be backwards. When you run zipl, it places pointers to certain files out on disk. If you then run mkinitrd after that, the pointer will now be aimed at unused space. At some point in the future, it is possible that those inodes will be reused with other data, rendering your system non-IPLable. It's not a given that this will happen, since /boot is not very volatile, so you may not run into it for a while, but it has happened to a number of people on the list. The zipl command should be the last command executed when making kernel, parmfile, or initrd changes. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Little, Chris Sent: Tuesday, December 14, 2004 2:54 PM To: [EMAIL PROTECTED] Subject: Re: LVM woes in SLES 9 if no IPL configuration has changed (dasd range, etc) then just enter "zipl" and then "mkinitrd" on the command line. Viola. -----Original Message----- From: Ranga Nathan [mailto:[EMAIL PROTECTED] Sent: Monday, December 13, 2004 6:54 PM To: [EMAIL PROTECTED] Subject: Re: LVM woes in SLES 9 We are using 3390 DASD. Could someone explain what needs to be done with mk_initrd and zipl? I thought I saw something in old mail but had difficulty formulating the complete procedure. Could someone share the steps? Thanks __________________________________________ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 "Seader, Cameron" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 12/13/2004 06:44 AM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject: Re: LVM woes in SLES 9 If you use EVMS to manage your FCP SCSI disks there are some timing issues with the boot.evms scripts that do not work. I had to make some work arounds for it. I have submitted these to SuSE and I'm waiting to here back on whether those will be in SP1 or not. -Cameron -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Kohrs, Steven Sent: Monday, December 13, 2004 07:21 To: [EMAIL PROTECTED] Subject: Re: LVM woes in SLES 9 On Sat, 2004-12-11 at 00:30, Ranga Nathan wrote: > I tried to do LVM via Yast many times but have not been successful. After > reboot the volume group and logical volumes disappeared. Thanks to VM I > re-cloned the guest and have recreated the vol group, this time from > command line. But with a POR coming up on Sunday, I am in a dilemma. If I > reboot the Linux guest, I will lose the volume group. Before that I need > to do whatever to make it stick. > ... > Does anyone have a checklist of things to make the vol group persistent > across reboot for SLES 9? > I don't have anything useful to contribute, just that this might explain why my SLES 9 guest stopped booting with a failure mounting a LVM logical volume. I thought I screwed something up and haven't had a chance to investigate the problem yet. Although, I had rebooted this guest many times before, so I probably did break it. Maybe I'll play with this today. I didn't want to do real work anyway. ---------------------------------------------------------------------- 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 This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
