One issue is in a default SuSE9 install, the "dasd=" is not used in the parmfile. If you add DASD and activate it via yast, the parmfile is not touched; yast will happily adds the new DASD to /etc/fstab until the /dev/dasdXX changes and then it won't boot.
To add confusion, SuSE9 also adds: /dev/disk/by-path/ccw-0.0.0309p1 -> ../../dasdj1 which appears persistent and mountable. But then if you add DASD in the middle, the link to /dev/dasdXX is not maintained and is wrong. ----------------------------------------------------------- Ismael Ifurung Tel. (916) 739-7689 Health & Human Services Data Center Fax. (916) 739-7777 P.O. Box 168025 Sacramento, CA 95816 [EMAIL PROTECTED] ----------------------------------------------------------- -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marcy Cortes Sent: Monday, June 13, 2005 9:25 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: e: LVM fragility? Well, on my sles8 instances, it seems to run out of "/etc/init.d/boot.lvm" . I didn't have to turn that one on so something either in the install or LVM creation must have. My SLES8 LVM's are perfectly happy having their disk letters changing (at least until I got to 26 letters and had to do more mknod's). Issue "chkconfig" and see if boot.lvm is set to ON. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Phil Smith III Sent: Saturday, June 11, 2005 06:49 To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] e: LVM fragility? "Sal Torres/SBC Inc." <[EMAIL PROTECTED]> wrote: >The nice thing about LVM is that you can change the DASD >addresses (disk letters) and still works as each physical LVM >volume gets it own unique id (uuid). For example if you have >an LVM group with 2 disks, dasdt1 (400) and dasdu1 (401), >you can change them to dasdv1(402) and dasdx1(404) with >no problems. How does one effect this change? Someone suggested to me that just running vgscan again would find & fix the LVM; if so, that's semi-easy, although it's a manual step. I suppose it could be added to init.d. Thanks for all the replies saying "don't do that"; that's not a workable answer in this case -- the LVMs are set up outside of Levanta, so the product has no way of knowing that particular disks are 'special'. ...phsiii ---------------------------------------------------------------------- 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
