Re: Adding DASD to a btrfs
Hej Mark, On 13:04 Sat 15 Aug , Mark Post wrote: On 8/14/2015 at 10:49 AM, Benjamin Block bbl...@linux.vnet.ibm.com wrote: In my case the system would not boot anymore because the second DASD was still masked by cio-ignores and the kernel couldn't build the btrfs (no support for degraded raids). I have not found a solution that would cover this out-of-the-box in SLES 12 (that included rebuilding the initrd loaded by zipl and the one loaded by grub2). The dependency tracking doesn't seem to take btrf-volumes into account. It looks like after adding the additional DASD volume to the file system with btrfs device add the proper incantation is grub2-install. After that, rebooting the system works just fine. Just make sure you use YaST, or the dasd_configure command to bring the new DASD volumes online initially. Simply using chccwdev -e won't cause the udev rule(s) to be written, nor will it update /boot/zipl/active_devices.txt. I will try this as soon as I get a chance to. The test-system from back then is a bit different right now. I am pretty sure I used dasd_configure to activate the dasd and I definitly used the btrfs command, but I may have missed the call to grub2-install. Thanks. Beste Grüße / Best regards, - Benjamin Block -- Linux on z Systems Development / IBM Systems Technology Group IBM Deutschland Research Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp / Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- 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: Adding DASD to a btrfs
Hej Mark, On 10:27 Sun 16 Aug , Mark Post wrote: On 8/15/2015 at 07:35 PM, Frank M. Ramaekers framaek...@ailife.com wrote: I was looking how to do the initrd zipl, but got lost: ls -l /etc/zipl.conf ls: cannot access /etc/zipl.conf: No such file or directory zipl -V Using config file '/etc/zipl.conf' Error: Config file '/etc/zipl.conf': No such file or directory ls -l /etc/dasd.conf ls: cannot access /etc/dasd.conf: No such file or directory Starting with SLES12, we're using grub2 as the boot loader. As on other architectures this means that the boot loader is able to look at what's under /boot and build a list of kernels to boot from. We still use zipl behind the scenes to enable the kernel that runs grub2 to get started, but there should be little to no need for customers to run it any more. So, we no longer have a /etc/zipl.conf file. We've never had a /etc/dasd.conf file. The problem I have encountered with this is, while I don't need the old zipl configuration and new kernels can be added to grub2 (which works very well), in case the root-fs changes in any way (like in this case with adding a second device to the root btrfs-fs, or lets say an other LUN in an zfcp setup) this also means the initrd that zipl loads has to be changed - because otherwise it won't be able to initialize the grub2-emulation properly because that is also resident on said root fs. If you use the provided tools to add and remove DASD, then things should just work [tm] for you. Those tools being YaST, and dasd_configure. If used, they create the necessary udev rules and update /boot/zipl/active_devices.txt to exclude devices from the cio_ignore list. (For virtualized environments, we don't recommend blacklisting devices in the first place, but blacklisting somehow became the default for SLES12. :( ) Its worth nothing if those changes (udev and un-ignoring) are not pulled into the environment available for the grub2-emulation, and because they reside on the root-fs that we change they are not unless they are pulled into said initrd. It wouldn't do this for me when I experimented last Friday with the LVM setup (I checked the time-stamps under /boot/zipl/), I had to invoke those updates myself (`update-bootloader --reinit` did the trick for me). The documentation for SLES12 is at https://www.suse.com/documentation/sles-12/ . If I am assuming wrong things here then pls correct me, this is just what I found while experimenting with it. I haven't found anything regarding addition of btrfs-devices using built-in tools in the documentation. Beste Grüße / Best regards, - Benjamin Block -- Linux on z Systems Development / IBM Systems Technology Group IBM Deutschland Research Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp / Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- 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: Adding DASD to a btrfs
Hej Frank, On 18:35 Sat 15 Aug , Frank M. Ramaekers wrote: Well, performed reinstall and got SLES 12 to us LVM, added a volume and expanded the volume group: --- Volume group --- VG Name system System ID Formatlvm2 Metadata Areas2 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV0 Cur LV1 Open LV 1 Max PV0 Cur PV2 Act PV2 VG Size 13.55 GiB PE Size 4.00 MiB Total PE 3470 Alloc PE / Size 1709 / 6.68 GiB Free PE / Size 1761 / 6.88 GiB VG UUID 8kTik4-y2B1-gjVd-E8ec-Hodg-06MI-aQPkrm Haven't expanded the LV yet, but I was looking how to do the initrd zipl, but got lost: ls -l /etc/zipl.conf ls: cannot access /etc/zipl.conf: No such file or directory zipl -V Using config file '/etc/zipl.conf' Error: Config file '/etc/zipl.conf': No such file or directory ls -l /etc/dasd.conf ls: cannot access /etc/dasd.conf: No such file or directory I don't think you have to touch any configuration files yourself :) As Mark also said, if you stick to yast and dasd_configure to first add the second dasd to your system-configuration and then yast to expand the LVM (as described in the documentation I linked you) it should take care of most everything for you. The only thing left that I had to do after those steps was to invoke the 2 commands I wrote you in the last mail (update-bootloader, dracut, with their arguments). There really should be no need for you to touch any configuration file for this. I am sry If my text on that was a bit confusing (it was already quite late for me on friday). If there are any other Suse specific things I am missing here, then Mark is probably better able to help. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ap-s390info.html#ap-s390info-Adding_DASDs-Persistently_setting_online (but this is a Red Hat manual, different in Suse?) Beste Grüße / Best regards, - Benjamin Block -- Linux on z Systems Development / IBM Systems Technology Group IBM Deutschland Research Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp / Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- 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: Use zedc from within zLinux ?
Thank's, will notify this for future use ! BR /Tore Tore Agblad zOpen Teamleader IT Services Volvo Group Headquarters Corporate Process IT SE-405 08, Gothenburg Sweden E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Utz Bacher Sent: den 14 augusti 2015 8:48 To: LINUX-390@VM.MARIST.EDU Subject: Re: Use zedc from within zLinux ? Agblad Tore wrote on 14.08.2015 15:14:49: Anyone knows if this is possible yet ? As I understand it's advertised to be available, but when ? SLES12 has got the kernel support already, as will an upcoming RHEL 7 release. Java can make use of this (some restrictions apply -- only useful for larger chunks of data, setting buffer sizes on the constructor for java.util.zip helps there) with the latest release as of April or May Regards, Utz :wq -- 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: Use zedc from within zLinux ?
Thank's ! Only problem now we don't have the card installed in our current z12 boxes :-( New z13 is planned, but not scheduled yet. Tore Agblad zOpen Teamleader IT Services Volvo Group Headquarters Corporate Process IT Dept. DE94230 Assar Gabrielssons väg 9 SE-405 08, Gothenburg Sweden Soft Phone: +46 313086198 Telephone: +46-31-3233569 E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Sebastian Ott Sent: den 14 augusti 2015 3:50 To: LINUX-390@VM.MARIST.EDU Subject: Re: Use zedc from within zLinux ? On Fri, 14 Aug 2015, Agblad Tore wrote: Anyone knows if this is possible yet ? zEDC can be used from within Linux with the genwqe device driver. genwqe is available in RHEL7.1 and SLES12. Details can be found here: https://www.ibm.com/developerworks/community/files/form/anonymous/api/library/f57fde24-5f30-4295-91fb-e612c6a7a75a/document/84c8bd13-0402-4540-b2f3-b6362a81e53a/media/GenWQE-GZIP-for-Linux-Doc.pdf Regards, Sebastian As I understand it's advertised to be available, but when ? BR /Tore Tore Agblad zOpen Teamleader IT Services Volvo Group Headquarters Corporate Process IT Dept. DE94230 Assar Gabrielssons väg 9 SE-405 08, Gothenburg Sweden Soft Phone: +46 313086198 Telephone: +46-31-3233569 E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Barton Robinson Sent: den 22 mars 2012 10:35 To: LINUX-390@VM.MARIST.EDU Subject: Re: New book: Linux Health Checker 1.0 User's Guide It's called zTUNE. http://velocitysoftware.com/zztune.html; Michel Beaulieu wrote: Hello Linux-390, I know this is the LINUX-390 list, However, let me ask: Do we have any equivalent System Health Checker for z/VM? Michel Beaulieu IBM SO-Delivery (Canada) -- 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/ -- 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/ -- 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/
Ubuntu Distribution Announced for LinuxONE(TM) and IBM z Systems
Morning, all. It appears that we will have Ubuntu Linux joining RedHat and SuSE in supporting Linux on the mainframe. http://mainframeinsights.com/ubuntu-distribution-announced-for-linuxone-and-ibm-z-systems Have a good one, too. DJ -- Dave Jones Houston, TX 281.578.7544 -- 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/
zFCP and NPIV - limit of 32
Hi! I have been told a long time ago that there was a limit of number of wwpns one may/should have per FCP channel. And it was “32”. Many times I’ve tried to find more information on this and what I found is: - it’s not a hard limit rather a rule - it’s not mainframe's thing but rather fabric's, where switches don’t have enough fast cpus to serve more than 32 nodes on one port - it will work with more than 32 but when channel goes down (for example for service) and then it comes back and all these nodes will try register to the fabric at the same time, things go bad If that’s is the case ….. why power7 and power8 officially can have up to 64 nodes per channel!? (That’s what I was told by AIX admins) But anyway, here is my real question. Can I have more (many more) wwpns and devices per FCP channel but use only up to 32 and I will be fine. It seems to be all good if my findings were true. I mean, switch doesn’t even know about a specific wwpn if it doesn’t initiate a connection. In other words, it is a limit/rule of 32 active nodes or defined wwpns. The point is to have wwpns “reserved” for live guest relocation without wasting them if not used. For example let’s assume we have two not shared FCP channels. One for each LPAR and: LPAR A 32 virtual machines using 32 FCP devices 32 FREE FCP devices reserved for LGR from LPAR B LPAR B 32 virtual machines using 32 FCP devices 32 FREE FCP devices reserved for LGR from LPAR A I just want to give storage people all possible wwpns a specific host will be using and might use if ever will be relocated. In the same time, I don’t want to waste wwpns from precious '32' Of course I know about all the requirements for LGR like device addresses, fabric zones etc. I hope this makes sense. Thanks for any input! Gregory Powiedziuk -- 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: Moving on
Congratulations, Mike!! Regards, Len Leonard J. Santalucia CTO | Business Development Manager | Certified Specialist Vicom Infinity, Inc. IBM Premier Business Partner One Penn Plaza - Suite 2010 New York, New York 10119 Office804-918-3728 Cell…….917-856-4493 eFax413-622-1229 vText……… 9178564...@vtext.com My Blog http://www.infinite-blue.com/blog/ Vicom Infinity http://www.vicominfinity.com Vicom Computer Services http://www.vicomnet.com/ Infinity Systems http://www.infinite-blue.com -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael MacIsaac Sent: Monday, August 17, 2015 10:43 AM To: LINUX-390@VM.MARIST.EDU Subject: Moving on Hello lists, I have again started a new job, moving on from Innovation Data Processing to ADP. At Innovation, helping to roll out the FDRPASVM product that allows you to migrate running Linux and z/VM systems to new DASD regardless of manufacturer was a challenging and satisfying project. However, most of that work was winding down. As ADP has a continually growing z/VM and Linux environment, they should keep me busy for many years to come. I look forward to this new role. -Mike MacIsaac -- 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: Moving on
congrats! On 08/17/2015 10:43 AM, Michael MacIsaac wrote: I have again started a new job, moving on from Innovation Data Processing to ADP. At Innovation, helping to roll out the FDRPASVM product that allows you to migrate running Linux and z/VM systems to new DASD regardless of manufacturer was a challenging and satisfying project. However, most of that work was winding down. As ADP has a continually growing z/VM and Linux environment, they should keep me busy for many years to come. I look forward to this new role. -Mike MacIsaac -- 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: Adding DASD to a btrfs
On 12:29 Mon 17 Aug , Benjamin Block wrote: Hej Mark, On 13:04 Sat 15 Aug , Mark Post wrote: On 8/14/2015 at 10:49 AM, Benjamin Block bbl...@linux.vnet.ibm.com wrote: In my case the system would not boot anymore because the second DASD was still masked by cio-ignores and the kernel couldn't build the btrfs (no support for degraded raids). I have not found a solution that would cover this out-of-the-box in SLES 12 (that included rebuilding the initrd loaded by zipl and the one loaded by grub2). The dependency tracking doesn't seem to take btrf-volumes into account. It looks like after adding the additional DASD volume to the file system with btrfs device add the proper incantation is grub2-install. After that, rebooting the system works just fine. Just make sure you use YaST, or the dasd_configure command to bring the new DASD volumes online initially. Simply using chccwdev -e won't cause the udev rule(s) to be written, nor will it update /boot/zipl/active_devices.txt. I will try this as soon as I get a chance to. The test-system from back then is a bit different right now. I am pretty sure I used dasd_configure to activate the dasd and I definitly used the btrfs command, but I may have missed the call to grub2-install. Just to follow up on that. I just gave it a try and that still doesn't cut it completely. You still have to update the initrd of the kernel you want to use, otherwise the system remains un-bootable. Which means, if you use the feature, you have to do the same steps as I have wrote for the LVM example: update the zipl-initrd (grub2-install, update-bootloader) and update the kernel-initrd (dracut, mkinitrd). Plus ofc using dasd_configure, as you have said, to activate the DASD in the first place. If you, for some reason, end up with an un-bootable system because you missed something, you might try to specify the additional DASD manually with the IPL. E.g.: if you added DASD 0.0.e10b in addition to the original DASD that you have used during installation (lets say 0.0.e109) try the IPL with [1]: #cp ipl e109 parm rd.dasd=0.0.e10b This should at least get you back into the system, but you'll still have to update the said parts. [1] - http://www.ibm.com/developerworks/linux/linux390/documentation_suse.html#sles12 - Device Drivers Book - Chp. 5 Beste Grüße / Best regards, - Benjamin Block -- Linux on z Systems Development / IBM Systems Technology Group IBM Deutschland Research Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp / Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- 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/
Moving on
Hello lists, I have again started a new job, moving on from Innovation Data Processing to ADP. At Innovation, helping to roll out the FDRPASVM product that allows you to migrate running Linux and z/VM systems to new DASD regardless of manufacturer was a challenging and satisfying project. However, most of that work was winding down. As ADP has a continually growing z/VM and Linux environment, they should keep me busy for many years to come. I look forward to this new role. -Mike MacIsaac -- 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: detaching dasd attached to a guest
On 8/14/2015 at 11:37 PM, Cameron Seay cws...@gmail.com wrote: Help me out here, Neale.. I'm not clear about what I am trying to find out. The sequence I followed was: attach 203E, 203F, 2107 *; cpfmtxa 203E, 203F, 2107; format 000 end; detach all the disks; edited the extent control file; rlde extent control; I think the following line is where you're getting into trouble. If you're going to be using dirmaint, _use_ dirmaint. Don't manually edit the user directory entry. Use the dirmaint commands to add space to the guest. Doing anything else is just going to cause problems. edit the direct enttry for the guest attaching the formatted dasd to it. 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: Moving on
On 8/17/2015 at 10:43 AM, Michael MacIsaac mike99...@gmail.com wrote: Hello lists, I have again started a new job, moving on from Innovation Data Processing to ADP. It's starting to get difficult to keep track of you lately. After 30 years in one place, now you're job hopping. :) I hope things work well for both ADP and you. 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: Adding DASD to a btrfs
Hej Frank, On 10:04 Mon 17 Aug , Frank M. Ramaekers wrote: Yes, that helped me to get it up: #cp ipl 100 parm rd.dasd=0.0.0102,0.0.0103 Then: Grub2-install But: # update-bootloader --refresh Perl-Bootloader: 2015-08-17 10:01:33 3 pbl-1212.2 Core::GRUB2::GrubDev2UnixDev.252: Error: did not find a match for hd0 in the device map # update-bootloader --reinit Perl-Bootloader: 2015-08-17 10:01:57 3 pbl-1301.2 Core::GRUB2::GrubDev2UnixDev.252: Error: did not find a match for hd0 in the device map Yes, I get that message too, but it doesn't seem to matter (I find that also very strange). Pls check if the timestamps of the most recent initrd under /boot/zipl change, that should be enough - its enough for me (like said, you don't have to/should not touch anything there). Also, I may have been a bit confusing again, you only have to run on of each command. So you may just run: $ grub2-install $ mkinitrd Or the commands I wrote to you in one of my previous eMails. As best as I know that should make no difference. If you have run those commands after you added the 2. DASD to your system and to your LVM with Yast (or, as I have discussed with mark, to btrfs with the respective commands) the system should boot without any IPL trickery. Frank M. Ramaekers Jr. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Benjamin Block Sent: Monday, August 17, 2015 8:42 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a btrfs Just to follow up on that. I just gave it a try and that still doesn't cut it completely. You still have to update the initrd of the kernel you want to use, otherwise the system remains un-bootable. Which means, if you use the feature, you have to do the same steps as I have wrote for the LVM example: update the zipl-initrd (grub2-install, update-bootloader) and update the kernel-initrd (dracut, mkinitrd). Plus ofc using dasd_configure, as you have said, to activate the DASD in the first place. If you, for some reason, end up with an un-bootable system because you missed something, you might try to specify the additional DASD manually with the IPL. E.g.: if you added DASD 0.0.e10b in addition to the original DASD that you have used during installation (lets say 0.0.e109) try the IPL with [1]: #cp ipl e109 parm rd.dasd=0.0.e10b This should at least get you back into the system, but you'll still have to update the said parts. [1] - http://www.ibm.com/developerworks/linux/linux390/documentation_suse.html#sles12 - Device Drivers Book - Chp. 5 Beste Grüße / Best regards, - Benjamin Block -- Linux on z Systems Development / IBM Systems Technology Group IBM Deutschland Research Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp / Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- 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: detaching dasd attached to a guest
On 8/15/2015 at 12:29 AM, Cameron Seay cws...@gmail.com wrote: DASD 203E CP SYSTEM ZOSA0E 0 Ready; T=0.01/0.01 18:23:37 But I don't like the look of that; shouldn't it say LNX104? The guest it is attached to is LNX004. We have been labeling the MOD-9 where the OS lives the same as the guest, So when I ask Q 2314 I get: DASD 2314 CP SYSTEM LNX004 1 Ready; T=0.01/0.01 18:27:44 Which is fine. The dasd we add to guest LNX004 is labeled in sequence LNX104, LNX204, etc. It may be wrong on our spreadsheet. Hi, Cameron, Part of the problem (for me at least) is that you're using the word attach(ed) which in the z/VM context has a specific meaning. What you're doing is not ATTACHing a DASD volume to a guest, you're giving it one or more minidisks out of a pool of DASD ATTACHed to SYSTEM. Assuming that you are 100% sure that you assigned a label of LNX104 to that volume, then you're right to be concerned. To be on the safe side I will just find some free dasd to add to the guest in question and fix it later. We have a production zOS guest with a lot of MOD-9s attached to it and I don't want to mess it up. And as you say, this is why you should be concerned. (Thinking out loud for anyone else out there that's new to this stuff.) How many people have access to the MAINT userid besides you? Or have rights to change stuff in dirmaint? Everyone needs to be talking about what they're doing so they don't trip up someone else. I will get my part time sysprog to make sure I am re-attaching the correct disks. We are okay for now. We are not in a crunch for dasd yet, and I want to err on the side of caution. There's that word attach again, which can be very confusing. I would say that your labeling scheme is a little unwieldy in the long run. DASD volumes are going to get used, released, re-used, etc. Since you're using dirmaint, labeling them to indicate what guest is going to be using them is going to lead to extra work. If that extra work doesn't get done, the labels are going to become meaningless as time goes on. Let dirmaint do its job and you'll be happier in the long run. 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: Adding DASD to a guest
On 8/15/2015 at 10:17 PM, Don Williams donbwms.foru...@gmail.com wrote: What was the reason, the VM designers chose VARY ON and DEATTACH CYL 0? I would say for the same reason a lot of decisions got made, way back when. Sharing DASD between disparate operating systems wasn't particularly top of mind to the developers. As Alan is always saying, if you think a change in behavior makes sense, a request for enhancement to IBM would be the best route to follow. 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: Moving on
Congratulations Mike! ADP is a company I admire very much, you will have fun working there. On Aug 17, 2015 11:49, Leonard Santalucia lsantalu...@vicominfinity.com wrote: Congratulations, Mike!! Regards, Len Leonard J. Santalucia CTO | Business Development Manager | Certified Specialist Vicom Infinity, Inc. IBM Premier Business Partner One Penn Plaza - Suite 2010 New York, New York 10119 Office804-918-3728 Cell…….917-856-4493 eFax413-622-1229 vText……… 9178564...@vtext.com My Blog http://www.infinite-blue.com/blog/ Vicom Infinity http://www.vicominfinity.com Vicom Computer Services http://www.vicomnet.com/ Infinity Systems http://www.infinite-blue.com -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael MacIsaac Sent: Monday, August 17, 2015 10:43 AM To: LINUX-390@VM.MARIST.EDU Subject: Moving on Hello lists, I have again started a new job, moving on from Innovation Data Processing to ADP. At Innovation, helping to roll out the FDRPASVM product that allows you to migrate running Linux and z/VM systems to new DASD regardless of manufacturer was a challenging and satisfying project. However, most of that work was winding down. As ADP has a continually growing z/VM and Linux environment, they should keep me busy for many years to come. I look forward to this new role. -Mike MacIsaac -- 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: Adding DASD to a btrfs
Yes, that helped me to get it up: #cp ipl 100 parm rd.dasd=0.0.0102,0.0.0103 Then: Grub2-install But: # update-bootloader --refresh Perl-Bootloader: 2015-08-17 10:01:33 3 pbl-1212.2 Core::GRUB2::GrubDev2UnixDev.252: Error: did not find a match for hd0 in the device map # update-bootloader --reinit Perl-Bootloader: 2015-08-17 10:01:57 3 pbl-1301.2 Core::GRUB2::GrubDev2UnixDev.252: Error: did not find a match for hd0 in the device map Frank M. Ramaekers Jr. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Benjamin Block Sent: Monday, August 17, 2015 8:42 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a btrfs On 12:29 Mon 17 Aug , Benjamin Block wrote: Hej Mark, On 13:04 Sat 15 Aug , Mark Post wrote: On 8/14/2015 at 10:49 AM, Benjamin Block bbl...@linux.vnet.ibm.com wrote: In my case the system would not boot anymore because the second DASD was still masked by cio-ignores and the kernel couldn't build the btrfs (no support for degraded raids). I have not found a solution that would cover this out-of-the-box in SLES 12 (that included rebuilding the initrd loaded by zipl and the one loaded by grub2). The dependency tracking doesn't seem to take btrf-volumes into account. It looks like after adding the additional DASD volume to the file system with btrfs device add the proper incantation is grub2-install. After that, rebooting the system works just fine. Just make sure you use YaST, or the dasd_configure command to bring the new DASD volumes online initially. Simply using chccwdev -e won't cause the udev rule(s) to be written, nor will it update /boot/zipl/active_devices.txt. I will try this as soon as I get a chance to. The test-system from back then is a bit different right now. I am pretty sure I used dasd_configure to activate the dasd and I definitly used the btrfs command, but I may have missed the call to grub2-install. Just to follow up on that. I just gave it a try and that still doesn't cut it completely. You still have to update the initrd of the kernel you want to use, otherwise the system remains un-bootable. Which means, if you use the feature, you have to do the same steps as I have wrote for the LVM example: update the zipl-initrd (grub2-install, update-bootloader) and update the kernel-initrd (dracut, mkinitrd). Plus ofc using dasd_configure, as you have said, to activate the DASD in the first place. If you, for some reason, end up with an un-bootable system because you missed something, you might try to specify the additional DASD manually with the IPL. E.g.: if you added DASD 0.0.e10b in addition to the original DASD that you have used during installation (lets say 0.0.e109) try the IPL with [1]: #cp ipl e109 parm rd.dasd=0.0.e10b This should at least get you back into the system, but you'll still have to update the said parts. [1] - http://www.ibm.com/developerworks/linux/linux390/documentation_suse.html#sles12 - Device Drivers Book - Chp. 5 Beste Grüße / Best regards, - Benjamin Block -- Linux on z Systems Development / IBM Systems Technology Group IBM Deutschland Research Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp / Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- 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: zFCP and NPIV - limit of 32
On Monday, 08/17/2015 at 10:33 EDT, Grzegorz Powiedziuk gpowiedz...@gmail.com wrote: If that?s is the case ?.. why power7 and power8 officially can have up to 64 nodes per channel!? (That?s what I was told by AIX admins) The number is now 64 on the z13 with the FICON Express16s cards. The following will be appearing in an upcoming edition of the IOCP book: Limit per FCP FICON FICON channel path (PCHID) Express8s Express16s -- - -- Defined subchannels 420 420 Active NPIV subchannels 32 64 Connected remote N_Ports5121024 Concurrent I/Os 9601528 Open LUNs (per feature)40968192 Can I have more (many more) wwpns and devices per FCP channel but use only up to 32 and I will be fine. The limit of 32 is on the number of active NPIV subchannels, not the number of active connections being used by a given NPIV subchannel. From an LGR perspective, you will want to set a unique EQID for a matched set of FCP pchids on system A and B. This will ensure that LGR won't overload any one FCP path. The 32/64 limit is a soft limit, an IBM recommendation. That is, it's up to you how far you want to push the envelope with respect to error recovery. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- 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: detaching dasd attached to a guest
On Monday, 08/17/2015 at 12:44 EDT, Mark Post mp...@suse.com wrote: Part of the problem (for me at least) is that you're using the word attach(ed) which in the z/VM context has a specific meaning. What you're doing is not ATTACHing a DASD volume to a guest, you're giving it one or more minidisks out of a pool of DASD ATTACHed to SYSTEM. When I teach VM, the first thing I do is insist on use of correct terminology. Failure to abide simply results in confusion later on down the line. To help, just keep seven simple rules in mind: 1. A virtual machine may not directly use real devices; it may use only virtual devices. 2. Virtual devices can be simulated, emulated, or dedicated. 3. Virtual devices are generally created by the CP DEFINE (simulated, emulated), LINK (emulated), and ATTACH (dedicated) commands. 4. The directory has statements that do the same things as DEFINE, LINK, and ATTACH. 5. Class B users MUST use QUERY VIRTUAL device when they want to know about virtual devices. 6. Class B users MUST use QUERY device when they want to know about real devices. 7. CP can't read your mind. Glossary o A simulated device exists only within CP. Ex: PRT, PUN, RDR, NIC, VDISK. o An emulated device converts the semantics of virtual device A to those of real device B. Device B is instantiated outside of CP. Ex: EDEVICE, minidisk, crypto, guest console. o A dedicated device exists only outside of CP. With few exceptions, the virtual machine has access to all of the native capabilities of the device. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- 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: zFCP and NPIV - limit of 32
On Aug 17, 2015, at 11:10 AM, Alan Altmark alan_altm...@us.ibm.com wrote: On Monday, 08/17/2015 at 10:33 EDT, Grzegorz Powiedziuk gpowiedz...@gmail.com wrote: If that?s is the case ?.. why power7 and power8 officially can have up to 64 nodes per channel!? (That?s what I was told by AIX admins) The number is now 64 on the z13 with the FICON Express16s cards. The following will be appearing in an upcoming edition of the IOCP book: Bummer .. we run zec12 :( so I guess it is 32. Can I have more (many more) wwpns and devices per FCP channel but use only up to 32 and I will be fine. The limit of 32 is on the number of active NPIV subchannels, not the number of active connections being used by a given NPIV sub channel. active NPIV subchannels - what exactly does it mean? If NPIV device just sits there in z/VM as “FREE” not attached to anything, is it considered to be active NPIV sub channel? I guess it is but I want to make it clear. If yes than I shouldn’t be doing what've asked about and I have my answer. From an LGR perspective, you will want to set a unique EQID for a matched set of FCP pchids on system A and B. This will ensure that LGR won't overload any one FCP path. I thought that EQUID is there so the z/vm knows which FCP device it should pick from a target system when machine is being LGR-ed. I am not sure if I understand what you meant with overloading or not overloading. I mean without EQUID it wouldn’t even LGR a virtual machine. Can you elaborate that? The 32/64 limit is a soft limit, an IBM recommendation. That is, it's up to you how far you want to push the envelope with respect to error recovery. Thanks Alan! I will definitely keep it safe. Gregory Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- 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: Moving on
Congratulations Mike! We will need to reinstate a moving on list just for you. David div Original message /divdivFrom: Michael MacIsaac mike99...@gmail.com /divdivDate:08-17-2015 11:43 (GMT-04:00) /divdivTo: LINUX-390@VM.MARIST.EDU /divdivSubject: Moving on /divdiv /divHello lists, I have again started a new job, moving on from Innovation Data Processing to ADP. At Innovation, helping to roll out the FDRPASVM product that allows you to migrate running Linux and z/VM systems to new DASD regardless of manufacturer was a challenging and satisfying project. However, most of that work was winding down. As ADP has a continually growing z/VM and Linux environment, they should keep me busy for many years to come. I look forward to this new role. -Mike MacIsaac -- 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: Moving on
Congrats and good luck on your new job Mike... I have again started a new job, moving on from Innovation Data Processing to ADP. At Innovation, helping to roll out the FDRPASVM product that allows you to migrate running Linux and z/VM systems to new DASD regardless of manufacturer was a challenging and satisfying project. However, most of that work was winding down. As ADP has a continually growing z/VM and Linux environment, they should keep me busy for many years to come. I look forward to this new role. -Mike MacIsaac -- 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: Ubuntu Distribution Announced for LinuxONE(TM) and IBM z Systems
On 8/17/2015 at 08:48 AM, Dave Jones d...@vsoft-software.com wrote: Morning, all. It appears that we will have Ubuntu Linux joining RedHat and SuSE in supporting Linux on the mainframe. http://mainframeinsights.com/ubuntu-distribution-announced-for-linuxone-and- ibm-z-systems Interesting. I wonder if we'll start seeing them at SHARE. 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: zFCP and NPIV - limit of 32
On Monday, 08/17/2015 at 03:04 EDT, Grzegorz Powiedziuk gpowiedz...@gmail.com wrote: On Aug 17, 2015, at 11:10 AM, Alan Altmark alan_altm...@us.ibm.com wrote: The limit of 32 is on the number of active NPIV subchannels, not the number of active connections being used by a given NPIV sub channel. active NPIV subchannels - what exactly does it mean? If NPIV device just sits there in z/VM as ?FREE? not attached to anything, is it considered to be active NPIV sub channel? I guess it is but I want to make it clear. If yes than I shouldn?t be doing what've asked about and I have my answer. An active NPIV subchannel is one that is attached to a guest and is being used, or one that is part of an EDEVICE. I thought that EQUID is there so the z/vm knows which FCP device it should pick from a target system when machine is being LGR-ed. I am not sure if I understand what you meant with overloading or not overloading. I mean without EQUID it wouldn?t even LGR a virtual machine. Can you elaborate that? The EQID allows CP to select an available equivalent device from the target system, where equivalent is defined to mean with the same EQID and device type. Let's assume that you have a) Ten (10) FCP paths on system A and B, and each path has 100 NPIV-enabled subchannels defined on it, for a total of 1000 NPIV-enabled subchannels. b) 100 guests, each using two NPIV-enabled FCP subchannels, for a total of 200 active subchannels. c) You are using seven of your ten FCP paths since you are placing no more than 32 active subchannels on each path. With me so far? Now, if you use EQID PURPLE on those 200 subchannels (on both A and B), you will discover that each path on B will fill to its capacity (100) before CP moves onto the next. That means that if you relocated all 100 guests, CP will be using exactly two paths on the target system. This behavior is a by-product of the fact that devices with the same EQID are consumed in device address order. No load balancing is performed. Oops. So to address this, make sure that the EQID assigned to the subchannels on an FCP path is unique to that path. This will keep all the PURPLE subchannels on a single chpid, all the RED ones on another, and all the BLUE ones on a third. (You might consider using an EQID like FCPnnn, where nnn is a sequence number that you assign as you consume FCP paths. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- 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/
