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: 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/
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: 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: 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: Adding DASD to a btrfs
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. 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. :( ) The documentation for SLES12 is at https://www.suse.com/documentation/sles-12/ . 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
Yeah, it should, but it doesn't. First time I rebooted, I got this: Buffer I/O error on device dm-1, logical block 3553264 Buffer I/O error on device dm-1, logical block 3553264 dracut-initqueueÝ331¨: Warning: Could not boot. dracut-initqueueÝ331¨: Warning: /dev/disk/by-uuid/22e98946-97d7-4d32-8e5b-de3f703587d2 does not exist Starting Dracut Emergency Shell... Warning: /dev/disk/by-uuid/22e98946-97d7-4d32-8e5b-de3f703587d2 does not exist Generating /run/initramfs/rdsosreport.txt Buffer I/O error on device dm-1, logical block 3553264 Buffer I/O error on device dm-1, logical block 3553264 Buffer I/O error on device dm-1, logical block 3553264 Buffer I/O error on device dm-1, logical block 3553264 Entering emergency mode. Exit the shell to continue. Type journalctl to view system logs. You might want to save /run/initramfs/rdsosreport.txt to a USB stick or /boot -- The second time, I reinstalled. I was able to expand the VG across 4 3390-9 DASD (I couldn't expand the LV because it would lose It's / configuration). After install, everything looked find, I just had to expand the LV for / to the entire VG. I used VNC and the YAST GUI and expanded the LV, rebooted and dracut-initqueueÝ358¨: ln: failed to create symbolic link '/dev/resume': File exists Buffer I/O error on device dm-2, logical block 7157744 Buffer I/O error on device dm-2, logical block 7157744 dracut-initqueueÝ358¨: Warning: Could not boot. dracut-initqueueÝ358¨: Warning: /dev/disk/by-uuid/2369faea-1f2f-43f7-a284-cdd1610cb042 does not exist Starting Dracut Emergency Shell... Warning: /dev/disk/by-uuid/2369faea-1f2f-43f7-a284-cdd1610cb042 does not exist Generating /run/initramfs/rdsosreport.txt Buffer I/O error on device dm-2, logical block 7157744 Buffer I/O error on device dm-2, logical block 7157744 Buffer I/O error on device dm-2, logical block 7157744 Buffer I/O error on device dm-2, logical block 7157744 Entering emergency mode. Exit the shell to continue. Type journalctl to view system logs. You might want to save /run/initramfs/rdsosreport.txt to a USB stick or /boot after mounting them and attach it to a bug report. dracut:/# Frank M. Ramaekers Jr. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Sunday, August 16, 2015 11:27 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a btrfs 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
Re: Adding DASD to a btrfs
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 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?) Frank M. Ramaekers Jr. -Original Message- From: Benjamin Block [mailto:bbl...@linux.vnet.ibm.com] Sent: Friday, August 14, 2015 2:24 PM To: Frank M. Ramaekers Cc: Linux on 390 Port Subject: Re: Adding DASD to a btrfs Hej Frank, I am also relatively new to z Systems, so I may not know everything, sry for that :) On 11:10 Fri 14 Aug , Frank M. Ramaekers wrote: Well, I'm not married to this (fresh) install, but I do want to be able to expand the root fs when necessary. I'd be willing to re-install if I can create the root fs so that it can be (easily) expanded if necessary. Currently I have only 1 single dasd (in use): Disk /dev/dasdc: cylinders : 10016 tracks per cylinder ..: 15 blocks per track .: 12 bytes per block ..: 4096 volume label .: VOL1 volume serial : max partitions ...: 3 --- tracks --- Device start end length Id System /dev/dasdc1 2 4267 42661 Linux native /dev/dasdc2 4268 150239 1459722 Linux native (dasda and dasd are swap on V-Disk) I have a /dev/dasd (unallocated), also a 3390-9 I could not figure out how to create an expandable fs at install time. I wanted to have: 1)3390-3 with /boot (300MB) and / (for the remaining 2GB) 2)3390-9 with other fs (/usr, /home, /opt, etc.), perhaps LVM (easily expandable?) I just tried a small LVM setup and if you install SUSE 12 it should already give you a working setup out of the box, you just have to tell it to use LVM. After the initial step, as soon as you get into Yast, you get the chance to select a partition setup under the point Suggested Partitioning [1]; if you select Edit Proposal Settings you will have the option to tell it to Create LVM-based Proposal. This will already take care of it (look out that you select the DASD in question on the previous screens). Boot for zipl will be separated and for the rest of the space it will create a single LVM volume group (for swap and /). This default layout is OK for most cases IMHO - in case it isn't you can afterwards still change it by accessing the expert mode, I have not tested this though. Later you can extend this initial volume group with additional disks. That should be straight forward with the help of Yast [2]. Essentially, you will just add the 2., or 3., or n. disk (a partition of those if you want) to the volume group of the original disk that Yast created for you during installation and then you resize the logical volume of / to use the additional space. Additionally the filesystem on / has to be extended, in case of btrfs and Yast this should work out of the box (Yast should take care of it). As *always*, after you change anything regarding the root-fs, you have to rebuild the initrd for zipl and the initrd for you current kernel. This is really important (otherwise your system might be un-bootable)! Something like this should do: update-bootloader --reinit --force dracut --force --host This will work for the most recent kernel installed. I believe that there are some restrictions on what fs can be in LVM (/boot can't for instance...and I had a problem with /lib) Boot (the boot that will include the zipl, the grub2 that SUSE uses should be OK though) can't be in the LVM. It is also important to use an FS that can be dynamically resized (e.g. btfs, xfs.. not lets say fat32 :) ). I am not aware of other restrictions. ...still waiting for: The Virtualization Cookbook for IBM z Systems Volume 3: SUSE Linux Enterprise
Re: Adding DASD to a guest
P.S. For some unknown reason, I was consistently misspelling DETACH On Sat, Aug 15, 2015 at 10:17 PM Don Williams donbwms.foru...@gmail.com wrote: Ouch. I typically work in the z/OS world where there is only VARY. Multiple systems (including systems that are not local VM guests) could have the same DASD device online. Those other systems could re-label the volume while the volume was online to VM but not attached. Then hours later I could attach that device and VM would use stale label information. While technically ATTACH is not varying a device online, it is conceptually close to that. Close enough that I expect many users assume that. What was the reason, the VM designers chose VARY ON and DEATTACH CYL 0? On Sat, Aug 15, 2015 at 9:36 PM Alan Altmark alan_altm...@us.ibm.com wrote: Volume labels are read at VARY ON and any time cylinder 0 is detached from a virtual machine, whether mdisk or dedicated dasd. Alan Altmark Senior Managing Consultant IBM Systems Lab Services Neale Ferguson --- Re: [LINUX-390] Adding DASD to a guest --- From:Neale Ferguson ne...@sinenomine.netTo: LINUX-390@VM.MARIST.EDUDate:Sat, Aug 15, 2015 12:19 PMSubject:Re: [LINUX-390] Adding DASD to a guest I thought vol1 labels were read at vary on time but that may have changed to attach/detach. Try varying the volume off/on and then attaching to the system. Original message From: Cameron Seay Date: 2015/08/15 11:56 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Adding DASD to a guest Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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/
Re: Adding DASD to a guest
Volume labels are read at VARY ON and any time cylinder 0 is detached from a virtual machine, whether mdisk or dedicated dasd. Alan Altmark Senior Managing Consultant IBM Systems Lab Services Neale Ferguson --- Re: [LINUX-390] Adding DASD to a guest --- From:Neale Ferguson ne...@sinenomine.netTo: LINUX-390@VM.MARIST.EDUDate:Sat, Aug 15, 2015 12:19 PMSubject:Re: [LINUX-390] Adding DASD to a guest I thought vol1 labels were read at vary on time but that may have changed to attach/detach. Try varying the volume off/on and then attaching to the system. Original message From: Cameron Seay Date: 2015/08/15 11:56 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Adding DASD to a guest Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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/
Re: Adding DASD to a guest
Ouch. I typically work in the z/OS world where there is only VARY. Multiple systems (including systems that are not local VM guests) could have the same DASD device online. Those other systems could re-label the volume while the volume was online to VM but not attached. Then hours later I could attach that device and VM would use stale label information. While technically ATTACH is not varying a device online, it is conceptually close to that. Close enough that I expect many users assume that. What was the reason, the VM designers chose VARY ON and DEATTACH CYL 0? On Sat, Aug 15, 2015 at 9:36 PM Alan Altmark alan_altm...@us.ibm.com wrote: Volume labels are read at VARY ON and any time cylinder 0 is detached from a virtual machine, whether mdisk or dedicated dasd. Alan Altmark Senior Managing Consultant IBM Systems Lab Services Neale Ferguson --- Re: [LINUX-390] Adding DASD to a guest --- From:Neale Ferguson ne...@sinenomine.netTo: LINUX-390@VM.MARIST.EDUDate:Sat, Aug 15, 2015 12:19 PMSubject:Re: [LINUX-390] Adding DASD to a guest I thought vol1 labels were read at vary on time but that may have changed to attach/detach. Try varying the volume off/on and then attaching to the system. Original message From: Cameron Seay Date: 2015/08/15 11:56 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Adding DASD to a guest Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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/
Re: Adding DASD to a guest
Here is a clue to the problem, I think: I attach volumes 2108-210a to system logged in as MAINT. When I q dasd free, I do not see these disks listed as free. I RLDE the EXTENT CONTROL file and log off MAINT (after I have replaced the user direct file for the guest in question). When I log on to the guest I get the not linked message. When I log back into MAINT and q dasd free, the disks in question are showing free again. This says to me I am not attaching them correctly. Am I on the right track? On Sat, Aug 15, 2015 at 1:12 PM, Don Williams donbwms.foru...@gmail.com wrote: ATTACH to SYSTEM would be the logical time to read the label, since VM would need to validate the label in order to securely process LINK requests. ATTACH to guest would not require validating label. I use to get confused between ATTACHing devices and LINKing minidisks. And the difference between ATTACHing to SYSTEM and to a guest. On Sat, Aug 15, 2015 at 12:52 PM Neale Ferguson ne...@sinenomine.net wrote: I believe he's reformatted the disks and reattached to the system. My q is when does the vol1 get re-read. In the old days it was after using: #CP VARY OFF rdev #CP VARY ON rdev But I seem to recall a change around VM/ESA that caused it to happen at attach time. Original message From: Mark Post mp...@suse.com Date: 2015/08/15 12:31 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding DASD to a guest On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com wrote: Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted Not sure how you're really trying to do this. The not linked message usually comes as a result of a LINK statement in USER DIRECT, not an ATTACH command. The volid ?? not mounted piece normally happens when the DASD volume is not ATTACHed to SYSTEM. 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/ -- 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/ -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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
Yes, you need to ATTACH rdev SYSTEM Original message From: Cameron Seay cws...@gmail.com Date: 2015/08/15 13:32 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding DASD to a guest Here is a clue to the problem, I think: I attach volumes 2108-210a to system logged in as MAINT. When I q dasd free, I do not see these disks listed as free. I RLDE the EXTENT CONTROL file and log off MAINT (after I have replaced the user direct file for the guest in question). When I log on to the guest I get the not linked message. When I log back into MAINT and q dasd free, the disks in question are showing free again. This says to me I am not attaching them correctly. Am I on the right track? On Sat, Aug 15, 2015 at 1:12 PM, Don Williams donbwms.foru...@gmail.com wrote: ATTACH to SYSTEM would be the logical time to read the label, since VM would need to validate the label in order to securely process LINK requests. ATTACH to guest would not require validating label. I use to get confused between ATTACHing devices and LINKing minidisks. And the difference between ATTACHing to SYSTEM and to a guest. On Sat, Aug 15, 2015 at 12:52 PM Neale Ferguson ne...@sinenomine.net wrote: I believe he's reformatted the disks and reattached to the system. My q is when does the vol1 get re-read. In the old days it was after using: #CP VARY OFF rdev #CP VARY ON rdev But I seem to recall a change around VM/ESA that caused it to happen at attach time. Original message From: Mark Post mp...@suse.com Date: 2015/08/15 12:31 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding DASD to a guest On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com wrote: Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted Not sure how you're really trying to do this. The not linked message usually comes as a result of a LINK statement in USER DIRECT, not an ATTACH command. The volid ?? not mounted piece normally happens when the DASD volume is not ATTACHed to SYSTEM. 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/ -- 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/ -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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 guest
When you ATTACH w/o keyword SYSTEM, you are ATTACHing to your guest, MAINT.
When you log off all the ATTACHs to MAINT are DEATTACHed. When you ATTACH
with SYSTEM, the attach is to VM which allows VM to process LINKs to
minidisks on that rdev. When you log off those ATTACHs remain.
On Sat, Aug 15, 2015 at 1:39 PM Neale Ferguson ne...@sinenomine.net wrote:
Yes, you need to ATTACH rdev SYSTEM
Original message
From: Cameron Seay cws...@gmail.com
Date: 2015/08/15 13:32 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
Here is a clue to the problem, I think: I attach volumes 2108-210a to
system logged in as MAINT. When I q dasd free, I do not see these disks
listed as free. I RLDE the EXTENT CONTROL file and log off MAINT (after I
have replaced the user direct file for the guest in question). When I log
on to the guest I get the not linked message. When I log back into MAINT
and q dasd free, the disks in question are showing free again. This says to
me I am not attaching them correctly. Am I on the right track?
On Sat, Aug 15, 2015 at 1:12 PM, Don Williams donbwms.foru...@gmail.com
wrote:
ATTACH to SYSTEM would be the logical time to read the label, since VM
would need to validate the label in order to securely process LINK
requests. ATTACH to guest would not require validating label.
I use to get confused between ATTACHing devices and LINKing minidisks.
And
the difference between ATTACHing to SYSTEM and to a guest.
On Sat, Aug 15, 2015 at 12:52 PM Neale Ferguson ne...@sinenomine.net
wrote:
I believe he's reformatted the disks and reattached to the system. My q
is
when does the vol1 get re-read. In the old days it was after using:
#CP VARY OFF rdev
#CP VARY ON rdev
But I seem to recall a change around VM/ESA that caused it to happen at
attach time.
Original message
From: Mark Post mp...@suse.com
Date: 2015/08/15 12:31 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com wrote:
Any ideas why I'm seeing this? I went through the steps to format,
label
and attach these to guest lnx065...
HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted
HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted
HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted
Not sure how you're really trying to do this. The not linked message
usually comes as a result of a LINK statement in USER DIRECT, not an
ATTACH
command. The volid ?? not mounted piece normally happens when
the
DASD volume is not ATTACHed to SYSTEM.
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/
--
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/
--
Cameron Seay, Ph.D.
Department of Computer Systems Technology
School of Technology
NC A T State University
Greensboro, NC
336 334 7717 x2251
--
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
Re: Adding DASD to a guest
Worked like a charm. Problem solved! Thanks folks! On Sat, Aug 15, 2015 at 1:52 PM, Don Williams donbwms.foru...@gmail.com wrote: When you ATTACH w/o keyword SYSTEM, you are ATTACHing to your guest, MAINT. When you log off all the ATTACHs to MAINT are DEATTACHed. When you ATTACH with SYSTEM, the attach is to VM which allows VM to process LINKs to minidisks on that rdev. When you log off those ATTACHs remain. On Sat, Aug 15, 2015 at 1:39 PM Neale Ferguson ne...@sinenomine.net wrote: Yes, you need to ATTACH rdev SYSTEM Original message From: Cameron Seay cws...@gmail.com Date: 2015/08/15 13:32 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding DASD to a guest Here is a clue to the problem, I think: I attach volumes 2108-210a to system logged in as MAINT. When I q dasd free, I do not see these disks listed as free. I RLDE the EXTENT CONTROL file and log off MAINT (after I have replaced the user direct file for the guest in question). When I log on to the guest I get the not linked message. When I log back into MAINT and q dasd free, the disks in question are showing free again. This says to me I am not attaching them correctly. Am I on the right track? On Sat, Aug 15, 2015 at 1:12 PM, Don Williams donbwms.foru...@gmail.com wrote: ATTACH to SYSTEM would be the logical time to read the label, since VM would need to validate the label in order to securely process LINK requests. ATTACH to guest would not require validating label. I use to get confused between ATTACHing devices and LINKing minidisks. And the difference between ATTACHing to SYSTEM and to a guest. On Sat, Aug 15, 2015 at 12:52 PM Neale Ferguson ne...@sinenomine.net wrote: I believe he's reformatted the disks and reattached to the system. My q is when does the vol1 get re-read. In the old days it was after using: #CP VARY OFF rdev #CP VARY ON rdev But I seem to recall a change around VM/ESA that caused it to happen at attach time. Original message From: Mark Post mp...@suse.com Date: 2015/08/15 12:31 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding DASD to a guest On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com wrote: Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted Not sure how you're really trying to do this. The not linked message usually comes as a result of a LINK statement in USER DIRECT, not an ATTACH command. The volid ?? not mounted piece normally happens when the DASD volume is not ATTACHed to SYSTEM. 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/ -- 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/ -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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
Glad we could help.
On Sat, Aug 15, 2015 at 1:57 PM Cameron Seay cws...@gmail.com wrote:
Worked like a charm. Problem solved! Thanks folks!
On Sat, Aug 15, 2015 at 1:52 PM, Don Williams donbwms.foru...@gmail.com
wrote:
When you ATTACH w/o keyword SYSTEM, you are ATTACHing to your guest,
MAINT.
When you log off all the ATTACHs to MAINT are DEATTACHed. When you ATTACH
with SYSTEM, the attach is to VM which allows VM to process LINKs to
minidisks on that rdev. When you log off those ATTACHs remain.
On Sat, Aug 15, 2015 at 1:39 PM Neale Ferguson ne...@sinenomine.net
wrote:
Yes, you need to ATTACH rdev SYSTEM
Original message
From: Cameron Seay cws...@gmail.com
Date: 2015/08/15 13:32 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
Here is a clue to the problem, I think: I attach volumes 2108-210a to
system logged in as MAINT. When I q dasd free, I do not see these
disks
listed as free. I RLDE the EXTENT CONTROL file and log off MAINT
(after
I
have replaced the user direct file for the guest in question). When I
log
on to the guest I get the not linked message. When I log back into
MAINT
and q dasd free, the disks in question are showing free again. This
says
to
me I am not attaching them correctly. Am I on the right track?
On Sat, Aug 15, 2015 at 1:12 PM, Don Williams
donbwms.foru...@gmail.com
wrote:
ATTACH to SYSTEM would be the logical time to read the label, since
VM
would need to validate the label in order to securely process LINK
requests. ATTACH to guest would not require validating label.
I use to get confused between ATTACHing devices and LINKing
minidisks.
And
the difference between ATTACHing to SYSTEM and to a guest.
On Sat, Aug 15, 2015 at 12:52 PM Neale Ferguson
ne...@sinenomine.net
wrote:
I believe he's reformatted the disks and reattached to the system.
My q
is
when does the vol1 get re-read. In the old days it was after using:
#CP VARY OFF rdev
#CP VARY ON rdev
But I seem to recall a change around VM/ESA that caused it to
happen
at
attach time.
Original message
From: Mark Post mp...@suse.com
Date: 2015/08/15 12:31 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com
wrote:
Any ideas why I'm seeing this? I went through the steps to
format,
label
and attach these to guest lnx065...
HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted
HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted
HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted
Not sure how you're really trying to do this. The not linked
message
usually comes as a result of a LINK statement in USER DIRECT, not
an
ATTACH
command. The volid ?? not mounted piece normally happens
when
the
DASD volume is not ATTACHed to SYSTEM.
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/
--
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/
--
Cameron Seay, Ph.D.
Department of Computer Systems Technology
School of Technology
NC A T State University
Greensboro, NC
336 334 7717 x2251
--
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
Re: Adding DASD to a guest
P.S. In order to do the format you need to attach to your guest. Then
reattach to SYSTEM to allow LINKs to be processed.
On Sat, Aug 15, 2015 at 1:58 PM Don Williams donbwms.foru...@gmail.com
wrote:
Glad we could help.
On Sat, Aug 15, 2015 at 1:57 PM Cameron Seay cws...@gmail.com wrote:
Worked like a charm. Problem solved! Thanks folks!
On Sat, Aug 15, 2015 at 1:52 PM, Don Williams donbwms.foru...@gmail.com
wrote:
When you ATTACH w/o keyword SYSTEM, you are ATTACHing to your guest,
MAINT.
When you log off all the ATTACHs to MAINT are DEATTACHed. When you
ATTACH
with SYSTEM, the attach is to VM which allows VM to process LINKs to
minidisks on that rdev. When you log off those ATTACHs remain.
On Sat, Aug 15, 2015 at 1:39 PM Neale Ferguson ne...@sinenomine.net
wrote:
Yes, you need to ATTACH rdev SYSTEM
Original message
From: Cameron Seay cws...@gmail.com
Date: 2015/08/15 13:32 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
Here is a clue to the problem, I think: I attach volumes 2108-210a to
system logged in as MAINT. When I q dasd free, I do not see these
disks
listed as free. I RLDE the EXTENT CONTROL file and log off MAINT
(after
I
have replaced the user direct file for the guest in question). When I
log
on to the guest I get the not linked message. When I log back into
MAINT
and q dasd free, the disks in question are showing free again. This
says
to
me I am not attaching them correctly. Am I on the right track?
On Sat, Aug 15, 2015 at 1:12 PM, Don Williams
donbwms.foru...@gmail.com
wrote:
ATTACH to SYSTEM would be the logical time to read the label, since
VM
would need to validate the label in order to securely process LINK
requests. ATTACH to guest would not require validating label.
I use to get confused between ATTACHing devices and LINKing
minidisks.
And
the difference between ATTACHing to SYSTEM and to a guest.
On Sat, Aug 15, 2015 at 12:52 PM Neale Ferguson
ne...@sinenomine.net
wrote:
I believe he's reformatted the disks and reattached to the system.
My q
is
when does the vol1 get re-read. In the old days it was after
using:
#CP VARY OFF rdev
#CP VARY ON rdev
But I seem to recall a change around VM/ESA that caused it to
happen
at
attach time.
Original message
From: Mark Post mp...@suse.com
Date: 2015/08/15 12:31 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com
wrote:
Any ideas why I'm seeing this? I went through the steps to
format,
label
and attach these to guest lnx065...
HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted
HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted
HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted
Not sure how you're really trying to do this. The not linked
message
usually comes as a result of a LINK statement in USER DIRECT, not
an
ATTACH
command. The volid ?? not mounted piece normally happens
when
the
DASD volume is not ATTACHed to SYSTEM.
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/
--
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/
--
Cameron Seay, Ph.D.
Department of Computer Systems Technology
School of Technology
NC A T State University
Greensboro, NC
336 334 7717 x2251
Re: Adding DASD to a guest
Got it. VM is GREAT! On Sat, Aug 15, 2015 at 2:01 PM, Don Williams donbwms.foru...@gmail.com wrote: P.S. In order to do the format you need to attach to your guest. Then reattach to SYSTEM to allow LINKs to be processed. On Sat, Aug 15, 2015 at 1:58 PM Don Williams donbwms.foru...@gmail.com wrote: Glad we could help. On Sat, Aug 15, 2015 at 1:57 PM Cameron Seay cws...@gmail.com wrote: Worked like a charm. Problem solved! Thanks folks! On Sat, Aug 15, 2015 at 1:52 PM, Don Williams donbwms.foru...@gmail.com wrote: When you ATTACH w/o keyword SYSTEM, you are ATTACHing to your guest, MAINT. When you log off all the ATTACHs to MAINT are DEATTACHed. When you ATTACH with SYSTEM, the attach is to VM which allows VM to process LINKs to minidisks on that rdev. When you log off those ATTACHs remain. On Sat, Aug 15, 2015 at 1:39 PM Neale Ferguson ne...@sinenomine.net wrote: Yes, you need to ATTACH rdev SYSTEM Original message From: Cameron Seay cws...@gmail.com Date: 2015/08/15 13:32 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding DASD to a guest Here is a clue to the problem, I think: I attach volumes 2108-210a to system logged in as MAINT. When I q dasd free, I do not see these disks listed as free. I RLDE the EXTENT CONTROL file and log off MAINT (after I have replaced the user direct file for the guest in question). When I log on to the guest I get the not linked message. When I log back into MAINT and q dasd free, the disks in question are showing free again. This says to me I am not attaching them correctly. Am I on the right track? On Sat, Aug 15, 2015 at 1:12 PM, Don Williams donbwms.foru...@gmail.com wrote: ATTACH to SYSTEM would be the logical time to read the label, since VM would need to validate the label in order to securely process LINK requests. ATTACH to guest would not require validating label. I use to get confused between ATTACHing devices and LINKing minidisks. And the difference between ATTACHing to SYSTEM and to a guest. On Sat, Aug 15, 2015 at 12:52 PM Neale Ferguson ne...@sinenomine.net wrote: I believe he's reformatted the disks and reattached to the system. My q is when does the vol1 get re-read. In the old days it was after using: #CP VARY OFF rdev #CP VARY ON rdev But I seem to recall a change around VM/ESA that caused it to happen at attach time. Original message From: Mark Post mp...@suse.com Date: 2015/08/15 12:31 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding DASD to a guest On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com wrote: Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted Not sure how you're really trying to do this. The not linked message usually comes as a result of a LINK statement in USER DIRECT, not an ATTACH command. The volid ?? not mounted piece normally happens when the DASD volume is not ATTACHed to SYSTEM. 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/ -- 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
Re: Adding DASD to a btrfs
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. 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
On 8/14/2015 at 10:49 AM, Benjamin Block bbl...@linux.vnet.ibm.com wrote: I have done the same thing on a test vm - adding a second DASD to a existing root-btrfs filesystem. In short: be very cautious. The btrfs-function works as you can find it in various help-texts, but the problem is, you change you root-fs and upon reboot the second DASD has to be whitlisted by the initrds so it can be used - and that is not yet supported afaik, even more so because the default disk-layout places the grub2 onto the same FS, and thus not even grub2 will be able to launch. The initrd will only know about the DASD that you have used initially to install the system. Did you use YaST to activate and dasdfmt the volume? 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
ATTACH to SYSTEM would be the logical time to read the label, since VM would need to validate the label in order to securely process LINK requests. ATTACH to guest would not require validating label. I use to get confused between ATTACHing devices and LINKing minidisks. And the difference between ATTACHing to SYSTEM and to a guest. On Sat, Aug 15, 2015 at 12:52 PM Neale Ferguson ne...@sinenomine.net wrote: I believe he's reformatted the disks and reattached to the system. My q is when does the vol1 get re-read. In the old days it was after using: #CP VARY OFF rdev #CP VARY ON rdev But I seem to recall a change around VM/ESA that caused it to happen at attach time. Original message From: Mark Post mp...@suse.com Date: 2015/08/15 12:31 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding DASD to a guest On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com wrote: Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted Not sure how you're really trying to do this. The not linked message usually comes as a result of a LINK statement in USER DIRECT, not an ATTACH command. The volid ?? not mounted piece normally happens when the DASD volume is not ATTACHed to SYSTEM. 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/ -- 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 guest
I thought vol1 labels were read at vary on time but that may have changed to attach/detach. Try varying the volume off/on and then attaching to the system. Original message From: Cameron Seay cws...@gmail.com Date: 2015/08/15 11:56 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Adding DASD to a guest Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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 guest
what is the command for that? On Sat, Aug 15, 2015 at 12:18 PM, Neale Ferguson ne...@sinenomine.net wrote: I thought vol1 labels were read at vary on time but that may have changed to attach/detach. Try varying the volume off/on and then attaching to the system. Original message From: Cameron Seay cws...@gmail.com Date: 2015/08/15 11:56 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Adding DASD to a guest Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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/ -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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
I believe he's reformatted the disks and reattached to the system. My q is when does the vol1 get re-read. In the old days it was after using: #CP VARY OFF rdev #CP VARY ON rdev But I seem to recall a change around VM/ESA that caused it to happen at attach time. Original message From: Mark Post mp...@suse.com Date: 2015/08/15 12:31 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding DASD to a guest On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com wrote: Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted Not sure how you're really trying to do this. The not linked message usually comes as a result of a LINK statement in USER DIRECT, not an ATTACH command. The volid ?? not mounted piece normally happens when the DASD volume is not ATTACHed to SYSTEM. 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/ -- 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/
Adding DASD to a guest
Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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 11:56 AM, Cameron Seay cws...@gmail.com wrote: Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted Not sure how you're really trying to do this. The not linked message usually comes as a result of a LINK statement in USER DIRECT, not an ATTACH command. The volid ?? not mounted piece normally happens when the DASD volume is not ATTACHed to SYSTEM. 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
I thought vol1 labels were read when to ATTACH dev TO SYSTEM. Once ATTACHed to SYSTEM, then minidisk on that volume would be available to LINK to guests. On Sat, Aug 15, 2015 at 12:31 PM Mark Post mp...@suse.com wrote: On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com wrote: Any ideas why I'm seeing this? I went through the steps to format, label and attach these to guest lnx065... HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted Not sure how you're really trying to do this. The not linked message usually comes as a result of a LINK statement in USER DIRECT, not an ATTACH command. The volid ?? not mounted piece normally happens when the DASD volume is not ATTACHed to SYSTEM. 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/ -- 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 09:08 Thu 13 Aug , Frank M. Ramaekers wrote: I'm new to both SLES (12 in my case) and btrfs. I just recently installed SLES 12 onto a 3390-9 (I had an additional 3390-9, but didn't see a way to combine the two into a single fs). I want to add the other 3390-9 to the btrfs (/) for expansion purposes. I have done the same thing on a test vm - adding a second DASD to a existing root-btrfs filesystem. In short: be very cautious. The btrfs-function works as you can find it in various help-texts, but the problem is, you change you root-fs and upon reboot the second DASD has to be whitlisted by the initrds so it can be used - and that is not yet supported afaik, even more so because the default disk-layout places the grub2 onto the same FS, and thus not even grub2 will be able to launch. The initrd will only know about the DASD that you have used initially to install the system. 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. Unless I missed something I'd advice against it. The official documentation that SUSE provides [1] suggests that LVM and DM-Raid are natively supported by it. [1] - https://www.suse.com/documentation/sles-12/stor_admin/data/stor_admin.html 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, I am also relatively new to z Systems, so I may not know everything, sry for that :) On 11:10 Fri 14 Aug , Frank M. Ramaekers wrote: Well, I'm not married to this (fresh) install, but I do want to be able to expand the root fs when necessary. I'd be willing to re-install if I can create the root fs so that it can be (easily) expanded if necessary. Currently I have only 1 single dasd (in use): Disk /dev/dasdc: cylinders : 10016 tracks per cylinder ..: 15 blocks per track .: 12 bytes per block ..: 4096 volume label .: VOL1 volume serial : max partitions ...: 3 --- tracks --- Device start end length Id System /dev/dasdc1 2 4267 42661 Linux native /dev/dasdc2 4268 150239 1459722 Linux native (dasda and dasd are swap on V-Disk) I have a /dev/dasd (unallocated), also a 3390-9 I could not figure out how to create an expandable fs at install time. I wanted to have: 1)3390-3 with /boot (300MB) and / (for the remaining 2GB) 2)3390-9 with other fs (/usr, /home, /opt, etc.), perhaps LVM (easily expandable?) I just tried a small LVM setup and if you install SUSE 12 it should already give you a working setup out of the box, you just have to tell it to use LVM. After the initial step, as soon as you get into Yast, you get the chance to select a partition setup under the point Suggested Partitioning [1]; if you select Edit Proposal Settings you will have the option to tell it to Create LVM-based Proposal. This will already take care of it (look out that you select the DASD in question on the previous screens). Boot for zipl will be separated and for the rest of the space it will create a single LVM volume group (for swap and /). This default layout is OK for most cases IMHO - in case it isn't you can afterwards still change it by accessing the expert mode, I have not tested this though. Later you can extend this initial volume group with additional disks. That should be straight forward with the help of Yast [2]. Essentially, you will just add the 2., or 3., or n. disk (a partition of those if you want) to the volume group of the original disk that Yast created for you during installation and then you resize the logical volume of / to use the additional space. Additionally the filesystem on / has to be extended, in case of btrfs and Yast this should work out of the box (Yast should take care of it). As *always*, after you change anything regarding the root-fs, you have to rebuild the initrd for zipl and the initrd for you current kernel. This is really important (otherwise your system might be un-bootable)! Something like this should do: update-bootloader --reinit --force dracut --force --host This will work for the most recent kernel installed. I believe that there are some restrictions on what fs can be in LVM (/boot can't for instance...and I had a problem with /lib) Boot (the boot that will include the zipl, the grub2 that SUSE uses should be OK though) can't be in the LVM. It is also important to use an FS that can be dynamically resized (e.g. btfs, xfs.. not lets say fat32 :) ). I am not aware of other restrictions. ...still waiting for: The Virtualization Cookbook for IBM z Systems Volume 3: SUSE Linux Enterprise Server 12, SG24-8890 Sry, I can't help you on that :) As I said before, I just tested this very small setup here locally, it worked as I described it. I can't guarantee that it will serve your purpose and system-architecture, it might even turn out that LVM is not the best choice after all. I just wanted to give the example because the btrfs-extension option doesn't work in SLES12 atm. [1] - https://www.suse.com/documentation/sles-12/book_sle_deployment/data/sec_i_yast2_inst_mode_partitioning.html [2] - https://www.suse.com/documentation/sles-12/stor_admin/data/sec_lvm_vg_resize.html Frank M. Ramaekers Jr. -Original Message- From: Benjamin Block [mailto:bbl...@linux.vnet.ibm.com] Sent: Friday, August 14, 2015 9:49 AM To: Frank M. Ramaekers Cc: Linux on 390 Port Subject: Re: Adding DASD to a btrfs Hej Frank, On 09:08 Thu 13 Aug , Frank M. Ramaekers wrote: I'm new to both SLES (12 in my case) and btrfs. I just recently installed SLES 12 onto a 3390-9 (I had an additional 3390-9, but didn't see a way to combine the two into a single fs). I want to add the other 3390-9 to the btrfs (/) for expansion purposes. I have done the same thing on a test vm - adding a second DASD to a existing root-btrfs filesystem. In short: be very cautious. The btrfs-function works as you can find it in various help-texts, but the problem is, you change you root-fs and upon reboot the second DASD has to be whitlisted by the initrds so it can be used - and that is not yet supported
Re: Adding DASD to a btrfs
Correction: Bootloader support for /boot, allowing to boot from a Btrfs partition Frank M. Ramaekers Jr. -Original Message- From: Frank M. Ramaekers Sent: Friday, August 14, 2015 11:11 AM To: 'Benjamin Block' Cc: Linux on 390 Port Subject: RE: Adding DASD to a btrfs Well, I'm not married to this (fresh) install, but I do want to be able to expand the root fs when necessary. I'd be willing to re-install if I can create the root fs so that it can be (easily) expanded if necessary. Currently I have only 1 single dasd (in use): Disk /dev/dasdc: cylinders : 10016 tracks per cylinder ..: 15 blocks per track .: 12 bytes per block ..: 4096 volume label .: VOL1 volume serial : max partitions ...: 3 --- tracks --- Device start end length Id System /dev/dasdc1 2 4267 42661 Linux native /dev/dasdc2 4268 150239 1459722 Linux native (dasda and dasd are swap on V-Disk) I have a /dev/dasd (unallocated), also a 3390-9 I could not figure out how to create an expandable fs at install time. I wanted to have: 1) 3390-3 with /boot (300MB) and / (for the remaining 2GB) 2) 3390-9 with other fs (/usr, /home, /opt, etc.), perhaps LVM (easily expandable?) I believe that there are some restrictions on what fs can be in LVM (/boot can't for instance...and I had a problem with /lib) ...still waiting for: The Virtualization Cookbook for IBM z Systems Volume 3: SUSE Linux Enterprise Server 12, SG24-8890 Frank M. Ramaekers Jr. -Original Message- From: Benjamin Block [mailto:bbl...@linux.vnet.ibm.com] Sent: Friday, August 14, 2015 9:49 AM To: Frank M. Ramaekers Cc: Linux on 390 Port Subject: Re: Adding DASD to a btrfs Hej Frank, On 09:08 Thu 13 Aug , Frank M. Ramaekers wrote: I'm new to both SLES (12 in my case) and btrfs. I just recently installed SLES 12 onto a 3390-9 (I had an additional 3390-9, but didn't see a way to combine the two into a single fs). I want to add the other 3390-9 to the btrfs (/) for expansion purposes. I have done the same thing on a test vm - adding a second DASD to a existing root-btrfs filesystem. In short: be very cautious. The btrfs-function works as you can find it in various help-texts, but the problem is, you change you root-fs and upon reboot the second DASD has to be whitlisted by the initrds so it can be used - and that is not yet supported afaik, even more so because the default disk-layout places the grub2 onto the same FS, and thus not even grub2 will be able to launch. The initrd will only know about the DASD that you have used initially to install the system. 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. Unless I missed something I'd advice against it. The official documentation that SUSE provides [1] suggests that LVM and DM-Raid are natively supported by it. [1] - https://www.suse.com/documentation/sles-12/stor_admin/data/stor_admin.html 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
Well, I'm not married to this (fresh) install, but I do want to be able to expand the root fs when necessary. I'd be willing to re-install if I can create the root fs so that it can be (easily) expanded if necessary. Currently I have only 1 single dasd (in use): Disk /dev/dasdc: cylinders : 10016 tracks per cylinder ..: 15 blocks per track .: 12 bytes per block ..: 4096 volume label .: VOL1 volume serial : max partitions ...: 3 --- tracks --- Device start end length Id System /dev/dasdc1 2 4267 42661 Linux native /dev/dasdc2 4268 150239 1459722 Linux native (dasda and dasd are swap on V-Disk) I have a /dev/dasd (unallocated), also a 3390-9 I could not figure out how to create an expandable fs at install time. I wanted to have: 1) 3390-3 with /boot (300MB) and / (for the remaining 2GB) 2) 3390-9 with other fs (/usr, /home, /opt, etc.), perhaps LVM (easily expandable?) I believe that there are some restrictions on what fs can be in LVM (/boot can't for instance...and I had a problem with /lib) ...still waiting for: The Virtualization Cookbook for IBM z Systems Volume 3: SUSE Linux Enterprise Server 12, SG24-8890 Frank M. Ramaekers Jr. -Original Message- From: Benjamin Block [mailto:bbl...@linux.vnet.ibm.com] Sent: Friday, August 14, 2015 9:49 AM To: Frank M. Ramaekers Cc: Linux on 390 Port Subject: Re: Adding DASD to a btrfs Hej Frank, On 09:08 Thu 13 Aug , Frank M. Ramaekers wrote: I'm new to both SLES (12 in my case) and btrfs. I just recently installed SLES 12 onto a 3390-9 (I had an additional 3390-9, but didn't see a way to combine the two into a single fs). I want to add the other 3390-9 to the btrfs (/) for expansion purposes. I have done the same thing on a test vm - adding a second DASD to a existing root-btrfs filesystem. In short: be very cautious. The btrfs-function works as you can find it in various help-texts, but the problem is, you change you root-fs and upon reboot the second DASD has to be whitlisted by the initrds so it can be used - and that is not yet supported afaik, even more so because the default disk-layout places the grub2 onto the same FS, and thus not even grub2 will be able to launch. The initrd will only know about the DASD that you have used initially to install the system. 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. Unless I missed something I'd advice against it. The official documentation that SUSE provides [1] suggests that LVM and DM-Raid are natively supported by it. [1] - https://www.suse.com/documentation/sles-12/stor_admin/data/stor_admin.html 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
Read this from you link (not sure what this means): Multiple device support. This feature is currently not supported on SUSE Linux Enterprise Server. Frank M. Ramaekers Jr. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Benjamin Block Sent: Friday, August 14, 2015 9:49 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a btrfs Hej Frank, On 09:08 Thu 13 Aug , Frank M. Ramaekers wrote: I'm new to both SLES (12 in my case) and btrfs. I just recently installed SLES 12 onto a 3390-9 (I had an additional 3390-9, but didn't see a way to combine the two into a single fs). I want to add the other 3390-9 to the btrfs (/) for expansion purposes. I have done the same thing on a test vm - adding a second DASD to a existing root-btrfs filesystem. In short: be very cautious. The btrfs-function works as you can find it in various help-texts, but the problem is, you change you root-fs and upon reboot the second DASD has to be whitlisted by the initrds so it can be used - and that is not yet supported afaik, even more so because the default disk-layout places the grub2 onto the same FS, and thus not even grub2 will be able to launch. The initrd will only know about the DASD that you have used initially to install the system. 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. Unless I missed something I'd advice against it. The official documentation that SUSE provides [1] suggests that LVM and DM-Raid are natively supported by it. [1] - https://www.suse.com/documentation/sles-12/stor_admin/data/stor_admin.html 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/
Adding DASD to a btrfs
I'm new to both SLES (12 in my case) and btrfs. I just recently installed SLES 12 onto a 3390-9 (I had an additional 3390-9, but didn't see a way to combine the two into a single fs). I want to add the other 3390-9 to the btrfs (/) for expansion purposes. lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks == 0.0.0301 active dasda 94:0FBA 512512MB 1048576 0.0.0300 active dasdb 94:4FBA 512256MB 524288 0.0.0100 active dasdc 94:8ECKD 4096 7042MB1802880 0.0.0101 active dasdd 94:12 ECKD 4096 7042MB1802880 Number Start End SizeFile system Flags 1 98.3kB 210MB 210MB ext2 2 210MB 7385MB 7175MB btrfs Filesystem Size Used Avail Use% Mounted on /dev/dasdc2 6.7G 3.6G 2.9G 56% / devtmpfs313M 4.0K 313M 1% /dev tmpfs 320M 20K 320M 1% /dev/shm tmpfs 320M 5.5M 315M 2% /run tmpfs 320M 0 320M 0% /sys/fs/cgroup /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/tmp /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/opt /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/log /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/spool /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/lib/pgsql /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/lib/mailman /dev/dasdc1 194M 24M 161M 13% /boot/zipl /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/lib/named /dev/dasdc2 6.7G 3.6G 2.9G 56% /usr/local /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/crash /dev/dasdc2 6.7G 3.6G 2.9G 56% /srv /dev/dasdc2 6.7G 3.6G 2.9G 56% /tmp /dev/dasdc2 6.7G 3.6G 2.9G 56% /opt /dev/dasdc2 6.7G 3.6G 2.9G 56% /home /dev/dasdc2 6.7G 3.6G 2.9G 56% /boot/grub2/s390x-emu TIA, Frank M. Ramaekers Jr. | Systems Programmer | Information Technology | American Income Life Insurance | 254-761-6649 -- 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
Frank, Up to this point, I've not seen this used ... So, I recommend a test system until you are comfortable and a backup of your /. But, on a lab Guest, I find: Using Btrfs with Multiple Devices https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices # mkfs.btrfs /dev/dasdc1 # mount /dev/dasdc1 /mnt # mkfs.btrfs /dev/dasdd1 # df | head -1; df | grep mnt Filesystem 1K-blocksUsed Available Use% Mounted on /dev/dasdc1 7212144 16704 6462208 1% /mnt # btrfs device add -f /dev/dasdd1 /mnt s390sles12:~ # df | head -1; df | grep mnt Filesystem 1K-blocksUsed Available Use% Mounted on /dev/dasdc1 14424288 16704 13673280 1% /mnt Mike O'Reilly IBM Linux Change Team Frank M. Ramaekers FRamaekers@ailif To e.comLINUX-390@VM.MARIST.EDU Sent by: Linux on cc 390 Port linux-...@vm.mar Subject IST.EDU Adding DASD to a btrfs 08/13/2015 07:08 AM Please respond to Linux on 390 Port linux-...@vm.mar IST.EDU I'm new to both SLES (12 in my case) and btrfs. I just recently installed SLES 12 onto a 3390-9 (I had an additional 3390-9, but didn't see a way to combine the two into a single fs). I want to add the other 3390-9 to the btrfs (/) for expansion purposes. lsdasd Bus-ID Status Name Device Type BlkSz Size Blocks == 0.0.0301 active dasda 94:0FBA 512512MB 1048576 0.0.0300 active dasdb 94:4FBA 512256MB 524288 0.0.0100 active dasdc 94:8ECKD 4096 7042MB1802880 0.0.0101 active dasdd 94:12 ECKD 4096 7042MB1802880 Number Start End SizeFile system Flags 1 98.3kB 210MB 210MB ext2 2 210MB 7385MB 7175MB btrfs Filesystem Size Used Avail Use% Mounted on /dev/dasdc2 6.7G 3.6G 2.9G 56% / devtmpfs313M 4.0K 313M 1% /dev tmpfs 320M 20K 320M 1% /dev/shm tmpfs 320M 5.5M 315M 2% /run tmpfs 320M 0 320M 0% /sys/fs/cgroup /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/tmp /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/opt /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/log /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/spool /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/lib/pgsql /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/lib/mailman /dev/dasdc1 194M 24M 161M 13% /boot/zipl /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/lib/named /dev/dasdc2 6.7G 3.6G 2.9G 56% /usr/local /dev/dasdc2 6.7G 3.6G 2.9G 56% /var/crash /dev/dasdc2 6.7G 3.6G 2.9G 56% /srv /dev/dasdc2 6.7G 3.6G 2.9G 56% /tmp /dev/dasdc2 6.7G 3.6G 2.9G 56% /opt /dev/dasdc2 6.7G 3.6G 2.9G 56% /home /dev/dasdc2 6.7G 3.6G 2.9G 56% /boot/grub2/s390x-emu TIA, Frank M. Ramaekers Jr. | Systems Programmer | Information Technology | American Income Life Insurance | 254-761-6649 -- 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
Re: Adding DASD to a Debian guest
Thanks for the response. In short, I am configuring a golden image that will live on one piece of dasd with LVM. When I clone it I will need to add more dasd to certain of the cloned guests, so the responses you guys have given previously are exactly what I need when I get to that point. So, now I am attempting to do a fresh install that has LVM for the golden image, because my current golden image does not use LVM. As you mentioned, in this process I am letting the 'installer' do the job. But, during one of the last steps of the install I get the error about zipl bootloader not being able to download and I have to skip that step. The install finishes but I cannot boot with the ipl command. Here is a run down of what I have done relating to the LVM. 1. Placed a 100M partition on the dasd and made it the /boot partition 2. Placed the remainder of dasd in a virtual group vg1 3. Created logical volume lv1 = '/' and lv2=swap, using vg1 4. Wrote partitions and moved on with install process Howard -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz Powiedziuk Sent: Wednesday, August 12, 2015 9:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a Debian guest At which point are you getting that error? If you do a fresh install then just add these dasds your virtual machine before initializing install process (attach or better define minidisks) and let the installator do the job. Installator should give you an option to add all your dasds into the lvm and partition it the way you want. If you do it this way, you shouldn’t have to go through all these steps we were talking about. These steps are only appropriate if you want to resize existing system. Or that’s exactly what you are doing but you are still getting an error? Gregory On Aug 11, 2015, at 9:30 PM, Howard V. Hardiman hvhar...@ncat.edu wrote: Okay.. Your help and advice is appreciated. I think I see the picture better now. As a result, I am now starting a fresh install to do so with LVM. I can create vg and lv's just fine (I think, yet to test completely). But I get an error that says that zipl bootloader could not be downloaded onto the device before the installation finishes. I thought that by creating a /boot partition (100M) on a piece of the dasd not affected by LVM would do the trick. But I get the same error Am I missing something here? If I proceed in the installation it says that I can manually boot with the /vmlinuz kernel on partition /dev/dasda1 and root /dev/mapper/vg1-lv1 passed as kernel argument. How do I do that? If it works, can I then load zipl or some bootloader that will allow me to be able to ipl the OS like normal? HH -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Stephen Powell Sent: Tuesday, August 11, 2015 8:39 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a Debian guest On Tue, 11 Aug 2015 12:27:08 -0400 (EDT), Grzegorz Powiedziuk wrote: Make sure that when you restart linux, these dasd will automatically show up in /proc/dasd/devices. Stephen suggested over here creating these empty files in /etc/sysconfig/hardware - I don’t know about that. I have never done it this way (but I haven’t been using debian in many years and things might have changed). Debian uses sysconfig-hardware to configure the hardware and bring it online at boot time. Other distributions, SUSE in particular, used to use sysconfig-hardware but don't anymore. But Debian still does. Creating the empty file in /etc/sysconfig/hardware is all that is necessary for a DASD device. For other devices, a network device for example, the file needs to have configuration data in it. If you're using a plain vanilla Debian system, rebuilding the initial RAM file system after creating a file in /etc/sysconfig/hardware is not necessary. But if you have reconfigured things the way I do it, so that DASD is brought online earlier (as I describe in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621080), then rebuilding the initial RAM file system is necessary. But it never hurts to rebuild the initial RAM file system. This should go without saying, but I'll say it anyway: the way I do it is not supported by Debian! I also need to offer the disclaimer that I have never used LVM2 on Debian. It's not that I have anything against it: I've just never needed to. -- .''`. Stephen Powellzlinux...@wowway.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
Re: Adding DASD to a Debian guest
On Tue, 11 Aug 2015 21:30:09 -0400 (EDT), Howard V. Hardiman wrote: Okay.. Your help and advice is appreciated. I think I see the picture better now. As a result, I am now starting a fresh install to do so with LVM. I can create vg and lv's just fine (I think, yet to test completely). But I get an error that says that zipl bootloader could not be downloaded onto the device before the installation finishes. I thought that by creating a /boot partition (100M) on a piece of the dasd not affected by LVM would do the trick. But I get the same error Am I missing something here? ... While I am glad to see Debian getting some publicity on this list, detailed problems with installation of Debian, even if it's mainframe Debian, might be better addressed on a Debian mailing list. Most of the folks on this list probably run a commercial distribution of Linux on their mainframes and are not interested in detailed installation problems with a distribution that they don't use. I think that debian-s...@lists.debian.org is the best place for this discussion to take place, and I will do my best to assist you over there. Please read https://www.debian.org/MailingLists/ for information on how to subscribe and the code of conduct. And please don't top post. We prefer the usenet style of quoting. See this article: https://en.wikipedia.org/wiki/Posting_style -- .''`. Stephen Powellzlinux...@wowway.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: Adding DASD to a Debian guest
Fair enough I have tried that list before with no response. HH -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Stephen Powell Sent: Wednesday, August 12, 2015 5:11 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a Debian guest On Tue, 11 Aug 2015 21:30:09 -0400 (EDT), Howard V. Hardiman wrote: Okay.. Your help and advice is appreciated. I think I see the picture better now. As a result, I am now starting a fresh install to do so with LVM. I can create vg and lv's just fine (I think, yet to test completely). But I get an error that says that zipl bootloader could not be downloaded onto the device before the installation finishes. I thought that by creating a /boot partition (100M) on a piece of the dasd not affected by LVM would do the trick. But I get the same error Am I missing something here? ... While I am glad to see Debian getting some publicity on this list, detailed problems with installation of Debian, even if it's mainframe Debian, might be better addressed on a Debian mailing list. Most of the folks on this list probably run a commercial distribution of Linux on their mainframes and are not interested in detailed installation problems with a distribution that they don't use. I think that debian-s...@lists.debian.org is the best place for this discussion to take place, and I will do my best to assist you over there. Please read https://www.debian.org/MailingLists/ for information on how to subscribe and the code of conduct. And please don't top post. We prefer the usenet style of quoting. See this article: https://en.wikipedia.org/wiki/Posting_style -- .''`. Stephen Powellzlinux...@wowway.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/ NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties. –– NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties. ––
Re: Adding DASD to a Debian guest
On Wed, 12 Aug 2015 17:37:29 -0400 (EDT), Howard V. Hardiman wrote: Fair enough I have tried that list before with no response. I'm sorry to hear that. But I'll be watching for it. If you post this issue to debian-s...@lists.debian.org, you'll get at least one response: mine. -- .''`. Stephen Powellzlinux...@wowway.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: Adding DASD to a Debian guest
At which point are you getting that error? If you do a fresh install then just add these dasds your virtual machine before initializing install process (attach or better define minidisks) and let the installator do the job. Installator should give you an option to add all your dasds into the lvm and partition it the way you want. If you do it this way, you shouldn’t have to go through all these steps we were talking about. These steps are only appropriate if you want to resize existing system. Or that’s exactly what you are doing but you are still getting an error? Gregory On Aug 11, 2015, at 9:30 PM, Howard V. Hardiman hvhar...@ncat.edu wrote: Okay.. Your help and advice is appreciated. I think I see the picture better now. As a result, I am now starting a fresh install to do so with LVM. I can create vg and lv's just fine (I think, yet to test completely). But I get an error that says that zipl bootloader could not be downloaded onto the device before the installation finishes. I thought that by creating a /boot partition (100M) on a piece of the dasd not affected by LVM would do the trick. But I get the same error Am I missing something here? If I proceed in the installation it says that I can manually boot with the /vmlinuz kernel on partition /dev/dasda1 and root /dev/mapper/vg1-lv1 passed as kernel argument. How do I do that? If it works, can I then load zipl or some bootloader that will allow me to be able to ipl the OS like normal? HH -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Stephen Powell Sent: Tuesday, August 11, 2015 8:39 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a Debian guest On Tue, 11 Aug 2015 12:27:08 -0400 (EDT), Grzegorz Powiedziuk wrote: Make sure that when you restart linux, these dasd will automatically show up in /proc/dasd/devices. Stephen suggested over here creating these empty files in /etc/sysconfig/hardware - I don’t know about that. I have never done it this way (but I haven’t been using debian in many years and things might have changed). Debian uses sysconfig-hardware to configure the hardware and bring it online at boot time. Other distributions, SUSE in particular, used to use sysconfig-hardware but don't anymore. But Debian still does. Creating the empty file in /etc/sysconfig/hardware is all that is necessary for a DASD device. For other devices, a network device for example, the file needs to have configuration data in it. If you're using a plain vanilla Debian system, rebuilding the initial RAM file system after creating a file in /etc/sysconfig/hardware is not necessary. But if you have reconfigured things the way I do it, so that DASD is brought online earlier (as I describe in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621080), then rebuilding the initial RAM file system is necessary. But it never hurts to rebuild the initial RAM file system. This should go without saying, but I'll say it anyway: the way I do it is not supported by Debian! I also need to offer the disclaimer that I have never used LVM2 on Debian. It's not that I have anything against it: I've just never needed to. -- .''`. Stephen Powellzlinux...@wowway.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/ NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties. –– NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties. –– -- 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 Debian guest
p.s. pvscan, vgscan, lvscan should all give you info to let you see what you built and how the space is used in LVM. On Tue, Aug 11, 2015 at 1:53 PM, Scott Rohling scott.rohl...@gmail.com wrote: On mainframes - where ECKD DASD comes in smaller chunks then you might be used to (2.3 G for 3390-3, etc) -- using LVM (logical volume manager) is standard practice. While there is debate whether root should be in an LVM, or things should be separated out (/usr /tmp, etc) -- the essence is that can allow you to extend an existing filesystem by adding space to the logical volume manager - and then using it's commands (lvextend, et al) to extend existing/new logical volumes groups with this space. Without that ability, you'd run into problems when you have a filesystem fill up -- all you can do is copy it to a new, bigger space. 'logical volumes' let you extend a single filesystem across several physical volumes... things like striping can also come into play, but that's a more advanced topic... it's main use is to allow us to use these historically small DASD units to be used in multiples for a single filesystem (mount point, whatever). LVM isn't a mainframe thing -- it's a Linux thing and there's lots of info on it via google, etc... Scott Rohling On Tue, Aug 11, 2015 at 12:49 PM, Howard V. Hardiman hvhar...@ncat.edu wrote: Thanks. So here is my question. What is LVM and how do I know if I should be using it? I did not use LVM on the install I am currently using. I portioned the single dasd for 'swap' (384k) and '/' (7G). I did not use LVM after that. I just now did a fresh install where I portioned the dasd the same way as before, but I selected LVM and portioned that way. I suppose it worked. I will retry the steps below to add additional dasd since they seem to be geared towards LVM. I'm asking about LVM because based on the responses, it just seems that's the easiest way to go... Comments? HH -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz Powiedziuk Sent: Tuesday, August 11, 2015 12:27 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a Debian guest It should be possible depending on what you did so far. If your “/“ is on LVM then you should be able to add new dasd to it’s volume group and extend the logical volume where “/“ lives. Make sure that when you restart linux, these dasd will automatically show up in /proc/dasd/devices Stephen suggested over here creating these empty files in /etc/sysconfig/hardware - I don’t know about that. I have never done it this way (but I haven’t been using debian in many years and things might have changed). As far as I remember, adding disks to zipl.conf and running zipl command was sufficient. But I googled it and it seems like that is something that came out with “wheeze debian” you might want to follow that than. cd /etc/sysconfig/hardware touch config-ccw-0.0. (0.0.0201 for example) At this point it would be good to rebuild the initramfs update-initramfs -uk $(uname -r) Reboot and make sure new dasd are there (cat /proc/dasd/devices or lsdasd) Create new partition on every new disk fdasd /dev/dasdc for example. And then “n” for new and follow instruction to create a partition using all space on a device. Now you should be able to create new physical volumes out of partitions you’ve just created. pvcreate /dev/dasdc1 run pvscan to see if new pv is on the list Now you can extend the volume group. Run vgdisplay to see what is the name of your current VG and then vgextend NAME_of_vg /dev/dasdc1- this will add physical volume” dasdc1 on top of your current vg Now you should be able to extend the size of your root logical volume. Run lvdisplay to see what is the name of your root logical volume and then lvextend NAME_of_root_logical_volume /dev/dasdc1- this will add free space from dasdc1 on top of your root logical volume Now you should be able to extend size of your ext filesystem resize2fs NAME_of_root_logical_volume Repeat steps for every new dasd That should do it. In sles I was able to run resize2fs on a mounted root filesystem, hopefully debian will be happy to do that as well. Gregory Powiedziuk On Aug 10, 2015, at 8:07 PM, Howard V. Hardiman hvhar...@ncat.edu wrote: Hello, I am also working on the system in question in the original question. I'm not used to creating or mounting the partitions using the command line options. I do that during the install using the text gui. During that process I partitioned the single dasd for just swap and / . I'd like know what it takes to simply add more and 'tack it on to the end' of the existing partition, if that's even possible. I am able to bring devices online and do the low level format and am able to see the devices in /proc/dasd/devices... But, I could use more detail after
Re: Adding DASD to a Debian guest
The only reason for the 3390-3, was I had already had some defined (DS8100), so I used them. Frank M. Ramaekers Jr. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Philipp Kern Sent: Sunday, August 09, 2015 10:27 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a Debian guest On Fri, Aug 07, 2015 at 08:13:02AM -0500, Frank M. Ramaekers wrote: I'd like to pick your brain on your Debian install. I've struggled, the biggest obstacle was ZIPL installit appears that partition has to be laid down just right (/ before any other fs), for instance. Had problems installing with ext4 LVM. Don't have a good ideas as to fs allocation. I'm using 3390-3, so I have to tie many together either RAID0 or via LVM. (Currently I have 6 allocated to Debian). I do wonder what kind of storage system you have that you insist on 3390-3 (instead of, say, two 3390-9). But then 3390-A are a DS8000-only feature, I guess? I liked it being arbitrary-sized very much. Of course there might be performance considerations, but not necessarily when you then need to tie six 3390-3 together for space reasons. Kind regards Philipp Kern -- 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 Debian guest
It should be possible depending on what you did so far. If your “/“ is on LVM then you should be able to add new dasd to it’s volume group and extend the logical volume where “/“ lives. Make sure that when you restart linux, these dasd will automatically show up in /proc/dasd/devices Stephen suggested over here creating these empty files in /etc/sysconfig/hardware - I don’t know about that. I have never done it this way (but I haven’t been using debian in many years and things might have changed). As far as I remember, adding disks to zipl.conf and running zipl command was sufficient. But I googled it and it seems like that is something that came out with “wheeze debian” you might want to follow that than. cd /etc/sysconfig/hardware touch config-ccw-0.0. (0.0.0201 for example) At this point it would be good to rebuild the initramfs update-initramfs -uk $(uname -r) Reboot and make sure new dasd are there (cat /proc/dasd/devices or lsdasd) Create new partition on every new disk fdasd /dev/dasdc for example. And then “n” for new and follow instruction to create a partition using all space on a device. Now you should be able to create new physical volumes out of partitions you’ve just created. pvcreate /dev/dasdc1 run pvscan to see if new pv is on the list Now you can extend the volume group. Run vgdisplay to see what is the name of your current VG and then vgextend NAME_of_vg /dev/dasdc1- this will add physical volume” dasdc1 on top of your current vg Now you should be able to extend the size of your root logical volume. Run lvdisplay to see what is the name of your root logical volume and then lvextend NAME_of_root_logical_volume /dev/dasdc1- this will add free space from dasdc1 on top of your root logical volume Now you should be able to extend size of your ext filesystem resize2fs NAME_of_root_logical_volume Repeat steps for every new dasd That should do it. In sles I was able to run resize2fs on a mounted root filesystem, hopefully debian will be happy to do that as well. Gregory Powiedziuk On Aug 10, 2015, at 8:07 PM, Howard V. Hardiman hvhar...@ncat.edu wrote: Hello, I am also working on the system in question in the original question. I'm not used to creating or mounting the partitions using the command line options. I do that during the install using the text gui. During that process I partitioned the single dasd for just swap and / . I'd like know what it takes to simply add more and 'tack it on to the end' of the existing partition, if that's even possible. I am able to bring devices online and do the low level format and am able to see the devices in /proc/dasd/devices... But, I could use more detail after that. Thanks for any help you can provide. HH -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz Powiedziuk Sent: Thursday, August 6, 2015 3:16 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a Debian guest Can you see them when you do cat /proc/dasd/devices ? If not than first bring them online (chccwdev -e 0.0.) and then check again. If they are there, than you are ready to do a low level format with dasdfmt /dev/dasdX (/proc/dasd/devices will tell you which dasdX is that). After that, create partitions (or not if you don’t want to) with fdasd /dev/dasdX Later you can create LVM (or not if you don’t want to) with pvcreate, vgcreate, lvcreate. Last step is creating a filesystem with mkfs.ext4 (or ext3) on a new partition or logical volume. And now, you can mount it. But you have to know that at this point you are also rewriting cylinder 0 of this DASD (if it is really attached) so it’s label will change. Let us know if you need more details Grzegorz Powiedziuk On Aug 6, 2015, at 3:04 PM, Cameron Seay cws...@gmail.com wrote: of course Debian can't see it until it's in a Linux filesystem. We don't know how to format it while in Debian. -- 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/ NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties. –– NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties. –– -- 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
Re: Adding DASD to a Debian guest
Thanks. So here is my question. What is LVM and how do I know if I should be using it? I did not use LVM on the install I am currently using. I portioned the single dasd for 'swap' (384k) and '/' (7G). I did not use LVM after that. I just now did a fresh install where I portioned the dasd the same way as before, but I selected LVM and portioned that way. I suppose it worked. I will retry the steps below to add additional dasd since they seem to be geared towards LVM. I'm asking about LVM because based on the responses, it just seems that's the easiest way to go... Comments? HH -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz Powiedziuk Sent: Tuesday, August 11, 2015 12:27 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a Debian guest It should be possible depending on what you did so far. If your “/“ is on LVM then you should be able to add new dasd to it’s volume group and extend the logical volume where “/“ lives. Make sure that when you restart linux, these dasd will automatically show up in /proc/dasd/devices Stephen suggested over here creating these empty files in /etc/sysconfig/hardware - I don’t know about that. I have never done it this way (but I haven’t been using debian in many years and things might have changed). As far as I remember, adding disks to zipl.conf and running zipl command was sufficient. But I googled it and it seems like that is something that came out with “wheeze debian” you might want to follow that than. cd /etc/sysconfig/hardware touch config-ccw-0.0. (0.0.0201 for example) At this point it would be good to rebuild the initramfs update-initramfs -uk $(uname -r) Reboot and make sure new dasd are there (cat /proc/dasd/devices or lsdasd) Create new partition on every new disk fdasd /dev/dasdc for example. And then “n” for new and follow instruction to create a partition using all space on a device. Now you should be able to create new physical volumes out of partitions you’ve just created. pvcreate /dev/dasdc1 run pvscan to see if new pv is on the list Now you can extend the volume group. Run vgdisplay to see what is the name of your current VG and then vgextend NAME_of_vg /dev/dasdc1- this will add physical volume” dasdc1 on top of your current vg Now you should be able to extend the size of your root logical volume. Run lvdisplay to see what is the name of your root logical volume and then lvextend NAME_of_root_logical_volume /dev/dasdc1- this will add free space from dasdc1 on top of your root logical volume Now you should be able to extend size of your ext filesystem resize2fs NAME_of_root_logical_volume Repeat steps for every new dasd That should do it. In sles I was able to run resize2fs on a mounted root filesystem, hopefully debian will be happy to do that as well. Gregory Powiedziuk On Aug 10, 2015, at 8:07 PM, Howard V. Hardiman hvhar...@ncat.edu wrote: Hello, I am also working on the system in question in the original question. I'm not used to creating or mounting the partitions using the command line options. I do that during the install using the text gui. During that process I partitioned the single dasd for just swap and / . I'd like know what it takes to simply add more and 'tack it on to the end' of the existing partition, if that's even possible. I am able to bring devices online and do the low level format and am able to see the devices in /proc/dasd/devices... But, I could use more detail after that. Thanks for any help you can provide. HH -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz Powiedziuk Sent: Thursday, August 6, 2015 3:16 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a Debian guest Can you see them when you do cat /proc/dasd/devices ? If not than first bring them online (chccwdev -e 0.0.) and then check again. If they are there, than you are ready to do a low level format with dasdfmt /dev/dasdX (/proc/dasd/devices will tell you which dasdX is that). After that, create partitions (or not if you don’t want to) with fdasd /dev/dasdX Later you can create LVM (or not if you don’t want to) with pvcreate, vgcreate, lvcreate. Last step is creating a filesystem with mkfs.ext4 (or ext3) on a new partition or logical volume. And now, you can mount it. But you have to know that at this point you are also rewriting cylinder 0 of this DASD (if it is really attached) so it’s label will change. Let us know if you need more details Grzegorz Powiedziuk On Aug 6, 2015, at 3:04 PM, Cameron Seay cws...@gmail.com wrote: of course Debian can't see it until it's in a Linux filesystem. We don't know how to format it while in Debian. -- For LINUX-390 subscribe / signoff / archive access instructions, send
Re: Adding DASD to a Debian guest
Okay.. Your help and advice is appreciated. I think I see the picture better now. As a result, I am now starting a fresh install to do so with LVM. I can create vg and lv's just fine (I think, yet to test completely). But I get an error that says that zipl bootloader could not be downloaded onto the device before the installation finishes. I thought that by creating a /boot partition (100M) on a piece of the dasd not affected by LVM would do the trick. But I get the same error Am I missing something here? If I proceed in the installation it says that I can manually boot with the /vmlinuz kernel on partition /dev/dasda1 and root /dev/mapper/vg1-lv1 passed as kernel argument. How do I do that? If it works, can I then load zipl or some bootloader that will allow me to be able to ipl the OS like normal? HH -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Stephen Powell Sent: Tuesday, August 11, 2015 8:39 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a Debian guest On Tue, 11 Aug 2015 12:27:08 -0400 (EDT), Grzegorz Powiedziuk wrote: Make sure that when you restart linux, these dasd will automatically show up in /proc/dasd/devices. Stephen suggested over here creating these empty files in /etc/sysconfig/hardware - I don’t know about that. I have never done it this way (but I haven’t been using debian in many years and things might have changed). Debian uses sysconfig-hardware to configure the hardware and bring it online at boot time. Other distributions, SUSE in particular, used to use sysconfig-hardware but don't anymore. But Debian still does. Creating the empty file in /etc/sysconfig/hardware is all that is necessary for a DASD device. For other devices, a network device for example, the file needs to have configuration data in it. If you're using a plain vanilla Debian system, rebuilding the initial RAM file system after creating a file in /etc/sysconfig/hardware is not necessary. But if you have reconfigured things the way I do it, so that DASD is brought online earlier (as I describe in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621080), then rebuilding the initial RAM file system is necessary. But it never hurts to rebuild the initial RAM file system. This should go without saying, but I'll say it anyway: the way I do it is not supported by Debian! I also need to offer the disclaimer that I have never used LVM2 on Debian. It's not that I have anything against it: I've just never needed to. -- .''`. Stephen Powellzlinux...@wowway.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/ NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties. –– NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties. ––
Re: Adding DASD to a Debian guest
On Tue, 11 Aug 2015 12:27:08 -0400 (EDT), Grzegorz Powiedziuk wrote: Make sure that when you restart linux, these dasd will automatically show up in /proc/dasd/devices. Stephen suggested over here creating these empty files in /etc/sysconfig/hardware - I don’t know about that. I have never done it this way (but I haven’t been using debian in many years and things might have changed). Debian uses sysconfig-hardware to configure the hardware and bring it online at boot time. Other distributions, SUSE in particular, used to use sysconfig-hardware but don't anymore. But Debian still does. Creating the empty file in /etc/sysconfig/hardware is all that is necessary for a DASD device. For other devices, a network device for example, the file needs to have configuration data in it. If you're using a plain vanilla Debian system, rebuilding the initial RAM file system after creating a file in /etc/sysconfig/hardware is not necessary. But if you have reconfigured things the way I do it, so that DASD is brought online earlier (as I describe in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621080), then rebuilding the initial RAM file system is necessary. But it never hurts to rebuild the initial RAM file system. This should go without saying, but I'll say it anyway: the way I do it is not supported by Debian! I also need to offer the disclaimer that I have never used LVM2 on Debian. It's not that I have anything against it: I've just never needed to. -- .''`. Stephen Powellzlinux...@wowway.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: Adding DASD to a Debian guest
Hello, I am also working on the system in question in the original question. I'm not used to creating or mounting the partitions using the command line options. I do that during the install using the text gui. During that process I partitioned the single dasd for just swap and / . I'd like know what it takes to simply add more and 'tack it on to the end' of the existing partition, if that's even possible. I am able to bring devices online and do the low level format and am able to see the devices in /proc/dasd/devices... But, I could use more detail after that. Thanks for any help you can provide. HH -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz Powiedziuk Sent: Thursday, August 6, 2015 3:16 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding DASD to a Debian guest Can you see them when you do cat /proc/dasd/devices ? If not than first bring them online (chccwdev -e 0.0.) and then check again. If they are there, than you are ready to do a low level format with dasdfmt /dev/dasdX (/proc/dasd/devices will tell you which dasdX is that). After that, create partitions (or not if you don’t want to) with fdasd /dev/dasdX Later you can create LVM (or not if you don’t want to) with pvcreate, vgcreate, lvcreate. Last step is creating a filesystem with mkfs.ext4 (or ext3) on a new partition or logical volume. And now, you can mount it. But you have to know that at this point you are also rewriting cylinder 0 of this DASD (if it is really attached) so it’s label will change. Let us know if you need more details Grzegorz Powiedziuk On Aug 6, 2015, at 3:04 PM, Cameron Seay cws...@gmail.com wrote: of course Debian can't see it until it's in a Linux filesystem. We don't know how to format it while in Debian. -- 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/ NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties. –– NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties. ––
Re: Adding DASD to a Debian guest
On Fri, Aug 07, 2015 at 08:13:02AM -0500, Frank M. Ramaekers wrote: I'd like to pick your brain on your Debian install. I've struggled, the biggest obstacle was ZIPL installit appears that partition has to be laid down just right (/ before any other fs), for instance. Had problems installing with ext4 LVM. Don't have a good ideas as to fs allocation. I'm using 3390-3, so I have to tie many together either RAID0 or via LVM. (Currently I have 6 allocated to Debian). I do wonder what kind of storage system you have that you insist on 3390-3 (instead of, say, two 3390-9). But then 3390-A are a DS8000-only feature, I guess? I liked it being arbitrary-sized very much. Of course there might be performance considerations, but not necessarily when you then need to tie six 3390-3 together for space reasons. Kind regards Philipp Kern -- 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 Debian guest
I'd like to pick your brain on your Debian install. I've struggled, the biggest obstacle was ZIPL installit appears that partition has to be laid down just right (/ before any other fs), for instance. Had problems installing with ext4 LVM. Don't have a good ideas as to fs allocation. I'm using 3390-3, so I have to tie many together either RAID0 or via LVM. (Currently I have 6 allocated to Debian). Frank M. Ramaekers Jr. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Cameron Seay Sent: Thursday, August 06, 2015 2:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Adding DASD to a Debian guest I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees the new dasd, but of course Debian can't see it until it's in a Linux filesystem. We don't know how to format it while in Debian. Any suggestions? -- 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 Debian guest
On Thu, 06 Aug 2015 15:04:10 -0400 (EDT), Cameron Seay wrote: I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees the new dasd, but of course Debian can't see it until it's in a Linux filesystem. We don't know how to format it while in Debian. Any suggestions? All steps here are performed as the root user. Step 1: cd to /etc/sysconfig/hardware. Create empty files in this directory, one per dasd device, with the touch command. Use something like touch config-ccw-0.0. where is the four-digit hexadecimal virtual device number (with leading zeros if necessary to make four digits). If the device number contains hexadecimal digits in the range A-F, make sure they are in lower case. For example: touch config-ccw-0.0.63fc touch config-ccw-0.0.63fd touch config-ccw-0.0.63fe Shutdown and reboot. The devices should now show up in the output of cat /proc/dasd/devices Step 2: Create 1 or more partitions (up to 3) on the device with the fdasd command. See the man page for fdasd for details. I usually create a single partition on each disk which occupies the entire volume. Step 3: If you are adding the new partitions to LVM2, use appropriate LVM2 commands to add the new partitions to LVM2 and enlarge the filesystem on the logical volume. I can't remember what they are because I don't use LVM2 with my Debian servers. If you want to use the partitions directly, use a file system formatter, such as mke2fs, to create a filesystem on each partition. At this point, I recommend a shutdown and reboot again. Upon reboot, udev aliases should have been created for your new partitions. Check out the pseudo-files in /dev/disk/by-uuid. Use these udev aliases in /etc/fstab to mount them. Of course, if it's a swap partition, use mkswap instead of mke2fs. Reboot again and your new file systems should be mounted. If you know what you're doing, you can avoid the reboots; but I'm trying to keep it simple (and the e-mail short). Debian doesn't use a front-end administration tool, such as yast, to do this kind of thing. You have to know the back-end commands. HTH. Debian has an s390 support e-mail list at debian-s...@lists.debian.org. The e-mail archives can be viewed at https://lists.debian.org/debian-s390/ Regards, -- .''`. Stephen Powellzlinux...@wowway.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: Adding DASD to a Debian guest
in debian as far as I remember it was just a matter of adding a new dasd to zipl.conf , running zipl and that’s it. Gregory Powiedziuk On Aug 6, 2015, at 3:17 PM, Mark Post mp...@suse.com wrote: On 8/6/2015 at 03:04 PM, Cameron Seay cws...@gmail.com wrote: I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees the new dasd, but of course Debian can't see it until it's in a Linux filesystem. We don't know how to format it while in Debian. The same as any other mainframe Linux system: dasdfmt. The bigger question is what tools and configuration files are available/needed to make the volumes persistent across a reboot. 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/ -- 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 Debian guest
On 8/6/2015 at 03:04 PM, Cameron Seay cws...@gmail.com wrote: I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees the new dasd, but of course Debian can't see it until it's in a Linux filesystem. We don't know how to format it while in Debian. The same as any other mainframe Linux system: dasdfmt. The bigger question is what tools and configuration files are available/needed to make the volumes persistent across a reboot. 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 Debian guest
Isn't dasdfmt, lsdasd, et al there? How did you install Debian? Are the ibm driver tools installed?Linux should be able to see it as soon as it's online. You may have to issue chccwdev -e for the disk if it doesn't happen automatically. cat /proc/partitions should give you some idea what disks Linux already sees as well. You could use LXFMT from Sine Nomine under CMS if you can't do it under Linux -- but you 'should' be able to. Scott Rohling On Thu, Aug 6, 2015 at 12:04 PM, Cameron Seay cws...@gmail.com wrote: I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees the new dasd, but of course Debian can't see it until it's in a Linux filesystem. We don't know how to format it while in Debian. Any suggestions? -- 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/
Adding DASD to a Debian guest
I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees the new dasd, but of course Debian can't see it until it's in a Linux filesystem. We don't know how to format it while in Debian. Any suggestions? -- 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 Debian guest
Can you see them when you do cat /proc/dasd/devices ? If not than first bring them online (chccwdev -e 0.0.) and then check again. If they are there, than you are ready to do a low level format with dasdfmt /dev/dasdX (/proc/dasd/devices will tell you which dasdX is that). After that, create partitions (or not if you don’t want to) with fdasd /dev/dasdX Later you can create LVM (or not if you don’t want to) with pvcreate, vgcreate, lvcreate. Last step is creating a filesystem with mkfs.ext4 (or ext3) on a new partition or logical volume. And now, you can mount it. But you have to know that at this point you are also rewriting cylinder 0 of this DASD (if it is really attached) so it’s label will change. Let us know if you need more details Grzegorz Powiedziuk On Aug 6, 2015, at 3:04 PM, Cameron Seay cws...@gmail.com wrote: of course Debian can't see it until it's in a Linux filesystem. We don't know how to format it while in Debian. -- 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/
Error code when adding DASD
All: I got this with my DIRM RLDE command while trying to add a MOD-9 volume to a guest. Help. Cameron DVHREQ2288I Your RLDEXTN request for MAINT at * has been accepted. DVHILZ3510I Starting DVHINITL with directory: USER DIRECT E DVHILZ3510I DVHINITL Parms: BLDMONO BLDDASD BLDLINK DVHIZD3508E Unable to determine maximum block for device 3309-09 while DVHIZD3508E processing record: LNX448 LNX448 1 10016 3309-09 DVHILZ3209E Unexpected RC= 3508, from Pipe: MasterPipe DVHRLE3212E Unexpected RC= 3209, from: EXEC DVHINITLZ RLDEXTN USER DVHRLE3212E DIRECT E BLDMONO BLDDASD BLDLINK DVHREQ2289E Your RLDEXTN request for MAINT at * has failed; with RC = DVHREQ2289E 3212. -- 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: Error code when adding DASD
If you didn't mistype -- then I would guess 3309-09 should be 3390-09 ? Scott Rohling On Tue, Aug 12, 2014 at 4:17 PM, Cameron Seay cws...@gmail.com wrote: All: I got this with my DIRM RLDE command while trying to add a MOD-9 volume to a guest. Help. Cameron DVHREQ2288I Your RLDEXTN request for MAINT at * has been accepted. DVHILZ3510I Starting DVHINITL with directory: USER DIRECT E DVHILZ3510I DVHINITL Parms: BLDMONO BLDDASD BLDLINK DVHIZD3508E Unable to determine maximum block for device 3309-09 while DVHIZD3508E processing record: LNX448 LNX448 1 10016 3309-09 DVHILZ3209E Unexpected RC= 3508, from Pipe: MasterPipe DVHRLE3212E Unexpected RC= 3209, from: EXEC DVHINITLZ RLDEXTN USER DVHRLE3212E DIRECT E BLDMONO BLDDASD BLDLINK DVHREQ2289E Your RLDEXTN request for MAINT at * has failed; with RC = DVHREQ2289E 3212. -- 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: Error code when adding DASD
I hit enter instead of starting new paragraph: In EXTENT CONTROL :REGIONS - I would guess you defined LNX448 as device type 3309-09 by mistake -- and DIRMAINT is complaining he doesn't know about such a type.. so correct this record in EXTENT CONTROL and then do the DIRM RLDE.. Scott Rohling On Tue, Aug 12, 2014 at 4:21 PM, Scott Rohling scott.rohl...@gmail.com wrote: If you didn't mistype -- then I would guess 3309-09 should be 3390-09 ? Scott Rohling On Tue, Aug 12, 2014 at 4:17 PM, Cameron Seay cws...@gmail.com wrote: All: I got this with my DIRM RLDE command while trying to add a MOD-9 volume to a guest. Help. Cameron DVHREQ2288I Your RLDEXTN request for MAINT at * has been accepted. DVHILZ3510I Starting DVHINITL with directory: USER DIRECT E DVHILZ3510I DVHINITL Parms: BLDMONO BLDDASD BLDLINK DVHIZD3508E Unable to determine maximum block for device 3309-09 while DVHIZD3508E processing record: LNX448 LNX448 1 10016 3309-09 DVHILZ3209E Unexpected RC= 3508, from Pipe: MasterPipe DVHRLE3212E Unexpected RC= 3209, from: EXEC DVHINITLZ RLDEXTN USER DVHRLE3212E DIRECT E BLDMONO BLDDASD BLDLINK DVHREQ2289E Your RLDEXTN request for MAINT at * has failed; with RC = DVHREQ2289E 3212. -- 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: Error code when adding DASD
Typo: device should be 3390-09, not 3309-09. It needs to match an entry in DEFAULT CONTROL unless you have overrides coded in your extent control. -- Mike Harding z/VM System Support mhard...@us.ibm.com mikehard...@mindless.com (925) 926-3179 (w) (925) 323-2070 (c) /sp Linux on 390 Port LINUX-390@vm.marist.edu wrote on 08/12/2014 04:17:22 PM: From: Cameron Seay cws...@gmail.com To: LINUX-390@vm.marist.edu Date: 08/12/2014 04:19 PM Subject: Error code when adding DASD Sent by: Linux on 390 Port LINUX-390@vm.marist.edu All: I got this with my DIRM RLDE command while trying to add a MOD-9 volume to a guest. Help. Cameron DVHREQ2288I Your RLDEXTN request for MAINT at * has been accepted. DVHILZ3510I Starting DVHINITL with directory: USER DIRECT E DVHILZ3510I DVHINITL Parms: BLDMONO BLDDASD BLDLINK DVHIZD3508E Unable to determine maximum block for device 3309-09 while DVHIZD3508E processing record: LNX448 LNX448 1 10016 3309-09 DVHILZ3209E Unexpected RC= 3508, from Pipe: MasterPipe DVHRLE3212E Unexpected RC= 3209, from: EXEC DVHINITLZ RLDEXTN USER DVHRLE3212E DIRECT E BLDMONO BLDDASD BLDLINK DVHREQ2289E Your RLDEXTN request for MAINT at * has failed; with RC = DVHREQ2289E 3212. -- 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: Error code when adding DASD
PERFECT! I love this board! Thanks guys. On Tue, Aug 12, 2014 at 7:24 PM, Michael Harding mhard...@us.ibm.com wrote: Typo: device should be 3390-09, not 3309-09. It needs to match an entry in DEFAULT CONTROL unless you have overrides coded in your extent control. -- Mike Harding z/VM System Support mhard...@us.ibm.com mikehard...@mindless.com (925) 926-3179 (w) (925) 323-2070 (c) /sp Linux on 390 Port LINUX-390@vm.marist.edu wrote on 08/12/2014 04:17:22 PM: From: Cameron Seay cws...@gmail.com To: LINUX-390@vm.marist.edu Date: 08/12/2014 04:19 PM Subject: Error code when adding DASD Sent by: Linux on 390 Port LINUX-390@vm.marist.edu All: I got this with my DIRM RLDE command while trying to add a MOD-9 volume to a guest. Help. Cameron DVHREQ2288I Your RLDEXTN request for MAINT at * has been accepted. DVHILZ3510I Starting DVHINITL with directory: USER DIRECT E DVHILZ3510I DVHINITL Parms: BLDMONO BLDDASD BLDLINK DVHIZD3508E Unable to determine maximum block for device 3309-09 while DVHIZD3508E processing record: LNX448 LNX448 1 10016 3309-09 DVHILZ3209E Unexpected RC= 3508, from Pipe: MasterPipe DVHRLE3212E Unexpected RC= 3209, from: EXEC DVHINITLZ RLDEXTN USER DVHRLE3212E DIRECT E BLDMONO BLDDASD BLDLINK DVHREQ2289E Your RLDEXTN request for MAINT at * has failed; with RC = DVHREQ2289E 3212. -- 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/ -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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 partition
On 7/6/2014 at 07:24 PM, Cameron Seay cws...@gmail.com wrote: On x86 LVM is done during the install. I have not figured out a way to do it during install with Linux on z. I seem to recall seeing in one of your previous emails that you're running SLES11. If so, the Deployment Guide talks about how to set up LVM during installation. It's really no different than on Intel/AMD. 1. Add a partition to the device you want to use 2. Mark it as LVM 3. Go to the Volume Management section of the Expert Partitioner. 4. Add a VG using the partition(s) you created in step 1. 5. Add the Logical Volumes you want in that VG. 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 partition
With SLES 11, during the install you have the option of specifying a display type of VNC and a VNC password. Once you receive a message indicating something to the effect ³You can connect to nnn.nnn.nnn.nnn, display:1 now with vncviewer Or use a Java capable browser on http://nnn.nnn.nnn.nnn:5801/³, you can utilize VNC to complete a graphical install utilizing yast2. After a few selections you will reach a ³Disk Activation² window where you can configure DASD. You will have the option of using the ³Expert Partitioner² at this point which will allow you to create LVM volume groups, physical volumes, logical volumes, and then filesystems on these logical volumes. Best Regards, Ted Allen Compute Platform Services Mainframe/Midrange Services z/VM and Linux on System z Support Wells Fargo Corporation ted.al...@wellsfargo.com On 7/6/14, 7:31 PM, Rich Smrcina r...@velocitysoftware.com wrote: I haven't been able to figure out how to do get it started after the install. At that point it's a combination of command line and YaST. pvcreate /dev/dasdx1 /dev/dasdy1 (or whatever your fresh partitions are called) vgcreate opt /dev/dasdx1 /dev/dasdy1 (again, your partitions here) Then the YaST partitioner can take over. On 07/06/2014 07:24 PM, Cameron Seay wrote: Yeahh... I figured I could not get around LVM. On x86 LVM is done during the install. I have not figured out a way to do it during install with Linux on z. Well, I gotta do it sooner or later. Thanks, Rich. On Sun, Jul 6, 2014 at 3:40 PM, Rich Smrcina r...@velocitysoftware.com wrote: The only way to do that is LVM (or something similar). On 07/06/2014 03:16 PM, Cameron Seay wrote: Can I add a DASD volume to an existing partition? I am using MOD-9s, and for example I would like to add one or more to the /opt partition. Or would it just be better to use LVM? Thanks -- 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/ -- Richard Smrcina Sr. Systems Engineer Velocity Software Inc. Main: (650) 964-8867 Main: (877) 964-8867 r...@velocitysoftware.com mailto://r...@velocitysoftware.com Signature http://www.velocitysoftware.com/ *Follow us:* facebook http://www.facebook.com/pages/Velocity-Software/356098274460840 LinkedIn http://www.linkedin.com/company/1798379?trk=tyah twitter https://twitter.com/VelocitySoftw Xing https://www.xing.com/companies/velocitysoftwaregmbh -- 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/ -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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/ -- Richard Smrcina Sr. Systems Engineer Velocity Software Inc. Main: (650) 964-8867 Main: (877) 964-8867 r...@velocitysoftware.com mailto://r...@velocitysoftware.com -- -- Signature http://www.velocitysoftware.com/ *Follow us:* facebook http://www.facebook.com/pages/Velocity-Software/356098274460840 LinkedIn http://www.linkedin.com/company/1798379?trk=tyah twitter https://twitter.com/VelocitySoftw Xing https://www.xing.com/companies/velocitysoftwaregmbh -- 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:
Re: Adding DASD to a partition
On 7/7/2014 at 03:02 PM, Ted Allen ted.al...@wellsfargo.com wrote: With SLES 11, during the install you have the option of specifying a display type of VNC and a VNC password. Once you receive a message indicating something to the effect *You can connect to nnn.nnn.nnn.nnn, display:1 now with vncviewer Or use a Java capable browser on http://nnn.nnn.nnn.nnn:5801/*, you can utilize VNC to complete a graphical install utilizing yast2. After a few selections you will reach a *Disk Activation* window where you can configure DASD. You will have the option of using the *Expert Partitioner* at this point which will allow you to create LVM volume groups, physical volumes, logical volumes, and then filesystems on these logical volumes. Note that none of these tasks depends on using VNC for the install. It can all be done from the ncurses interface as well. 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/
Adding DASD to a partition
Can I add a DASD volume to an existing partition? I am using MOD-9s, and for example I would like to add one or more to the /opt partition. Or would it just be better to use LVM? Thanks -- 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 partition
The only way to do that is LVM (or something similar). On 07/06/2014 03:16 PM, Cameron Seay wrote: Can I add a DASD volume to an existing partition? I am using MOD-9s, and for example I would like to add one or more to the /opt partition. Or would it just be better to use LVM? Thanks -- 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/ -- Richard Smrcina Sr. Systems Engineer Velocity Software Inc. Main: (650) 964-8867 Main: (877) 964-8867 r...@velocitysoftware.com mailto://r...@velocitysoftware.com Signature http://www.velocitysoftware.com/ *Follow us:* facebook http://www.facebook.com/pages/Velocity-Software/356098274460840 LinkedIn http://www.linkedin.com/company/1798379?trk=tyah twitter https://twitter.com/VelocitySoftw Xing https://www.xing.com/companies/velocitysoftwaregmbh -- 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 partition
Yeahh... I figured I could not get around LVM. On x86 LVM is done during the install. I have not figured out a way to do it during install with Linux on z. Well, I gotta do it sooner or later. Thanks, Rich. On Sun, Jul 6, 2014 at 3:40 PM, Rich Smrcina r...@velocitysoftware.com wrote: The only way to do that is LVM (or something similar). On 07/06/2014 03:16 PM, Cameron Seay wrote: Can I add a DASD volume to an existing partition? I am using MOD-9s, and for example I would like to add one or more to the /opt partition. Or would it just be better to use LVM? Thanks -- 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/ -- Richard Smrcina Sr. Systems Engineer Velocity Software Inc. Main: (650) 964-8867 Main: (877) 964-8867 r...@velocitysoftware.com mailto://r...@velocitysoftware.com Signature http://www.velocitysoftware.com/ *Follow us:* facebook http://www.facebook.com/pages/Velocity-Software/356098274460840 LinkedIn http://www.linkedin.com/company/1798379?trk=tyah twitter https://twitter.com/VelocitySoftw Xing https://www.xing.com/companies/velocitysoftwaregmbh -- 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/ -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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 partition
I haven't been able to figure out how to do get it started after the install. At that point it's a combination of command line and YaST. pvcreate /dev/dasdx1 /dev/dasdy1 (or whatever your fresh partitions are called) vgcreate opt /dev/dasdx1 /dev/dasdy1 (again, your partitions here) Then the YaST partitioner can take over. On 07/06/2014 07:24 PM, Cameron Seay wrote: Yeahh... I figured I could not get around LVM. On x86 LVM is done during the install. I have not figured out a way to do it during install with Linux on z. Well, I gotta do it sooner or later. Thanks, Rich. On Sun, Jul 6, 2014 at 3:40 PM, Rich Smrcina r...@velocitysoftware.com wrote: The only way to do that is LVM (or something similar). On 07/06/2014 03:16 PM, Cameron Seay wrote: Can I add a DASD volume to an existing partition? I am using MOD-9s, and for example I would like to add one or more to the /opt partition. Or would it just be better to use LVM? Thanks -- 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/ -- Richard Smrcina Sr. Systems Engineer Velocity Software Inc. Main: (650) 964-8867 Main: (877) 964-8867 r...@velocitysoftware.com mailto://r...@velocitysoftware.com Signature http://www.velocitysoftware.com/ *Follow us:* facebook http://www.facebook.com/pages/Velocity-Software/356098274460840 LinkedIn http://www.linkedin.com/company/1798379?trk=tyah twitter https://twitter.com/VelocitySoftw Xing https://www.xing.com/companies/velocitysoftwaregmbh -- 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/ -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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/ -- Richard Smrcina Sr. Systems Engineer Velocity Software Inc. Main: (650) 964-8867 Main: (877) 964-8867 r...@velocitysoftware.com mailto://r...@velocitysoftware.com Signature http://www.velocitysoftware.com/ *Follow us:* facebook http://www.facebook.com/pages/Velocity-Software/356098274460840 LinkedIn http://www.linkedin.com/company/1798379?trk=tyah twitter https://twitter.com/VelocitySoftw Xing https://www.xing.com/companies/velocitysoftwaregmbh -- 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 partition
Setting up LVM during install is there in SuSE and RedHat, but the incantation varies between the two, and from release to release (RHEL7 is very different from RHEL6). If you are going to clone it, and it tries to default to names that include the computer name, change the names to NOT include the computer name. The general flow of the incantations is: Create /boot as non-LVM. I make it 512M which leaves me some back-pocket space to figure out what happened when the user's fill / to 100%. Create PVs Create VG from PVs. Create LV for Swap Create LV for / Done Chuck Tribolet trib...@us.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet From: Cameron Seay cws...@gmail.com To: LINUX-390@vm.marist.edu, Date: 07/06/2014 04:40 PM Subject:Re: Adding DASD to a partition Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Yeahh... I figured I could not get around LVM. On x86 LVM is done during the install. I have not figured out a way to do it during install with Linux on z. Well, I gotta do it sooner or later. Thanks, Rich. On Sun, Jul 6, 2014 at 3:40 PM, Rich Smrcina r...@velocitysoftware.com wrote: The only way to do that is LVM (or something similar). On 07/06/2014 03:16 PM, Cameron Seay wrote: Can I add a DASD volume to an existing partition? I am using MOD-9s, and for example I would like to add one or more to the /opt partition. Or would it just be better to use LVM? Thanks -- 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/ -- Richard Smrcina Sr. Systems Engineer Velocity Software Inc. Main: (650) 964-8867 Main: (877) 964-8867 r...@velocitysoftware.com mailto://r...@velocitysoftware.com Signature http://www.velocitysoftware.com/ *Follow us:* facebook http://www.facebook.com/pages/Velocity-Software/356098274460840 LinkedIn http://www.linkedin.com/company/1798379?trk=tyah twitter https://twitter.com/VelocitySoftw Xing https://www.xing.com/companies/velocitysoftwaregmbh -- 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/ -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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 partition
I don't like to have / on LVM. It makes things very difficult if you have problems with the guest, like forgetting the root password, running mkinitrd without zipl, and so on. I usually create LV for home, var, opt and usr, and leave all the other (etc, bin, boot and so on) on physical disk. Those dirs don't grow a lot, so they can be left out of a LV. If your users don't use the home partition, it could be left as well. If you have multiple disks on the guest, and all the guests are clones, solving a forgotten root password problem will be much more trouble than leaving /etc out of a LV. Once I was talking about this with a friend, and he said I was being overcautious. In the same minute, he runs mkinitrd reboot. I looked at that and said: now, have a good time solving this mess... He took almost an hour to run the installer, get to the shell, activate all disks, mount the LVM, chroot into it and run zipl. All linuxes were clones, so they had the same lv and vg names... Now he doesn't uses LVM for / and I think he is happy... Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. 2014-07-06 23:01 GMT-03:00 Chuck Tribolet trib...@us.ibm.com: Setting up LVM during install is there in SuSE and RedHat, but the incantation varies between the two, and from release to release (RHEL7 is very different from RHEL6). If you are going to clone it, and it tries to default to names that include the computer name, change the names to NOT include the computer name. The general flow of the incantations is: Create /boot as non-LVM. I make it 512M which leaves me some back-pocket space to figure out what happened when the user's fill / to 100%. Create PVs Create VG from PVs. Create LV for Swap Create LV for / Done Chuck Tribolet trib...@us.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet From: Cameron Seay cws...@gmail.com To: LINUX-390@vm.marist.edu, Date: 07/06/2014 04:40 PM Subject:Re: Adding DASD to a partition Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Yeahh... I figured I could not get around LVM. On x86 LVM is done during the install. I have not figured out a way to do it during install with Linux on z. Well, I gotta do it sooner or later. Thanks, Rich. On Sun, Jul 6, 2014 at 3:40 PM, Rich Smrcina r...@velocitysoftware.com wrote: The only way to do that is LVM (or something similar). On 07/06/2014 03:16 PM, Cameron Seay wrote: Can I add a DASD volume to an existing partition? I am using MOD-9s, and for example I would like to add one or more to the /opt partition. Or would it just be better to use LVM? Thanks -- 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/ -- Richard Smrcina Sr. Systems Engineer Velocity Software Inc. Main: (650) 964-8867 Main: (877) 964-8867 r...@velocitysoftware.com mailto://r...@velocitysoftware.com Signature http://www.velocitysoftware.com/ *Follow us:* facebook http://www.facebook.com/pages/Velocity-Software/356098274460840 LinkedIn http://www.linkedin.com/company/1798379?trk=tyah twitter https://twitter.com/VelocitySoftw Xing https://www.xing.com/companies/velocitysoftwaregmbh -- 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/ -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A T State University Greensboro, NC 336 334 7717 x2251 -- 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
Re: Adding DASD to a partition
I keep GOOD track of the root passwords. I also keep a second ID with sudo privs that can be used to reset the root password. I use different VG names on SuSE and RedHat. If I need to mount / from SuSE system A on SuSE system B, I mount it on a RedHat system, rename the VG, unmount, mount on SuSEB, fix, rename back. And I've learned my lesson about mkinitrd, so that mistake happens very rarely. My users find very creative ways to fill up / And LVM makes it really easy to add space. Chuck Tribolet trib...@us.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet From: Mauro Souza thoriu...@gmail.com To: LINUX-390@vm.marist.edu, Date: 07/06/2014 08:06 PM Subject:Re: Adding DASD to a partition Sent by:Linux on 390 Port LINUX-390@vm.marist.edu I don't like to have / on LVM. It makes things very difficult if you have problems with the guest, like forgetting the root password, running mkinitrd without zipl, and so on. I usually create LV for home, var, opt and usr, and leave all the other (etc, bin, boot and so on) on physical disk. Those dirs don't grow a lot, so they can be left out of a LV. If your users don't use the home partition, it could be left as well. If you have multiple disks on the guest, and all the guests are clones, solving a forgotten root password problem will be much more trouble than leaving /etc out of a LV. Once I was talking about this with a friend, and he said I was being overcautious. In the same minute, he runs mkinitrd reboot. I looked at that and said: now, have a good time solving this mess... He took almost an hour to run the installer, get to the shell, activate all disks, mount the LVM, chroot into it and run zipl. All linuxes were clones, so they had the same lv and vg names... Now he doesn't uses LVM for / and I think he is happy... Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. 2014-07-06 23:01 GMT-03:00 Chuck Tribolet trib...@us.ibm.com: Setting up LVM during install is there in SuSE and RedHat, but the incantation varies between the two, and from release to release (RHEL7 is very different from RHEL6). If you are going to clone it, and it tries to default to names that include the computer name, change the names to NOT include the computer name. The general flow of the incantations is: Create /boot as non-LVM. I make it 512M which leaves me some back-pocket space to figure out what happened when the user's fill / to 100%. Create PVs Create VG from PVs. Create LV for Swap Create LV for / Done Chuck Tribolet trib...@us.ibm.com (IBM business) trib...@garlic.com (Personal) http://www.almaden.ibm.com/cs/people/triblet From: Cameron Seay cws...@gmail.com To: LINUX-390@vm.marist.edu, Date: 07/06/2014 04:40 PM Subject:Re: Adding DASD to a partition Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Yeahh... I figured I could not get around LVM. On x86 LVM is done during the install. I have not figured out a way to do it during install with Linux on z. Well, I gotta do it sooner or later. Thanks, Rich. On Sun, Jul 6, 2014 at 3:40 PM, Rich Smrcina r...@velocitysoftware.com wrote: The only way to do that is LVM (or something similar). On 07/06/2014 03:16 PM, Cameron Seay wrote: Can I add a DASD volume to an existing partition? I am using MOD-9s, and for example I would like to add one or more to the /opt partition. Or would it just be better to use LVM? Thanks -- 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/ -- Richard Smrcina Sr. Systems Engineer Velocity Software Inc. Main: (650) 964-8867 Main: (877) 964-8867 r...@velocitysoftware.com mailto://r...@velocitysoftware.com Signature http://www.velocitysoftware.com/ *Follow us:* facebook http://www.facebook.com/pages/Velocity-Software/356098274460840 LinkedIn http://www.linkedin.com/company/1798379?trk=tyah twitter https://twitter.com/VelocitySoftw Xing https://www.xing.com/companies/velocitysoftwaregmbh -- 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
Re: sles11 - adding dasd yast problem
Hi Mark, Do you have an idea in what cases this wouldn't work? This method in combination with the default dasd udev rules seems to be working for me in SLES11. Samir Reddahi Mark Post mp...@novell.com Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 08/01/2010 19:09 Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: sles11 - adding dasd yast problem On 1/8/2010 at 07:52 AM, Samir Reddahi samir.redd...@securex.be wrote: -snip- You can also add an options dasd_mod dasd= line to the /etc/modprobe.conf.local with all the dasd devices you want to get online after IPL. After that you run mkinitrd en zipl. for example: options dasd_mod dasd=200-202,203(diag),204-207,300-31F That won't necessarily bring them _online_ in SLES11. That's controlled by udev rules, which is why Novell recommends using YaST, or the dasd_configure script to set up your disks. Both of those will handle all the necessary pieces. 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 - Confidentiality Notice - This communication and the information it contains is intended (a) for the person(s) or organization(s) named above and for no other person or organization, and (b) may be confidential, legally privileged and protected by law. Unauthorized use, copying or disclosure of any of it may be unlawful! If you receive this communication in error, please notify us immediately, destroy any copies and delete it from your computer system. Please consult our disclaimer on our site www.securex.eu Thank you. -- 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
Re: sles11 - adding dasd yast problem
On 1/11/2010 at 05:25 AM, Samir Reddahi samir.redd...@securex.be wrote:
Hi Mark,
Do you have an idea in what cases this wouldn't work? This method in
combination with the default dasd udev rules seems to be working for me in
SLES11.
Not really. I just know that the default rules in 59-dasd.rules don't have the
equivalent of
ACTION==add, ENV{COLLECT_0.0.0150}==0, ATTR{[ccw/0.0.0150]online}=1
in the file. The /init script in the initrd _should_ pick up everything
specified on the kernel command line, but there has been at least one bug in
parsing that which has affected DASD units. Doing it via udev rules means
that's less likely to happen, and there's no need to rebuild the initrd.
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
Re: sles11 - adding dasd yast problem
Sue, For your first problem. Like the others already mentioned you can use the dasd_configure command. You can also add an options dasd_mod dasd= line to the /etc/modprobe.conf.local with all the dasd devices you want to get online after IPL. After that you run mkinitrd en zipl. for example: options dasd_mod dasd=200-202,203(diag),204-207,300-31F Regards, Samir Reddahi Sue Sivets ssiv...@fdrinnovation.com Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 07/01/2010 04:19 Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject sles11 - adding dasd yast problem I have just finished installing Sles 11, and now I need to add two mini-disks. The first is read only, the second is read-write. I tried running mkinitrd zipl like I would for sles10, but it doesn't seem to be working. Mkinitrd is only writing 6 or 8 lines to the console (it writes almost a screen full on sles10), and it seems to be changing the disk identifier from dasdc dasdd to dasda or dasdb so that /etc/fstab ends up being correct for the current ipl, but not the next. I guess zipl is working, at least the system seems to boot. If I run mkinitrd zipl manually, the new disks don't seem to be picked up and added to the dasd configuration so they are avail for the next ipl. If I use yast-hardware-dasd to activate them, then the dasd id is changed, and the disks seem to be varied online at the next ipl. How do I get the dasd added and mounted at each ipl? Can I add dasd without using yast and if so how? What commands do I need to run? Problem #2 - When I try to run yast2, I get an error message that Xlib: extension RANDR missing on display localhost:10.0 along with a bunch of other messages. I thought I saw something about Gnome in an earlier error message, and I did not install either Gnome of KDE since I was doing a z/linux install, and neither of these have worked very well on previous sles versions. yast seems to work so far, but I much prefer yast2. Can anyone shed any light on either of these problems? Thank you Sue Sivets -- Suzanne Sivets Systems Programmer Innovation Data Processing 275 Paterson Ave Little Falls, NJ 07424-1658 973-890-7300 Fax 973-890-7147 ssiv...@fdrinnovation.com This email (and attachments, if any) is confidential and access by anyone other than the addressee(s) is unauthorized. We would appreciate your notifying the sender and supp...@fdrinnovation.com immediately if you are not the intended recipient of this message. -- 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 - Confidentiality Notice - This communication and the information it contains is intended (a) for the person(s) or organization(s) named above and for no other person or organization, and (b) may be confidential, legally privileged and protected by law. Unauthorized use, copying or disclosure of any of it may be unlawful! If you receive this communication in error, please notify us immediately, destroy any copies and delete it from your computer system. Please consult our disclaimer on our site www.securex.eu Thank you. -- 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
Re: sles11 - adding dasd yast problem
On 1/8/2010 at 07:52 AM, Samir Reddahi samir.redd...@securex.be wrote: -snip- You can also add an options dasd_mod dasd= line to the /etc/modprobe.conf.local with all the dasd devices you want to get online after IPL. After that you run mkinitrd en zipl. for example: options dasd_mod dasd=200-202,203(diag),204-207,300-31F That won't necessarily bring them _online_ in SLES11. That's controlled by udev rules, which is why Novell recommends using YaST, or the dasd_configure script to set up your disks. Both of those will handle all the necessary pieces. 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
Re: sles11 - adding dasd yast problem
For Marcy, Marian and Samir, thank you all for the information. I've tried both yast and the dasd_configure command and I'm very happy that I can still choose to add new dasd manually with dasd_configure, makinitrd zipl, or automatically with yast. So far, I've found over the years, that using yast from a windows machine when I'm working from home, almost never works. Yast usuallly freezes or abends, and I end up frustrated, so I prefer to use the manual method when I'm working from home. When I'm at work, though, and I've got a Suse Linux desktop, then I almost always use yast. For Mark Post, thank you for the information about the Rotation AND Resizing extension. The block of messages I received after trying to invoke yast2 was: *suse11:~ #* yast2 Xlib: extension RANDR missing on display localhost:10.0. The program 'y2controlcenter-gnome' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 74 error_code 2 request_code 146 minor_code 1) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Is there a problem with what I installed for Suse11, and do I need to install Gnome/KDE (was my choice not to install these a mistake)? Or is there a problem with my Linux desktop (it is really old), or is something else causing this problem? At the moment, I don't have another Linux desktop to try and run Yast2 on. Thank you everyone Sue Sivets Marian Gasparovic wrote: Sue, use dasd_configure command. It brings device online and also makes sure it will come online after next IPL. for example dasd_configure 0.0.0105 1 === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. --- On Thu, 1/7/10, Sue Sivets ssiv...@fdrinnovation.com wrote: From: Sue Sivets ssiv...@fdrinnovation.com Subject: sles11 - adding dasd yast problem To: LINUX-390@VM.MARIST.EDU Date: Thursday, January 7, 2010, 4:18 AM I have just finished installing Sles 11, and now I need to add two mini-disks. The first is read only, the second is read-write. I tried running mkinitrd zipl like I would for sles10, but it doesn't seem to be working. Mkinitrd is only writing 6 or 8 lines to the console (it writes almost a screen full on sles10), and it seems to be changing the disk identifier from dasdc dasdd to dasda or dasdb so that /etc/fstab ends up being correct for the current ipl, but not the next. I guess zipl is working, at least the system seems to boot. If I run mkinitrd zipl manually, the new disks don't seem to be picked up and added to the dasd configuration so they are avail for the next ipl. If I use yast-hardware-dasd to activate them, then the dasd id is changed, and the disks seem to be varied online at the next ipl. How do I get the dasd added and mounted at each ipl? Can I add dasd without using yast and if so how? What commands do I need to run? Problem #2 - When I try to run yast2, I get an error message that Xlib: extension RANDR missing on display localhost:10.0 along with a bunch of other messages. I thought I saw something about Gnome in an earlier error message, and I did not install either Gnome of KDE since I was doing a z/linux install, and neither of these have worked very well on previous sles versions. yast seems to work so far, but I much prefer yast2. Can anyone shed any light on either of these problems? Thank you Sue Sivets -- Suzanne Sivets Systems Programmer Innovation Data Processing 275 Paterson Ave Little Falls, NJ 07424-1658 973-890-7300 Fax 973-890-7147 ssiv...@fdrinnovation.com This email (and attachments, if any) is confidential and access by anyone other than the addressee(s) is unauthorized. We would appreciate your notifying the sender and supp...@fdrinnovation.com immediately if you are not the intended recipient of this message. -- 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 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 This email (and attachments, if any) is confidential and access by anyone other than the addressee(s) is unauthorized. We would appreciate your notifying the sender and supp...@fdrinnovation.com immediately if you are not the intended
Re: sles11 - adding dasd yast problem
On 1/8/2010 at 04:41 PM, Sue Sivets ssiv...@fdrinnovation.com wrote: -snip- *suse11:~ #* yast2 Xlib: extension RANDR missing on display localhost:10.0. The program 'y2controlcenter-gnome' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 74 error_code 2 request_code 146 minor_code 1) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) This looks like a bug to me. I've seen the same thing umpteen times when building things for Slack/390. You should open a service request for this. 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
Re: sles11 - adding dasd yast problem
Sue, use dasd_configure command. It brings device online and also makes sure it will come online after next IPL. for example dasd_configure 0.0.0105 1 === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. --- On Thu, 1/7/10, Sue Sivets ssiv...@fdrinnovation.com wrote: From: Sue Sivets ssiv...@fdrinnovation.com Subject: sles11 - adding dasd yast problem To: LINUX-390@VM.MARIST.EDU Date: Thursday, January 7, 2010, 4:18 AM I have just finished installing Sles 11, and now I need to add two mini-disks. The first is read only, the second is read-write. I tried running mkinitrd zipl like I would for sles10, but it doesn't seem to be working. Mkinitrd is only writing 6 or 8 lines to the console (it writes almost a screen full on sles10), and it seems to be changing the disk identifier from dasdc dasdd to dasda or dasdb so that /etc/fstab ends up being correct for the current ipl, but not the next. I guess zipl is working, at least the system seems to boot. If I run mkinitrd zipl manually, the new disks don't seem to be picked up and added to the dasd configuration so they are avail for the next ipl. If I use yast-hardware-dasd to activate them, then the dasd id is changed, and the disks seem to be varied online at the next ipl. How do I get the dasd added and mounted at each ipl? Can I add dasd without using yast and if so how? What commands do I need to run? Problem #2 - When I try to run yast2, I get an error message that Xlib: extension RANDR missing on display localhost:10.0 along with a bunch of other messages. I thought I saw something about Gnome in an earlier error message, and I did not install either Gnome of KDE since I was doing a z/linux install, and neither of these have worked very well on previous sles versions. yast seems to work so far, but I much prefer yast2. Can anyone shed any light on either of these problems? Thank you Sue Sivets -- Suzanne Sivets Systems Programmer Innovation Data Processing 275 Paterson Ave Little Falls, NJ 07424-1658 973-890-7300 Fax 973-890-7147 ssiv...@fdrinnovation.com This email (and attachments, if any) is confidential and access by anyone other than the addressee(s) is unauthorized. We would appreciate your notifying the sender and supp...@fdrinnovation.com immediately if you are not the intended recipient of this message. -- 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 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
Re: sles11 - adding dasd yast problem
For question 2 concerning yast2, if you're using PuTTY to connect, have you loaded the session and changed the Connection-SSH-X11 to use X11 forwarding and XDM-Authorization-1, and also started Exceed, or whatever whatever product you use to accept X11 output? |-Original Message- |From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of |Sue Sivets |Sent: Wednesday, January 06, 2010 9:18 PM |To: LINUX-390@VM.MARIST.EDU |Subject: sles11 - adding dasd yast problem | |I have just finished installing Sles 11, and now I need to add two |mini-disks. The first is read only, the second is read-write. I tried |running mkinitrd zipl like I would for sles10, but it doesn't seem to |be working. Mkinitrd is only writing 6 or 8 lines to the console (it |writes almost a screen full on sles10), and it seems to be changing the |disk identifier from dasdc dasdd to dasda or dasdb so that /etc/fstab |ends up being correct for the current ipl, but not the next. I guess |zipl is working, at least the system seems to boot. If I run mkinitrd |zipl manually, the new disks don't seem to be picked up and added to the |dasd configuration so they are avail for the next ipl. If I use |yast-hardware-dasd to activate them, then the dasd id is changed, and |the disks seem to be varied online at the next ipl. | |How do I get the dasd added and mounted at each ipl? |Can I add dasd without using yast and if so how? What commands do I need |to run? | |Problem #2 - When I try to run yast2, I get an error message that Xlib: |extension RANDR missing on display localhost:10.0 along with a bunch |of other messages. I thought I saw something about Gnome in an earlier |error message, and I did not install either Gnome of KDE since I was |doing a z/linux install, and neither of these have worked very well on |previous sles versions. yast seems to work so far, but I much prefer |yast2. | |Can anyone shed any light on either of these problems? | |Thank you | |Sue Sivets | |-- | Suzanne Sivets | Systems Programmer | Innovation Data Processing | 275 Paterson Ave | Little Falls, NJ 07424-1658 | 973-890-7300 | Fax 973-890-7147 | ssiv...@fdrinnovation.com | | | |This email (and attachments, if any) is confidential and access by |anyone other than the addressee(s) is unauthorized. We would appreciate |your notifying the sender and supp...@fdrinnovation.com immediately if |you are not the intended recipient of this message. | |-- |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 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
FW: sles11 - adding dasd yast problem
For question 2 concerning yast2, if you're using PuTTY to connect, have you loaded the session and changed the Connection-SSH-X11 to use X11 forwarding and XDM-Authorization-1, and also started Exceed, or whatever whatever product you use to accept X11 output? ||-Original Message- ||From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of ||Sue Sivets ||Sent: Wednesday, January 06, 2010 9:18 PM ||To: LINUX-390@VM.MARIST.EDU ||Subject: sles11 - adding dasd yast problem || ||I have just finished installing Sles 11, and now I need to add two ||mini-disks. The first is read only, the second is read-write. I tried ||running mkinitrd zipl like I would for sles10, but it doesn't seem to ||be working. Mkinitrd is only writing 6 or 8 lines to the console (it ||writes almost a screen full on sles10), and it seems to be changing the ||disk identifier from dasdc dasdd to dasda or dasdb so that /etc/fstab ||ends up being correct for the current ipl, but not the next. I guess ||zipl is working, at least the system seems to boot. If I run mkinitrd ||zipl manually, the new disks don't seem to be picked up and added to |the ||dasd configuration so they are avail for the next ipl. If I use ||yast-hardware-dasd to activate them, then the dasd id is changed, and ||the disks seem to be varied online at the next ipl. || ||How do I get the dasd added and mounted at each ipl? ||Can I add dasd without using yast and if so how? What commands do I |need ||to run? || ||Problem #2 - When I try to run yast2, I get an error message that |Xlib: ||extension RANDR missing on display localhost:10.0 along with a |bunch ||of other messages. I thought I saw something about Gnome in an earlier ||error message, and I did not install either Gnome of KDE since I was ||doing a z/linux install, and neither of these have worked very well on ||previous sles versions. yast seems to work so far, but I much prefer ||yast2. || ||Can anyone shed any light on either of these problems? || ||Thank you || ||Sue Sivets || ||-- || Suzanne Sivets || Systems Programmer || Innovation Data Processing || 275 Paterson Ave || Little Falls, NJ 07424-1658 || 973-890-7300 || Fax 973-890-7147 || ssiv...@fdrinnovation.com || || || ||This email (and attachments, if any) is confidential and access by ||anyone other than the addressee(s) is unauthorized. We would |appreciate ||your notifying the sender and supp...@fdrinnovation.com immediately if ||you are not the intended recipient of this message. || ||-- ||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 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
Re: sles11 - adding dasd yast problem
On 1/6/2010 at 10:18 PM, Sue Sivets ssiv...@fdrinnovation.com wrote: -snip- Problem #2 - When I try to run yast2, I get an error message that Xlib: extension RANDR missing on display localhost:10.0 along with a bunch of other messages. That is not an error message, but an informational one. It simply means that the X server you're running on your desktop doesn't support the Rotation AND Resizing extension. The other messages, which you didn't list, may have been errors. I thought I saw something about Gnome in an earlier error message, and I did not install either Gnome of KDE since I was doing a z/linux install, and neither of these have worked very well on previous sles versions. yast seems to work so far, but I much prefer yast2. You don't need any graphical desktop environment to use X-enabled applications, just the X libraries. Which, you clearly do have installed. 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
Re: FW: sles11 - adding dasd yast problem
Hi Dale, I'm not using Putty. I'm using a Linux Shell - Konsole on an old version of Linux running on a PC, and I'm logging in with the following command: ssh -2 -4 -X r...@192.168.xxx.xxx This is the same login command I use for both of my Suse9 and Suse10 systems. Sue Slaughter, Dale wrote: For question 2 concerning yast2, if you're using PuTTY to connect, have you loaded the session and changed the Connection-SSH-X11 to use X11 forwarding and XDM-Authorization-1, and also started Exceed, or whatever whatever product you use to accept X11 output? ||-Original Message- ||From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of ||Sue Sivets ||Sent: Wednesday, January 06, 2010 9:18 PM ||To: LINUX-390@VM.MARIST.EDU ||Subject: sles11 - adding dasd yast problem || ||I have just finished installing Sles 11, and now I need to add two ||mini-disks. The first is read only, the second is read-write. I tried ||running mkinitrd zipl like I would for sles10, but it doesn't seem to ||be working. Mkinitrd is only writing 6 or 8 lines to the console (it ||writes almost a screen full on sles10), and it seems to be changing the ||disk identifier from dasdc dasdd to dasda or dasdb so that /etc/fstab ||ends up being correct for the current ipl, but not the next. I guess ||zipl is working, at least the system seems to boot. If I run mkinitrd ||zipl manually, the new disks don't seem to be picked up and added to |the ||dasd configuration so they are avail for the next ipl. If I use ||yast-hardware-dasd to activate them, then the dasd id is changed, and ||the disks seem to be varied online at the next ipl. || ||How do I get the dasd added and mounted at each ipl? ||Can I add dasd without using yast and if so how? What commands do I |need ||to run? || ||Problem #2 - When I try to run yast2, I get an error message that |Xlib: ||extension RANDR missing on display localhost:10.0 along with a |bunch ||of other messages. I thought I saw something about Gnome in an earlier ||error message, and I did not install either Gnome of KDE since I was ||doing a z/linux install, and neither of these have worked very well on ||previous sles versions. yast seems to work so far, but I much prefer ||yast2. || ||Can anyone shed any light on either of these problems? || ||Thank you || ||Sue Sivets || ||-- || Suzanne Sivets || Systems Programmer || Innovation Data Processing || 275 Paterson Ave || Little Falls, NJ 07424-1658 || 973-890-7300 || Fax 973-890-7147 || ssiv...@fdrinnovation.com || || || ||This email (and attachments, if any) is confidential and access by ||anyone other than the addressee(s) is unauthorized. We would |appreciate ||your notifying the sender and supp...@fdrinnovation.com immediately if ||you are not the intended recipient of this message. || ||-- ||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 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 This email (and attachments, if any) is confidential and access by anyone other than the addressee(s) is unauthorized. We would appreciate your notifying the sender and supp...@fdrinnovation.com immediately if you are not the intended recipient of this message. -- Suzanne Sivets Systems Programmer Innovation Data Processing 275 Paterson Ave Little Falls, NJ 07424-1658 973-890-7300 Fax 973-890-7147 ssiv...@fdrinnovation.com This email (and attachments, if any) is confidential and access by anyone other than the addressee(s) is unauthorized. We would appreciate your notifying the sender and supp...@fdrinnovation.com immediately if you are not the intended recipient of this message. -- 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
sles11 - adding dasd yast problem
I have just finished installing Sles 11, and now I need to add two mini-disks. The first is read only, the second is read-write. I tried running mkinitrd zipl like I would for sles10, but it doesn't seem to be working. Mkinitrd is only writing 6 or 8 lines to the console (it writes almost a screen full on sles10), and it seems to be changing the disk identifier from dasdc dasdd to dasda or dasdb so that /etc/fstab ends up being correct for the current ipl, but not the next. I guess zipl is working, at least the system seems to boot. If I run mkinitrd zipl manually, the new disks don't seem to be picked up and added to the dasd configuration so they are avail for the next ipl. If I use yast-hardware-dasd to activate them, then the dasd id is changed, and the disks seem to be varied online at the next ipl. How do I get the dasd added and mounted at each ipl? Can I add dasd without using yast and if so how? What commands do I need to run? Problem #2 - When I try to run yast2, I get an error message that Xlib: extension RANDR missing on display localhost:10.0 along with a bunch of other messages. I thought I saw something about Gnome in an earlier error message, and I did not install either Gnome of KDE since I was doing a z/linux install, and neither of these have worked very well on previous sles versions. yast seems to work so far, but I much prefer yast2. Can anyone shed any light on either of these problems? Thank you Sue Sivets -- Suzanne Sivets Systems Programmer Innovation Data Processing 275 Paterson Ave Little Falls, NJ 07424-1658 973-890-7300 Fax 973-890-7147 ssiv...@fdrinnovation.com This email (and attachments, if any) is confidential and access by anyone other than the addressee(s) is unauthorized. We would appreciate your notifying the sender and supp...@fdrinnovation.com immediately if you are not the intended recipient of this message. -- 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
Re: sles11 - adding dasd yast problem
Sue, I think you'll need to use dasd_configure on sles 11. I'm not quite that far yet, but that's what I remember and since no one else has answered yet... :) Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Sue Sivets Sent: Wednesday, January 06, 2010 7:18 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] sles11 - adding dasd yast problem I have just finished installing Sles 11, and now I need to add two mini-disks. The first is read only, the second is read-write. I tried running mkinitrd zipl like I would for sles10, but it doesn't seem to be working. Mkinitrd is only writing 6 or 8 lines to the console (it writes almost a screen full on sles10), and it seems to be changing the disk identifier from dasdc dasdd to dasda or dasdb so that /etc/fstab ends up being correct for the current ipl, but not the next. I guess zipl is working, at least the system seems to boot. If I run mkinitrd zipl manually, the new disks don't seem to be picked up and added to the dasd configuration so they are avail for the next ipl. If I use yast-hardware-dasd to activate them, then the dasd id is changed, and the disks seem to be varied online at the next ipl. How do I get the dasd added and mounted at each ipl? Can I add dasd without using yast and if so how? What commands do I need to run? Problem #2 - When I try to run yast2, I get an error message that Xlib: extension RANDR missing on display localhost:10.0 along with a bunch of other messages. I thought I saw something about Gnome in an earlier error message, and I did not install either Gnome of KDE since I was doing a z/linux install, and neither of these have worked very well on previous sles versions. yast seems to work so far, but I much prefer yast2. Can anyone shed any light on either of these problems? Thank you Sue Sivets -- Suzanne Sivets Systems Programmer Innovation Data Processing 275 Paterson Ave Little Falls, NJ 07424-1658 973-890-7300 Fax 973-890-7147 ssiv...@fdrinnovation.com This email (and attachments, if any) is confidential and access by anyone other than the addressee(s) is unauthorized. We would appreciate your notifying the sender and supp...@fdrinnovation.com immediately if you are not the intended recipient of this message. -- 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 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
Re: adding DASD on SUSE
Mark, as dasd= parm in zipl.conf is not used now, how can I check which DASDs were supposed to be online ? Thank you === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. --- On Fri, 11/13/09, Mark Post mp...@novell.com wrote: From: Mark Post mp...@novell.com Subject: Re: adding DASD on SUSE To: LINUX-390@VM.MARIST.EDU Date: Friday, November 13, 2009, 11:01 PM On 11/13/2009 at 4:41 PM, Mark Ver mark...@us.ibm.com wrote: What I was really interested in was the Linux side configuration to add the disk permanently so that it would be online during boot up. Like were most people ... - just running a big script calling dasd_configure as Mark Post had suggested This brings the volume online _and_ creates the hwcfg file for it, thus making it permanent in the sense it will be online when you reach runlevel 3 at the next reboot. Even better, it's supported. - or do most just do chccwdev and then run mkinitrd and zipl This will not make it permanent in any practical sense, - or copy an old hwcfg-dasd-bus-ccw-* file, run mkinitrd/zipl if needed, and reboot. Not recommended, but you get to keep all the pieces. - or modify the options dasd_mod line with a dasd=dasd-list parameter in the appropriate modprobe.conf - or add a dasd=dasd-list in their kernel parameters - or use yast to add the disks (including patiently adding it all one at a time during installation). Also supported, but for large numbers of volumes, certainly not recommended. The thing you need to understand about the Linux 2.6 kernels is that the system will detect any and all DASD volumes that are accessible to it during the boot process, or later if the volume is ATTACHed or configured online to the LPAR. The need to have the 'dasd=unit1,unit2,unit3' kernel parameter isn't there any longer, per se. If you want to have read-only disks and the like, that is still somewhat useful. The real question is how do you ensure that volumes you want online are indeed online after the next reboot. For one or two, use YaST. For bunches, use dasd_configure. Your fingers will thank you for 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 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
Re: adding DASD on SUSE
sudo /sbin/lsdasd to se what dasd is online su - (just for simplicity) lsdasd vmcp link VMUSERLX 300 300 MR = link to new disk added in VM profile chccwdev -e 300 = make it online, should now be visible with lsdasd ___ Tore Agblad Volvo Information Technology Infrastructure Mainframe Design Development, Linux servers Dept 4352 DA1S SE-405 08, Gothenburg Sweden 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-...@vm.marist.edu] On Behalf Of Marian Gasparovic Sent: den 20 november 2009 11:26 To: LINUX-390@VM.MARIST.EDU Subject: Re: adding DASD on SUSE Mark, as dasd= parm in zipl.conf is not used now, how can I check which DASDs were supposed to be online ? Thank you === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. --- On Fri, 11/13/09, Mark Post mp...@novell.com wrote: From: Mark Post mp...@novell.com Subject: Re: adding DASD on SUSE To: LINUX-390@VM.MARIST.EDU Date: Friday, November 13, 2009, 11:01 PM On 11/13/2009 at 4:41 PM, Mark Ver mark...@us.ibm.com wrote: What I was really interested in was the Linux side configuration to add the disk permanently so that it would be online during boot up. Like were most people ... - just running a big script calling dasd_configure as Mark Post had suggested This brings the volume online _and_ creates the hwcfg file for it, thus making it permanent in the sense it will be online when you reach runlevel 3 at the next reboot. Even better, it's supported. - or do most just do chccwdev and then run mkinitrd and zipl This will not make it permanent in any practical sense, - or copy an old hwcfg-dasd-bus-ccw-* file, run mkinitrd/zipl if needed, and reboot. Not recommended, but you get to keep all the pieces. - or modify the options dasd_mod line with a dasd=dasd-list parameter in the appropriate modprobe.conf - or add a dasd=dasd-list in their kernel parameters - or use yast to add the disks (including patiently adding it all one at a time during installation). Also supported, but for large numbers of volumes, certainly not recommended. The thing you need to understand about the Linux 2.6 kernels is that the system will detect any and all DASD volumes that are accessible to it during the boot process, or later if the volume is ATTACHed or configured online to the LPAR. The need to have the 'dasd=unit1,unit2,unit3' kernel parameter isn't there any longer, per se. If you want to have read-only disks and the like, that is still somewhat useful. The real question is how do you ensure that volumes you want online are indeed online after the next reboot. For one or two, use YaST. For bunches, use dasd_configure. Your fingers will thank you for 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 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 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
Re: adding DASD on SUSE
Tore, lsdasd shows disks that are online. My question is how ot find which disks were supposed to be online, in other words, which disks were configured by dasd_configure to be online on the next boot. Say you have 20 disks in your image, you realize something is missing (maybe some misconfig on VM side, or disk problem, whatever) and you want to check which dasd is not online although you set it to be online on each boot. === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. --- On Fri, 11/20/09, Agblad Tore tore.agb...@volvo.com wrote: From: Agblad Tore tore.agb...@volvo.com Subject: Re: adding DASD on SUSE To: LINUX-390@VM.MARIST.EDU Date: Friday, November 20, 2009, 11:40 AM sudo /sbin/lsdasd to se what dasd is online su - (just for simplicity) lsdasd vmcp link VMUSERLX 300 300 MR = link to new disk added in VM profile chccwdev -e 300 = make it online, should now be visible with lsdasd ___ Tore Agblad Volvo Information Technology Infrastructure Mainframe Design Development, Linux servers Dept 4352 DA1S SE-405 08, Gothenburg Sweden 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-...@vm.marist.edu] On Behalf Of Marian Gasparovic Sent: den 20 november 2009 11:26 To: LINUX-390@VM.MARIST.EDU Subject: Re: adding DASD on SUSE Mark, as dasd= parm in zipl.conf is not used now, how can I check which DASDs were supposed to be online ? Thank you === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. --- On Fri, 11/13/09, Mark Post mp...@novell.com wrote: From: Mark Post mp...@novell.com Subject: Re: adding DASD on SUSE To: LINUX-390@VM.MARIST.EDU Date: Friday, November 13, 2009, 11:01 PM On 11/13/2009 at 4:41 PM, Mark Ver mark...@us.ibm.com wrote: What I was really interested in was the Linux side configuration to add the disk permanently so that it would be online during boot up. Like were most people ... - just running a big script calling dasd_configure as Mark Post had suggested This brings the volume online _and_ creates the hwcfg file for it, thus making it permanent in the sense it will be online when you reach runlevel 3 at the next reboot. Even better, it's supported. - or do most just do chccwdev and then run mkinitrd and zipl This will not make it permanent in any practical sense, - or copy an old hwcfg-dasd-bus-ccw-* file, run mkinitrd/zipl if needed, and reboot. Not recommended, but you get to keep all the pieces. - or modify the options dasd_mod line with a dasd=dasd-list parameter in the appropriate modprobe.conf - or add a dasd=dasd-list in their kernel parameters - or use yast to add the disks (including patiently adding it all one at a time during installation). Also supported, but for large numbers of volumes, certainly not recommended. The thing you need to understand about the Linux 2.6 kernels is that the system will detect any and all DASD volumes that are accessible to it during the boot process, or later if the volume is ATTACHed or configured online to the LPAR. The need to have the 'dasd=unit1,unit2,unit3' kernel parameter isn't there any longer, per se. If you want to have read-only disks and the like, that is still somewhat useful. The real question is how do you ensure that volumes you want online are indeed online after the next reboot. For one or two, use YaST. For bunches, use dasd_configure. Your fingers will thank you for 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 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 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 LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
Re: adding DASD on SUSE
On Fri, Nov 20, 2009 at 12:02 PM, Marian Gasparovic mar...@yahoo.com wrote: lsdasd shows disks that are online. My question is how ot find which disks were supposed to be online, in other words, which disks were configured by dasd_configure to be online on the next boot. Say you have 20 disks in your image, you realize something is missing (maybe some misconfig on VM side, or disk problem, whatever) and you want to check which dasd is not online although you set it to be online on each boot. The output of vmcp query virtual dasd would have to be combined with lsdasd (and you probably keep out the R/O disks and maybe also very small disks). I am sure others can do that in bash/perl as easy as I could with CMS Pipelines ;-) And if your question is slightly wider, you could also consider the output of vmcp query mdisk 0-fff dir to find the disks that have been defined for you already, but possibly not linked (so you can issue a LINK for those). Rob -- 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
Re: adding DASD on SUSE
Marian, You could do lsdasd when the guest's running normally and save the lsdasd output somewhere safe to compare against lsdasd's output when something is missing. Simpler than looking at all the ways and places that could put dasd online: dasd_configure's output files (different on sles9,10 than 11), boot.local, initrd, ... -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Marian Gasparovic Sent: Friday, November 20, 2009 6:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: adding DASD on SUSE Tore, lsdasd shows disks that are online. My question is how ot find which disks were supposed to be online, in other words, which disks were configured by dasd_configure to be online on the next boot. Say you have 20 disks in your image, you realize something is missing (maybe some misconfig on VM side, or disk problem, whatever) and you want to check which dasd is not online although you set it to be online on each boot. === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. --- On Fri, 11/20/09, Agblad Tore tore.agb...@volvo.com wrote: From: Agblad Tore tore.agb...@volvo.com Subject: Re: adding DASD on SUSE To: LINUX-390@VM.MARIST.EDU Date: Friday, November 20, 2009, 11:40 AM sudo /sbin/lsdasd to se what dasd is online su - (just for simplicity) lsdasd vmcp link VMUSERLX 300 300 MR = link to new disk added in VM profile chccwdev -e 300 = make it online, should now be visible with lsdasd This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -- 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
Re: adding DASD on SUSE
On 11/20/2009 at 5:26 AM, Marian Gasparovic mar...@yahoo.com wrote: Mark, as dasd= parm in zipl.conf is not used now, how can I check which DASDs were supposed to be online ? Look in /etc/sysconfig/hardware/ for hwcfg files for DASD. 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
Re: adding DASD on SUSE
Check in /etc/sysconfig/hardware and look for files for each disk called something like hwcfg-dasd-bus-ccw-0.0. marcy Tore, lsdasd shows disks that are online. My question is how ot find which disks were supposed to be online, in other words, which disks were configured by dasd_configure to be online on the next boot. Say you have 20 disks in your image, you realize something is missing (maybe some misconfig on VM side, or disk problem, whatever) and you want to check which dasd is not online although you set it to be online on each boot. === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. --- On Fri, 11/20/09, Agblad Tore tore.agb...@volvo.com wrote: From: Agblad Tore tore.agb...@volvo.com Subject: Re: adding DASD on SUSE To: LINUX-390@VM.MARIST.EDU Date: Friday, November 20, 2009, 11:40 AM sudo /sbin/lsdasd to se what dasd is online su - (just for simplicity) lsdasd vmcp link VMUSERLX 300 300 MR = link to new disk added in VM profile chccwdev -e 300 = make it online, should now be visible with lsdasd This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -- 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 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
Re: adding DASD on SUSE
Sorry, I was talking about SLES 11 which does not support dasd= parameter and does not use hwcfg files. Looks like the only solution now is to save lsdasd output when everything is ok. === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. --- On Fri, 11/20/09, Mark Post mp...@novell.com wrote: From: Mark Post mp...@novell.com Subject: Re: adding DASD on SUSE To: LINUX-390@VM.MARIST.EDU Date: Friday, November 20, 2009, 4:15 PM On 11/20/2009 at 5:26 AM, Marian Gasparovic mar...@yahoo.com wrote: Mark, as dasd= parm in zipl.conf is not used now, how can I check which DASDs were supposed to be online ? Look in /etc/sysconfig/hardware/ for hwcfg files for DASD. 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 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
Re: adding DASD on SUSE
On 11/20/2009 at 10:34 AM, Marian Gasparovic mar...@yahoo.com wrote: Sorry, I was talking about SLES 11 which does not support dasd= parameter and does not use hwcfg files. Oh. In that case, look in /etc/udev/rules.d/ for 51-dasd-*.rules files. 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
Re: adding DASD on SUSE
Thank you, that was exactly what I was looking for. === Marian Gasparovic === The mere thought hadn't even begun to speculate about the merest possibility of crossing my mind. --- On Fri, 11/20/09, Mark Post mp...@novell.com wrote: From: Mark Post mp...@novell.com Subject: Re: adding DASD on SUSE To: LINUX-390@VM.MARIST.EDU Date: Friday, November 20, 2009, 4:38 PM On 11/20/2009 at 10:34 AM, Marian Gasparovic mar...@yahoo.com wrote: Sorry, I was talking about SLES 11 which does not support dasd= parameter and does not use hwcfg files. Oh. In that case, look in /etc/udev/rules.d/ for 51-dasd-*.rules files. 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 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
Re: adding DASD on SUSE
Mark, Like were most people ... I like this one: - or add a dasd=dasd-list in their kernel parameters because then you can go to /etc/zipl.conf to see which disks (or disks and slots) the system is supposed to have. And if you do leave slots open, you can add DASD more easily. Mike MacIsaac mike...@us.ibm.com (845) 433-7061 -- 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
Re: adding DASD on SUSE
What I was really interested in was the Linux side configuration to add the disk permanently so that it would be online during boot up. Like were most people ... - just running a big script calling dasd_configure as Mark Post had suggested - or do most just do chccwdev and then run mkinitrd and zipl - or copy an old hwcfg-dasd-bus-ccw-* file, run mkinitrd/zipl if needed, and reboot. - or modify the options dasd_mod line with a dasd=dasd-list parameter in the appropriate modprobe.conf - or add a dasd=dasd-list in their kernel parameters - or use yast to add the disks (including patiently adding it all one at a time during installation). - Mark Ver office: Building 710 / Room 2-RF-10 phone: (845) 435-7794 [tie 8 295-7794] -- 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
Re: adding DASD on SUSE
On 11/13/2009 at 4:41 PM, Mark Ver mark...@us.ibm.com wrote: What I was really interested in was the Linux side configuration to add the disk permanently so that it would be online during boot up. Like were most people ... - just running a big script calling dasd_configure as Mark Post had suggested This brings the volume online _and_ creates the hwcfg file for it, thus making it permanent in the sense it will be online when you reach runlevel 3 at the next reboot. Even better, it's supported. - or do most just do chccwdev and then run mkinitrd and zipl This will not make it permanent in any practical sense, - or copy an old hwcfg-dasd-bus-ccw-* file, run mkinitrd/zipl if needed, and reboot. Not recommended, but you get to keep all the pieces. - or modify the options dasd_mod line with a dasd=dasd-list parameter in the appropriate modprobe.conf - or add a dasd=dasd-list in their kernel parameters - or use yast to add the disks (including patiently adding it all one at a time during installation). Also supported, but for large numbers of volumes, certainly not recommended. The thing you need to understand about the Linux 2.6 kernels is that the system will detect any and all DASD volumes that are accessible to it during the boot process, or later if the volume is ATTACHed or configured online to the LPAR. The need to have the 'dasd=unit1,unit2,unit3' kernel parameter isn't there any longer, per se. If you want to have read-only disks and the like, that is still somewhat useful. The real question is how do you ensure that volumes you want online are indeed online after the next reboot. For one or two, use YaST. For bunches, use dasd_configure. Your fingers will thank you for 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
Re: adding DASD on SUSE
Add the disk to the directory link the disk, format and convert to linux format detach the disk use secuser to linux server to link the disk and bring it online. That assums that you have root logged on the console. I do. Wrap it all up in an exec and you can do as many as you want. You could also start the exec up on different ids and get multiple formats going on at the same time. Calvin Fisher MVMUA web site http://vm.marist.edu/~mvmua Just out of curiosity, since SLES has many different ways to let you add DASD, what method have most folks been using to add a lot of DASD at once (like say 40 to 80 volumes) ? Thanks, - Mark Ver office: Building 710 / Room 2-RF-10 phone: (845) 435-7794 [tie 8 295-7794] -- 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 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
Re: adding DASD on SUSE
Just out of curiosity, since SLES has many different ways to let you add DASD, what method have most folks been using to add a lot of DASD at once (like say 40 to 80 volumes) ? Thanks, - Mark Ver office: Building 710 / Room 2-RF-10 phone: (845) 435-7794 [tie 8 295-7794] -- 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
Re: adding DASD on SUSE
On 11/11/2009 at 4:13 PM, Mark Ver mark...@us.ibm.com wrote: Just out of curiosity, since SLES has many different ways to let you add DASD, what method have most folks been using to add a lot of DASD at once (like say 40 to 80 volumes) ? If you're asking this because you want to script it, then dasd_configure would be the easiest way. It will both bring the volume online _and_ create the hwcfg file for 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
