I received several responses suggesting not to use 0-END but rather 1-END. I should have mentioned the reason why I do this - the disk in question is mod-a with 212k cylinders. CP (and hence also DirMaint) does not support minidisk bigger than 65,519 cylinders. And I cannot carve up this disk to many small disks for management reasons. Just imagine, I would neeed to use 4 disks instead of one. As it is RHEL 5.6 I need to use multipathing for PAV which gives me 16 devices to work with instead of 4. And I will have several of theses mod-a volumes available in a single Linux.
That is why I use 0-END which forces me to take care of volume serial in Linux because I need to keep the volume serial names consistent to naming scheme. =================== Marian Gasparovic =================== "The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind." > >On Wed, Aug 31, 2011 at 12:03 PM, Marian Gasparovic <[email protected]> wrote: > >Hello all, >>I am not sure if I do something wrong here.... >> >>I format a DASD in CP as PERM. Then I provide this DASD to Linux as fullpack >>minidisk, 0-END. >>When I issue lsdasd I see the disk is not formatted, as expected. >>>From CP I can see the volume serial on disk via Q <rdev> >> >>Then I run dasdfmt with a -k parameter to preserve a volume serial, it >>complains that there is no volume serial on the disk. >>If I run dasdfmt -l volser, it works as expected and sets the volume serial. >>So either I do something wrong or dasdfmt can set but not read the volume >>serial. >>Any ideas ? >>It is RHEL 5.6 >> >>Thank you >> >> > ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
