Re: VOL1
Here is a little more info about VOL1 capabilities. The official IBM standard only requires 80 bytes, far less than the 512 bytes reserved for MBR. The MBR reservation is common for many filesystems (EXT2/3/4 and others). You can have a VOL1 label while keeping the FS at the front of the disk. It fits. Things continue to work. This is really useful for systems like zPDT because you can 'mount -o loop' the file defining the disk on the host system. Similarly, a PV could be "attached" to Linux on zPDT, happily with VOL1 label. (Same for an LV, of course.) "But wait, there's more!" A physical disk could be attached to Linux on zPDT. (Though not partitioned if stamped VOL1.) Alan said, "Linux could obtain, via IBM channels, an official VOL1 standard version ID." IPL text for FBA DASD also fits in "MBR space". So why CDL? Because it provides a VTOC and flattens the learning curve for MVS shops. (Hence the comment "MVS needs to grow up.") Then what's wrong with CDL? It truncates records at the front of the disk rendering all other uses void. (filesystems, partitioning, PV) The VOL1 standard does not require this; it doesn't mandate end-of-record at 80 bytes. Think about interoperability. VM shops might prefer a CMS reserved file where MVS wants a DS. (The label would be "CMS1". Holy minidisks, Bat Man!) Going extreme ... ISO-9660 (CD-ROM) reserves a whopping 32K. I recall putting a traditional PC partition table at the front of a minidisk with a boot partition following the ISO-9660 FS. -- R; <>< -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
VOL1
We might be in agreement except for your incorrect use of the word "no". On 12/04/2015 08:52 PM, Alan Altmark wrote: >> > MVS should grow up. > No, ... Yes, MVS should grow up. But we'll consider that out of scope for this conversation. Okay? > ... Linux should obey the IBM VOL1 label standard when using ECKD devices, > just like everyone else. In fact, if I were asked (I haven't been), I > would suggest that it use the CPVOLUME format. That's one that MVS > already recognizes, and whose reactions Certain People are expending > effort to improve upon. The objection is to track-and-record behavior in support of CDL. I didn't hear anyone complain about VOL1, and I don't recall complaining about it myself. Reason for rant is the tricks with tracks, which only loosely links with labeling. AS IT HAPPENS, the CPVOLUME form of VOL1 label fits nicely at the front of an EXT2/3/4 filesystem. > Alternatively, Linux could obtain, via IBM channels, an official VOL1 > standard version ID. E.g. one that has zeroes in the VTOC address > indicating no VTOC. So much the better. > If there were no VTOC, then a volumes could be entirely formatted with 4K > records. The label is defined in the VOL1 label standard to be a > *minimum* of 80 bytes. It can be 4096. It's the VTOC that's creates the > problem. Agreed. > All of the OSes would have to recognize it since "version number" is part > of the standard, specifically designed for building interoperable labels. Interoperability is a good thing. -- R; <>< -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: VOL1
Nice.. another version of one of my favorite lines:If you were right I'd agree with you. ;-) Scott Rohling On Mon, Dec 14, 2015 at 9:15 AM, Rick Troth <r...@casita.net> wrote: > We might be in agreement except for your incorrect use of the word "no". > > > On 12/04/2015 08:52 PM, Alan Altmark wrote: > >> > MVS should grow up. > > No, ... > > Yes, MVS should grow up. > But we'll consider that out of scope for this conversation. > Okay? > > > > ... Linux should obey the IBM VOL1 label standard when using ECKD > devices, > > just like everyone else. In fact, if I were asked (I haven't been), I > > would suggest that it use the CPVOLUME format. That's one that MVS > > already recognizes, and whose reactions Certain People are expending > > effort to improve upon. > > The objection is to track-and-record behavior in support of CDL. > I didn't hear anyone complain about VOL1, and I don't recall complaining > about it myself. > Reason for rant is the tricks with tracks, which only loosely links with > labeling. > > AS IT HAPPENS, the CPVOLUME form of VOL1 label fits nicely at the front > of an EXT2/3/4 filesystem. > > > > Alternatively, Linux could obtain, via IBM channels, an official VOL1 > > standard version ID. E.g. one that has zeroes in the VTOC address > > indicating no VTOC. > > So much the better. > > > > If there were no VTOC, then a volumes could be entirely formatted with 4K > > records. The label is defined in the VOL1 label standard to be a > > *minimum* of 80 bytes. It can be 4096. It's the VTOC that's creates the > > problem. > > Agreed. > > > > All of the OSes would have to recognize it since "version number" is part > > of the standard, specifically designed for building interoperable labels. > > Interoperability is a good thing. > > > -- R; <>< > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu 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/ > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
expected Label VOL1 not found
Our zVM version is 5.4. Linux version is SUSE Enterprise Server 11 SP1 running as guest on zVM. I add 2 more dasd for this guest's directory like below: MDISK 0207 3390 0001 END LBE508 MR LNX4VM LNX4VM LNX4VM MDISK 0208 3390 0001 END LBE509 MR LNX4VM LNX4VM LNX4VM On linux, I want create a volume group by these 2 dasd. But system reject creating this volume group. A warning diaglog pop-up showing following messages: Failure occurred during following action: Creating volume group testvg from /dev/dasde /dev/dasdk System error code was: -4010 At the same time, I also found error messages on this guest's console: - dasde: Warning, expected Label VOL1 not found, treating as CDL formated Disk Jan 29 19:12:03 LXCPOB kernel: Warning, expected Label VOL1 not found, treating as CDL formated Disk dasdk: Warning, expected Label VOL1 not found, treating as CDL formated Disk Jan 29 19:12:03 LXCPOB kernel: Warning, expected Label VOL1 not found, treating as CDL formated Disk Anyone has idea about this problem? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: expected Label VOL1 not found
Lu GL Gao, What type of storage are you using? What does lsdasd show? Mike O'Reilly IBM Linux Change Team Lu GL Gao lu...@cn.ibm.com To Sent by: Linux on LINUX-390@vm.marist.edu, 390 Port cc linux-...@vm.mar ist.edu Subject expected Label VOL1 not found 01/29/2013 08:05 AM Please respond to Linux on 390 Port linux-...@vm.mar ist.edu Our zVM version is 5.4. Linux version is SUSE Enterprise Server 11 SP1 running as guest on zVM. I add 2 more dasd for this guest's directory like below: MDISK 0207 3390 0001 END LBE508 MR LNX4VM LNX4VM LNX4VM MDISK 0208 3390 0001 END LBE509 MR LNX4VM LNX4VM LNX4VM On linux, I want create a volume group by these 2 dasd. But system reject creating this volume group. A warning diaglog pop-up showing following messages: Failure occurred during following action: Creating volume group testvg from /dev/dasde /dev/dasdk System error code was: -4010 At the same time, I also found error messages on this guest's console: - dasde: Warning, expected Label VOL1 not found, treating as CDL formated Disk Jan 29 19:12:03 LXCPOB kernel: Warning, expected Label VOL1 not found, treating as CDL formated Disk dasdk: Warning, expected Label VOL1 not found, treating as CDL formated Disk Jan 29 19:12:03 LXCPOB kernel: Warning, expected Label VOL1 not found, treating as CDL formated Disk Anyone has idea about this problem? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ inline: ecblank.gifinline: graycol.gifinline: pic32731.gif
Re: expected Label VOL1 not found
Anyone has idea about this problem? Were the volumes CPFMTXA'd? Mike MacIsaac mikemac at-sign us.ibm.com -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: expected Label VOL1 not found
I add 2 more dasd for this guest's directory like below: MDISK 0207 3390 0001 END LBE508 MR LNX4VM LNX4VM LNX4VM MDISK 0208 3390 0001 END LBE509 MR LNX4VM LNX4VM LNX4VM On linux, I want create a volume group by these 2 dasd. But system reject creating this volume group. A warning diaglog pop-up showing following messages: Failure occurred during following action: Creating volume group testvg from /dev/dasde /dev/dasdk System error code was: -4010 At the same time, I also found error messages on this guest's console: - dasde: Warning, expected Label VOL1 not found, treating as CDL formated Disk Jan 29 19:12:03 LXCPOB kernel: Warning, expected Label VOL1 not found, treating as CDL formated Disk dasdk: Warning, expected Label VOL1 not found, treating as CDL formated Disk Jan 29 19:12:03 LXCPOB kernel: Warning, expected Label VOL1 not found, treating as CDL formated Disk Anyone has idea about this problem? The Linux disk driver probes to determine if there is a valid IBM standard label on any disk device it sees; if not, it falls back to assuming the disk is a CDL formatted disk (a bad assumption IMHO, but then I'd like to see CDL completely go away so we don't have to explain this weirdness to people). All those messages are telling you is that that probe process didn't find a IBM standard label. They're normal for unformatted disks. To get rid of them, you need to format and partition the new disks with fdisk and dasdfmt. Adding the MDISK statement is equivalent to plugging in a brand new blank drive; you still have to format the drive for use with the operating system. If you want to do that outside the Linux environment, use LXFMT (http://www.sinenomine.net/products/vm/lxfmt). Free. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: expected Label VOL1 not found
On 1/29/2013 at 11:39 AM, Michael MacIsaac mike...@us.ibm.com wrote: Were the volumes CPFMTXA'd? They wouldn't have come online to the guest as a minidisk if that had been skipped. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: expected Label VOL1 not found
On 1/29/2013 at 11:05 AM, Lu GL Gao lu...@cn.ibm.com wrote: Our zVM version is 5.4. Linux version is SUSE Enterprise Server 11 SP1 running as guest on zVM. I add 2 more dasd for this guest's directory like below: MDISK 0207 3390 0001 END LBE508 MR LNX4VM LNX4VM LNX4VM MDISK 0208 3390 0001 END LBE509 MR LNX4VM LNX4VM LNX4VM On linux, I want create a volume group by these 2 dasd. But system reject creating this volume group. A warning diaglog pop-up showing following messages: Failure occurred during following action: Creating volume group testvg from /dev/dasde /dev/dasdk System error code was: -4010 Did you run dasdfmt and fdasd against these two disks before trying to use them? Also, did you specific /dev/dasde1 and /dev/dasdk1 instead of /dev/dasde and /dev/dasdk? The correct usage would be /dev/dasde1 and /dev/dasdk1. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: expected Label VOL1 not found
Well, normally one does this: fdasd -a /dev/dasde fdasd -a /dev/dasdk and then pvcreate /dev/dasde1 pvcreate /dev/dasdk1 then create the group out of /dev/dasde1 and /dev/dask1 Marcy -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Lu GL Gao Sent: Tuesday, January 29, 2013 8:06 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] expected Label VOL1 not found Our zVM version is 5.4. Linux version is SUSE Enterprise Server 11 SP1 running as guest on zVM. I add 2 more dasd for this guest's directory like below: MDISK 0207 3390 0001 END LBE508 MR LNX4VM LNX4VM LNX4VM MDISK 0208 3390 0001 END LBE509 MR LNX4VM LNX4VM LNX4VM On linux, I want create a volume group by these 2 dasd. But system reject creating this volume group. A warning diaglog pop-up showing following messages: Failure occurred during following action: Creating volume group testvg from /dev/dasde /dev/dasdk System error code was: -4010 At the same time, I also found error messages on this guest's console: - dasde: Warning, expected Label VOL1 not found, treating as CDL formated Disk Jan 29 19:12:03 LXCPOB kernel: Warning, expected Label VOL1 not found, treating as CDL formated Disk dasdk: Warning, expected Label VOL1 not found, treating as CDL formated Disk Jan 29 19:12:03 LXCPOB kernel: Warning, expected Label VOL1 not found, treating as CDL formated Disk Anyone has idea about this problem? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: expected Label VOL1 not found
Thanks guys! These disks are ECKD 3390-3 dasd on DS8300. Firstly I defined MDISK to that linux guest. Secondly using CPFMTXA utility to format thess dasds at range between cylinder 0 to END. Thirdly boot that linux guest, I didn't use fdisk and dasdfmt, but use YAST - Hardware - DASD - Select target disks - Perform Action - Activate and Format. Lastly adding new volume group. Based on your explanation, I think the high possibility of my problem is that I didn't create partition for every disk before defining new volume group. My YAST steps didn't execute pvcreate operation. So when I added them to volume group, they were still /dev/dasde rather than /dev/dasde1. Thank you again! -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
