HYPERPAV problem RHEL6.5
I must be doing something wrong but I sure don't see it. Has anyone seen this behavior? Thanks Tom Devices dedicated in z/VM directory. DEDICATE B600 B600 DEDICATE B640 B640 DEDICATE B641 B641 DEDICATE B642 B642 DEDICATE B643 B643 From a class B user CP Q PAV Device B600 is a base HyperParallel Access Volume device in Pool 0 Device B640 is an alias HyperParallel Access Volume device in Pool 0 Device B641 is an alias HyperParallel Access Volume device in Pool 0 Device B642 is an alias HyperParallel Access Volume device in Pool 0 Device B643 is an alias HyperParallel Access Volume device in Pool 0 From the z/LINUX virtual machine CP Q V PAV HYPERPAV BASE B600 ON B600 0ZB600 POOL 0 HYPERPAV ALIAS B640 ON B640 POOL 0 HYPERPAV ALIAS B641 ON B641 POOL 0 HYPERPAV ALIAS B642 ON B642 POOL 0 HYPERPAV ALIAS B643 ON B643 POOL 0 Set them online to LINUX chccwdev -e b600,b640-b643 Setting device 0.0.b600 online dasd-eckd 0.0.b600: New DASD 3390/0E (CU 3990/01) with 262668 cylinders, 15 heads, 224 sectors dasd-eckd 0.0.b600: DASD with 4 KB/block, 189120960 KB total size, 48 KB/track, linux disk layout dasdb:(nonl) dasdb1 Done Setting device 0.0.b640 online dasd-eckd 0.0.b640: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done Setting device 0.0.b641 online dasd-eckd 0.0.b641: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done Setting device 0.0.b642 online dasd-eckd 0.0.b642: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done Setting device 0.0.b643 online dasd-eckd 0.0.b643: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done [root@tom128 ~]# As seen by LINUX OS. lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks == 0.0.b640 active ??? : ECKD 0 0.0.b641 active ??? : ECKD 0 0.0.b642 active ??? : ECKD 0 0.0.b643 active ??? : ECKD 0 0.0.0100 active dasda 94:0ECKD 4096 7042MB 1802880 0.0.b600 n/f dasdb 94:4 ECKD [root@tom128 ~]# WHY DOESN'T LINUX SEE THE ALIAS VOLUMES? -- 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: HYPERPAV problem RHEL6.5
On 6/30/2015 at 12:43 PM, Tom Huegel tehue...@gmail.com wrote: I must be doing something wrong but I sure don't see it. Has anyone seen this behavior? Does anything change after you dasdfmt the base volume? If not, then I would assume it's a bug in Linux. 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: HYPERPAV problem RHEL6.5
I have done this 2 ways. For RH, I also update /etc/dasd.conf COMMAND DEF HYPERPAVALIAS 7EE0 FOR BASE 800 MDISK 800 3390 32760 LX7E10 MR READ WRITE MULT COMMAND DEF HYPERPAVALIAS 7EE0 FOR BASE 800 MDISK 800 3390 DEVNO 7E38 MR READ WRITE MULT Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Tom Huegel Sent: Tuesday, June 30, 2015 12:44 PM To: LINUX-390@VM.MARIST.EDU Subject: HYPERPAV problem RHEL6.5 I must be doing something wrong but I sure don't see it. Has anyone seen this behavior? Thanks Tom Devices dedicated in z/VM directory. DEDICATE B600 B600 DEDICATE B640 B640 DEDICATE B641 B641 DEDICATE B642 B642 DEDICATE B643 B643 From a class B user CP Q PAV Device B600 is a base HyperParallel Access Volume device in Pool 0 Device B640 is an alias HyperParallel Access Volume device in Pool 0 Device B641 is an alias HyperParallel Access Volume device in Pool 0 Device B642 is an alias HyperParallel Access Volume device in Pool 0 Device B643 is an alias HyperParallel Access Volume device in Pool 0 From the z/LINUX virtual machine CP Q V PAV HYPERPAV BASE B600 ON B600 0ZB600 POOL 0 HYPERPAV ALIAS B640 ON B640 POOL 0 HYPERPAV ALIAS B641 ON B641 POOL 0 HYPERPAV ALIAS B642 ON B642 POOL 0 HYPERPAV ALIAS B643 ON B643 POOL 0 Set them online to LINUX chccwdev -e b600,b640-b643 Setting device 0.0.b600 online dasd-eckd 0.0.b600: New DASD 3390/0E (CU 3990/01) with 262668 cylinders, 15 heads, 224 sectors dasd-eckd 0.0.b600: DASD with 4 KB/block, 189120960 KB total size, 48 KB/track, linux disk layout dasdb:(nonl) dasdb1 Done Setting device 0.0.b640 online dasd-eckd 0.0.b640: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done Setting device 0.0.b641 online dasd-eckd 0.0.b641: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done Setting device 0.0.b642 online dasd-eckd 0.0.b642: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done Setting device 0.0.b643 online dasd-eckd 0.0.b643: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done [root@tom128 ~]# As seen by LINUX OS. lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks == 0.0.b640 active ??? : ECKD 0 0.0.b641 active ??? : ECKD 0 0.0.b642 active ??? : ECKD 0 0.0.b643 active ??? : ECKD 0 0.0.0100 active dasda 94:0ECKD 4096 7042MB 1802880 0.0.b600 n/f dasdb 94:4 ECKD [root@tom128 ~]# WHY DOESN'T LINUX SEE THE ALIAS VOLUMES? -- 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/ The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities.
Re: HYPERPAV problem RHEL6.5
Thanks for the responses. My problem was with the sequence of events. I was doing dasdfmt of the base after attaching the devices (base and aliases). Then I thought just chccwdev -d and then chccwdev -e would be enough. What I needed to do was after dasdfmt to attach (detach first if necessary) the aliases. Then I see what I expected. lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks == 0.0.b640 alias ECKD 0.0.b641 alias ECKD 0.0.b642 alias ECKD 0.0.b643 alias ECKD 0.0.0100 active dasda 94:0ECKD 4096 7042MB 1802880 0.0.b600 active dasdb 94:4ECKD 4096 184688MB 47280240 [root@tom128 ~]# dasd-eckd 0.0.b600: SIM - SRC: 62600280 On Tue, Jun 30, 2015 at 9:51 AM, Vitale, Joseph joseph.vit...@bnymellon.com wrote: I have done this 2 ways. For RH, I also update /etc/dasd.conf COMMAND DEF HYPERPAVALIAS 7EE0 FOR BASE 800 MDISK 800 3390 32760 LX7E10 MR READ WRITE MULT COMMAND DEF HYPERPAVALIAS 7EE0 FOR BASE 800 MDISK 800 3390 DEVNO 7E38 MR READ WRITE MULT Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Tom Huegel Sent: Tuesday, June 30, 2015 12:44 PM To: LINUX-390@VM.MARIST.EDU Subject: HYPERPAV problem RHEL6.5 I must be doing something wrong but I sure don't see it. Has anyone seen this behavior? Thanks Tom Devices dedicated in z/VM directory. DEDICATE B600 B600 DEDICATE B640 B640 DEDICATE B641 B641 DEDICATE B642 B642 DEDICATE B643 B643 From a class B user CP Q PAV Device B600 is a base HyperParallel Access Volume device in Pool 0 Device B640 is an alias HyperParallel Access Volume device in Pool 0 Device B641 is an alias HyperParallel Access Volume device in Pool 0 Device B642 is an alias HyperParallel Access Volume device in Pool 0 Device B643 is an alias HyperParallel Access Volume device in Pool 0 From the z/LINUX virtual machine CP Q V PAV HYPERPAV BASE B600 ON B600 0ZB600 POOL 0 HYPERPAV ALIAS B640 ON B640 POOL 0 HYPERPAV ALIAS B641 ON B641 POOL 0 HYPERPAV ALIAS B642 ON B642 POOL 0 HYPERPAV ALIAS B643 ON B643 POOL 0 Set them online to LINUX chccwdev -e b600,b640-b643 Setting device 0.0.b600 online dasd-eckd 0.0.b600: New DASD 3390/0E (CU 3990/01) with 262668 cylinders, 15 heads, 224 sectors dasd-eckd 0.0.b600: DASD with 4 KB/block, 189120960 KB total size, 48 KB/track, linux disk layout dasdb:(nonl) dasdb1 Done Setting device 0.0.b640 online dasd-eckd 0.0.b640: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done Setting device 0.0.b641 online dasd-eckd 0.0.b641: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done Setting device 0.0.b642 online dasd-eckd 0.0.b642: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done Setting device 0.0.b643 online dasd-eckd 0.0.b643: New DASD 3390/0A (CU 3990/01) with 0 cylinders, 0 heads, 0 sectors Done [root@tom128 ~]# As seen by LINUX OS. lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks == 0.0.b640 active ??? : ECKD 0 0.0.b641 active ??? : ECKD 0 0.0.b642 active ??? : ECKD 0 0.0.b643 active ??? : ECKD 0 0.0.0100 active dasda 94:0ECKD 4096 7042MB 1802880 0.0.b600 n/f dasdb 94:4 ECKD [root@tom128 ~]# WHY DOESN'T LINUX SEE THE ALIAS VOLUMES? -- 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/ The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities
