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 that.
Re: Suggestion on improving FTP large file transfer
Thank Bruce, good information. Question, Pg 13 TCP segmentation offload(TSO) . My guests are using a VSWITCH with VLAN Tags. Would offload still apply ? Thanks Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bruce Hayden Sent: Monday, August 10, 2015 12:02 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suggestion on improving FTP large file transfer Start out by looking at the Network tuning presentation on this page: http://www.ibm.com/developerworks/linux/linux390/perf/tuning_networking.html It has suggestions for tuning the networking on Linux for these types of transfers. On Mon, Aug 10, 2015 at 10:45 AM, Vitale, Joseph joseph.vit...@bnymellon.com wrote: Hello, We have approximately 30Gb to FTP, zLinux to zOS. Would like to improve FTP timing but found TCP Receive Socket window default/max is 32Mb. Also, Send Socket window default/max is 32 Mb. Window scaling is enabled. Have not checked zOS Blocksize or number of extents. Not sure if quote site comes into play FTPing to zLinux? Running Red Hat 6.6 under zVM 6.3 Thanks Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. -- 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/ -- Bruce Hayden z/VM and Linux on z Systems ATS IBM, Endicott, NY -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities.
Re: Suggestion on improving FTP large file transfer
z/OS and zLinux are on the same box? Did you consider using HiperSockets? Also make sure your mtu is configured to the maximum allowed by your network... One more thing is to make sure your zLinux is getting enough cpu and that you don't have any steal (you can monitor it using top/sar/vmstat) Good luck Offer Baruch On Aug 11, 2015 1:40 PM, Vitale, Joseph joseph.vit...@bnymellon.com wrote: Thank Bruce, good information. Question, Pg 13 TCP segmentation offload(TSO) . My guests are using a VSWITCH with VLAN Tags. Would offload still apply ? Thanks Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bruce Hayden Sent: Monday, August 10, 2015 12:02 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suggestion on improving FTP large file transfer Start out by looking at the Network tuning presentation on this page: http://www.ibm.com/developerworks/linux/linux390/perf/tuning_networking.html It has suggestions for tuning the networking on Linux for these types of transfers. On Mon, Aug 10, 2015 at 10:45 AM, Vitale, Joseph joseph.vit...@bnymellon.com wrote: Hello, We have approximately 30Gb to FTP, zLinux to zOS. Would like to improve FTP timing but found TCP Receive Socket window default/max is 32Mb. Also, Send Socket window default/max is 32 Mb. Window scaling is enabled. Have not checked zOS Blocksize or number of extents. Not sure if quote site comes into play FTPing to zLinux? Running Red Hat 6.6 under zVM 6.3 Thanks Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. -- 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/ -- Bruce Hayden z/VM and Linux on z Systems ATS IBM, Endicott, NY -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. -- 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
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: Suggestion on improving FTP large file transfer
According to the document, TSO only applies if the OSA connection is layer 3 and directly attached (so dedicated under z/VM.) Ignore this since you are using a vswitch. On Mon, Aug 10, 2015 at 1:27 PM, Vitale, Joseph joseph.vit...@bnymellon.com wrote: Thank Bruce, good information. Question, Pg 13 TCP segmentation offload(TSO) . My guests are using a VSWITCH with VLAN Tags. Would offload still apply ? Thanks Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bruce Hayden Sent: Monday, August 10, 2015 12:02 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suggestion on improving FTP large file transfer Start out by looking at the Network tuning presentation on this page: http://www.ibm.com/developerworks/linux/linux390/perf/tuning_networking.html It has suggestions for tuning the networking on Linux for these types of transfers. On Mon, Aug 10, 2015 at 10:45 AM, Vitale, Joseph joseph.vit...@bnymellon.com wrote: Hello, We have approximately 30Gb to FTP, zLinux to zOS. Would like to improve FTP timing but found TCP Receive Socket window default/max is 32Mb. Also, Send Socket window default/max is 32 Mb. Window scaling is enabled. Have not checked zOS Blocksize or number of extents. Not sure if quote site comes into play FTPing to zLinux? Running Red Hat 6.6 under zVM 6.3 Thanks Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. -- 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/ -- Bruce Hayden z/VM and Linux on z Systems ATS IBM, Endicott, NY -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. -- Bruce Hayden z/VM and Linux on z Systems ATS IBM, Endicott, NY -- 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
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: Suggestion on improving FTP large file transfer
On Tuesday, 08/11/2015 at 03:06 EDT, Bruce Hayden bjhay...@gmail.com wrote: According to the document, TSO only applies if the OSA connection is layer 3 and directly attached (so dedicated under z/VM.) Ignore this since you are using a vswitch. The VSWITCH does not virtualize the TSO function of OSA. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: 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: Suggestion on improving FTP large file transfer - Thank You
Thank you all very much. Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bruce Hayden Sent: Tuesday, August 11, 2015 3:05 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suggestion on improving FTP large file transfer According to the document, TSO only applies if the OSA connection is layer 3 and directly attached (so dedicated under z/VM.) Ignore this since you are using a vswitch. On Mon, Aug 10, 2015 at 1:27 PM, Vitale, Joseph joseph.vit...@bnymellon.com wrote: Thank Bruce, good information. Question, Pg 13 TCP segmentation offload(TSO) . My guests are using a VSWITCH with VLAN Tags. Would offload still apply ? Thanks Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bruce Hayden Sent: Monday, August 10, 2015 12:02 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Suggestion on improving FTP large file transfer Start out by looking at the Network tuning presentation on this page: http://www.ibm.com/developerworks/linux/linux390/perf/tuning_networkin g.html It has suggestions for tuning the networking on Linux for these types of transfers. On Mon, Aug 10, 2015 at 10:45 AM, Vitale, Joseph joseph.vit...@bnymellon.com wrote: Hello, We have approximately 30Gb to FTP, zLinux to zOS. Would like to improve FTP timing but found TCP Receive Socket window default/max is 32Mb. Also, Send Socket window default/max is 32 Mb. Window scaling is enabled. Have not checked zOS Blocksize or number of extents. Not sure if quote site comes into play FTPing to zLinux? Running Red Hat 6.6 under zVM 6.3 Thanks Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. -- 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/ -- Bruce Hayden z/VM and Linux on z Systems ATS IBM, Endicott, NY -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. -- Bruce Hayden z/VM and Linux on z Systems ATS IBM, Endicott, NY -- 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 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/
