OK I see. Do you really need real cyl0 for the virtual systems? David -----Original Message----- From: Linux on 390 Port on behalf of Ayer, Paul W Sent: Wed 1/23/2008 1:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: dasdfmt Right attached and dedicated to me was always who cares they are about the same ...
We have been using mini disks up to this point and the space that the linux would see was always after cylinder 0 (vm staff is calling this attached).. dasdfmt has no effect on what VM sees for volser Now we are doing full volumes and linux now sees cylinder 0 too (vm staff is calling this dedicated) VM now sees whatever volser is done via dasdfmt ... We can and will if needed get in sync so that the volser will be unique actually I have suggested that we just start dedicating "real addres" as "real address" and then set the volser to "real address" for any full volume packs ... But was just wondering if I was missing a way to not have dasdfmt lay down a label / volser .. looks like no ... -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Kreuter Sent: Wednesday, January 23, 2008 1:01 PM To: LINUX-390@vm.marist.edu Subject: Re: dasdfmt >We have been using all vm mini disks up to this point with attach >statements. Like; > attach 2021 as aa01 to systemA > attach 2022 as aa01 to systemB > attach 2023 as aa01 to systemC Attached disks are not minidisks; the virtual system owns real cylinder 0 once the pack is attached. It is the same as DEDicated volumes, except an attach command can be done dynamically. At IPL time unless you instruct system config otherwise you will have 3 volumes with the same label, true. I don't see in your example where you are using minidisks that start on a cylinder other than 0. Real cylinder 0 should be avoided for virtual machine use. David -----Original Message----- From: Linux on 390 Port on behalf of Ayer, Paul W Sent: Wed 1/23/2008 12:56 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: dasdfmt Running under z/VM 5.2 / 5.3 & RHEL 4.4 and 4.5 We have been using all vm mini disks up to this point with attach statements. Like; attach 2021 as aa01 to systemA attach 2022 as aa01 to systemB attach 2023 as aa01 to systemC ... Now we are starting to dedicate full disks (and share space across LPAR's as well); Dedicate 3301 as aa01 to system1 Dedicate 3302 as aa01 to system2 Dedicate 3303 as aa01 to system3 So the link as xxx is good on the linux side for standards and all. The dasdfmt we have been using thus far is to set the -l to LXzzzz (zzzz = the address that the linux sees) dasdfmt -b 4096 -d cdl -f /dev/dasdw -l LXAA01 -p -y Works fine on mini disk and the label / volser is never seen. On dedicated full volumes the label / volser is seen and from VM's point of view it now has three disks with a volser of LXAA01. I'm told this will cause a problem at VM IPL time .... Thanks, Paul ... -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Wednesday, January 23, 2008 11:54 AM To: LINUX-390@vm.marist.edu Subject: Re: dasdfmt >>> On Wed, Jan 23, 2008 at 8:07 AM, in message <[EMAIL PROTECTED]>, "Ayer, Paul W" <[EMAIL PROTECTED]> wrote: > Using dasdfmt to format ECKD disks. Is there a way to not write a > volser to the disk? I imagine you could pass a string of blanks for the volser, but why do you think you need to do that? Mark Post ---------------------------------------------------------------------- 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
