"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
