Re: Dasd_diag_mod question
My impression is that its more efficient, and that you would build that efficiency into your 'golden image' so that it can be leveraged with the building of each new image. I agree that in normal conditions theres negligible difference, but when the host system is being stressed and you really NEED swapping, I think the shorter I/O paths could only work in your favor. Still, I'll have to see if I'm comfortable with the number of modifications needed to implement diag, since fba mode works right out of the box. Ray Mrohs -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Marcy Cortes Sent: Wednesday, July 29, 2009 7:33 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Dasd_diag_mod question Question, what is the value of using diag for swapping to vdisk? Even if it is a more efficient driver, you're swapping to memory. How much does it save? And how much swapping would you need to be doing for any savings to be worthwhile? Wouldn't it be simpler to just increase the VM size to an amount that minimizes swapping? Or are there servers you *want* swapping a lot for some reason and if so why? Inquiring minds... Marcy -- 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: ISCSI, SUSE and Installation
Right, which is why I prefer to install the base Linux image onto more conventional disk, like 3390 DASD. Once the Linux kernel successfully boots, it can then begin to exploit the more unconventional (at least in a S/390 sense) disks like FCP. Andrew Galewsky wrote: The interesting thing of course is that the yast installation intimates that it is ok to put everything but /boot on the remote disk. The problem comes is I think that since /etc/init.d and the other stuff isnt mounted so you cant really get the system up enough to move things around! On 7/24/09 2:31 PM, Dave Jones d...@vsoft-software.com wrote: Yes, it does, Andy. Can you move the iSCSI startup to someplace later in the boot process, after the network has come up? Andy Galewsky wrote: It appears that iSCSI is trying to start before the Ethernet is actually up Cannot find device eth0 SIOCGIFFLAGS: No such device RTNETLINK answers: Network is unreachable Starting iSCSI daemon Login session 10.37.1.72:3260 iqn.2006-01.com.openfiler:tsn.3386c86c41ee iscsiadm: Could not login session (err 4). -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Dave Jones Sent: Thursday, July 23, 2009 7:59 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: ISCSI, SUSE and Installation Hi, Andy. What error, exactly, does the initiator report at boot time? What's on the Linux console? -- 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 -- Dave Jones V/Soft www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For 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 -- Dave Jones V/Soft www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
OSA config on new machine
I am moving one of my SUSE 10 images to a different machine where the OSA has a different hardware address. We do not have VM (very sad, I know). The address will be changing from f840 to b708, the name will change from GIGPORT1 to OSAEGA0 and the IP will go from 10.5.100.31 to 10.50.40.121 I have renamed /etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0.f840 to etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0.b708 and changed: STARTMODE='auto' MODULE='qeth' MODULE_OPTIONS='' MODULE_UNLOAD='yes' SCRIPTUP='hwup-ccw' SCRIPTUP_ccw='hwup-ccw' SCRIPTUP_ccwgroup='hwup-qeth' SCRIPTDOWN='hwdown-ccw' CCW_CHAN_IDS='0.0.f840 0.0.f841 0.0.f842' CCW_CHAN_NUM='3' CCW_CHAN_MODE='GIGPORT1' QETH_LAYER2_SUPPORT='0' LCS_LANCMD_TIMEOUT='' QETH_IPA_TAKEOVER='0' QETH_OPTIONS='' TO STARTMODE='auto' MODULE='qeth' MODULE_OPTIONS='' MODULE_UNLOAD='yes' SCRIPTUP='hwup-ccw' SCRIPTUP_ccw='hwup-ccw' SCRIPTUP_ccwgroup='hwup-qeth' SCRIPTDOWN='hwdown-ccw' CCW_CHAN_IDS='0.0.b708 0.0.b709 0.0.b70E' CCW_CHAN_NUM='3' CCW_CHAN_MODE='OSAEGA0' QETH_LAYER2_SUPPORT='0' LCS_LANCMD_TIMEOUT='' QETH_IPA_TAKEOVER='0' QETH_OPTIONS='' I also renamed /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0.f840 to /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0.b708 and changed BOOTPROTO='static' UNIQUE='' STARTMODE='auto' IPADDR='10.5.100.31' NETMASK='255.255.0.0' NETWORK='' BROADCAST='' _nm_name='qeth-bus-ccw-0.0.f840' ETHTOOL_OPTIONS='' LLADDR='' MTU='' NAME='' REMOTE_IPADDR='' USERCONTROL='no' TO BOOTPROTO='static' UNIQUE='' STARTMODE='auto' IPADDR='10.50.40.121' NETMASK='255.255.255.224' NETWORK='' BROADCAST='' _nm_name='qeth-bus-ccw-0.0.b708' ETHTOOL_OPTIONS='' LLADDR='' MTU='' NAME='' REMOTE_IPADDR='' USERCONTROL='no' When SuSE comes up on the new box, I get a message saying qeth-bus-ccw-0.0.b708 No interface found Any ideas what the problem might be? Are there more changes that need to be made to Linux, or do I need to look into the IO def for the LPAR? Thank you for your help, Russell Jones ANPAC System Programmer Trainee rjo...@anpac.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
Re: OSA config on new machine
On 8/3/2009 at 4:51 PM, Jones, Russell russell.jo...@anpac.com wrote: I am moving one of my SUSE 10 images to a different machine where the OSA has a different hardware address. We do not have VM (very sad, I know). The address will be changing from f840 to b708, the name will change from GIGPORT1 to OSAEGA0 and the IP will go from 10.5.100.31 to 10.50.40.121 -snip- When SuSE comes up on the new box, I get a message saying qeth-bus-ccw-0.0.b708 No interface found Any ideas what the problem might be? Are there more changes that need to be made to Linux, or do I need to look into the IO def for the LPAR? What does lscss and lsqeth report? 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: OSA config on new machine
Can I list a range of address with lscss? It is listing too many devices to see the range that I need. 'lsqeth' reports: ls: /sys/bus/ccwgroup/drivers/qeth: No such file or directory Russell Jones ANPAC System Programmer Trainee rjo...@anpac.com -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Monday, August 03, 2009 4:00 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: OSA config on new machine On 8/3/2009 at 4:51 PM, Jones, Russell russell.jo...@anpac.com wrote: I am moving one of my SUSE 10 images to a different machine where the OSA has a different hardware address. We do not have VM (very sad, I know). The address will be changing from f840 to b708, the name will change from GIGPORT1 to OSAEGA0 and the IP will go from 10.5.100.31 to 10.50.40.121 -snip- When SuSE comes up on the new box, I get a message saying qeth-bus-ccw-0.0.b708 No interface found Any ideas what the problem might be? Are there more changes that need to be made to Linux, or do I need to look into the IO def for the LPAR? What does lscss and lsqeth report? 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: OSA config on new machine
On 08/03/2009 10:51 PM, Jones, Russell wrote: I am moving one of my SUSE 10 images to a different machine where the OSA has a different hardware address. We do not have VM (very sad, I know). The address will be changing from f840 to b708, the name will change from GIGPORT1 to OSAEGA0 and the IP will go from 10.5.100.31 to 10.50.40.121 CCW_CHAN_IDS='0.0.b708 0.0.b709 0.0.b70E' Shouldn't this be?: CCW_CHAN_IDS='0.0.b708 0.0.b709 0.0.b70a' Assuming the triplets are defined subsequently (which wouldn't be necessary for the data channel). Also, it is a safe choice to specify hex digits in lower case letters for Linux. Steffen Linux on System z Development IBM Deutschland Research Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Erich Baier 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
Re: OSA config on new machine
On 08/03/2009 11:08 PM, Jones, Russell wrote: Can I list a range of address with lscss? It is listing too many devices to see the range that I need. Just a quick hack which should definitely work to reduce the result set: lscss | fgrep 0.0.b70 Steffen Linux on System z Development IBM Deutschland Research Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Erich Baier 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
Re: OSA config on new machine
Good idea. I get no hits on that address range. Looks like the addresses are not available to the LPAR. Thanks. Now I know who to complain to. Russell Jones ANPAC System Programmer Trainee rjo...@anpac.com (417)887-4990 x2193 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Steffen Maier Sent: Monday, August 03, 2009 4:21 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: OSA config on new machine On 08/03/2009 11:08 PM, Jones, Russell wrote: Can I list a range of address with lscss? It is listing too many devices to see the range that I need. Just a quick hack which should definitely work to reduce the result set: lscss | fgrep 0.0.b70 Steffen Linux on System z Development IBM Deutschland Research Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Erich Baier 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 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: OSA config on new machine
On 8/3/2009 at 5:29 PM, Jones, Russell russell.jo...@anpac.com wrote: Good idea. I get no hits on that address range. Looks like the addresses are not available to the LPAR. Try it again and use the -i switch on grep, since lscss reports everything in upper case: lscss | grep -i 0.b70 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
