On Sat, Jan 3, 2009 at 8:29 AM, Philip Hitti <[email protected]> wrote:
> Cloned several Suse Zlinux machine under Z/vm from the base system by > giving the same Mdisk addresses > MDISK 1000 3390 DEVNO F010 MR > MDISK 1001 3390 DEVNO F011 MR > which create duplicate label as 0x1000 and 0x1001. > How we can create the differet volume label of the linux machines or > change the volume label of linux machines. You can specify / change it with fdasd. Linux itself does not use the volser, it would only be for other System z Operating Systems in the environment to recognize the volumes (and storage admin persons). But with Linux being able to change the volser, anything you base on that knowledge is possibly at risk. If you give Linux "pseudo full pack" disks (starting at cylinder 1) then z/VM can manage the volser as you want. Unfortunately, you can't shrink the existing Linux disks now, so you would need to copy the files. The advantage of using volser to manage your DASD (rather than real address) is that you can use logical names that make sense in managing the data. So you can have volser VMxxxx for VM data and LXTxxx for Linux test and LXPxxx for Linux production, or whatever. Using device address ranges is less pleasant because that also has performance implications (disks in the same rank or array). Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/ ---------------------------------------------------------------------- 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
