Re: BMC BladeLogic
We're waiting for it too. Supposedly the version that supported z was to be available in November, but we've had no news. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Rick Truett Sent: Friday, December 04, 2009 9:14 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] BMC BladeLogic Greetings, I have been searching BMC's site and could find an answer to 'does BMC certify their BladeLogic suite on zLinux?' Would anyone on the Listserv know? -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. The information contained in this e-mail was obtained from sources believed to be reliable; however, the accuracy or completeness of this information is not guaranteed. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Past performance is no guarantee of future results. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: When will CMMA be removed from the kernel?
All of our RHEL4 guests are pre-update-7 and unlikely to be upgraded any time soon. I think I've seen this doc before. Thanks though. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of dave Sent: Tuesday, September 22, 2009 9:35 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] When will CMMA be removed from the kernel? This presentation might be of some interest to those looking at the CMM-1 and CMM2/CMMA options: http://www.linuxvm.org/Present/SHARE113/S9272lj.pdf Enjoy. DJ - Original Message - From: "Hall, Ken (GTS)" To: LINUX-390@VM.MARIST.EDU Subject: Re: When will CMMA be removed from the kernel? Date: Wed, 23 Sep 2009 11:45:29 -0400 > We tried CMM-1 a month or two ago on a single guest. > Without VMRM, there's nothing for it to talk to, so it > does nothing. (It works by having VMRM send it notices to > decrease working set size.) > > With it enabled on one guest, on a machine slightly memory > constrained, it drove the memory utilization of the guest > down to the point that it wouldn't run at all. Obviously, > it has to be enabled on a significant percentage of your > guests to be useful. > > Most of ours are RHEL4 though, so (I believe) that's out > of the question. We're still evaluating. > > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] > On Behalf Of Michael MacIsaac > Sent: Wednesday, September 23, 2009 10:51 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] When will CMMA be removed from > the kernel? > > Sam, > > > We load the CMM module via > > /etc/sysconfig/kernel > > MODULES_LOADED_ON_BOOT="vmcp cmm" > > > > So what is it that we have turned on? > Good question. You've turned on CMM1 on Linux, but as I > understand it, there must also be a *collaborative* piece > enabled on z/VM. > > In both the latest Virtualization Cookbooks > (ibm.com/redbooks), and the SLES 10 SP2 "read-only" root > paper (linuxvm.org/present), there is a writeup on how to > use CMM1 (much of this section was written by Ray Mansell > - thanks Ray!). Search for "Enabling Collaborative Memory > Management". It discusses how to also enable the > collaborative piece: VMRM > on z/VM. > > I'm curious that Barton wrote on August 28th: > > VMRM has taken so much storage away from servers that > > the server or application dies. I would HIGHLY > recommend against using it. > > But he wrote today: > > CMM-1 has very positive results > > So does CMM-1 have positive results without the > collaborative piece? Barton, could you point to some > numbers showing CMM-1 with positive results without VMRM? > Did you use a different z/VM collaborative piece? Thanks. > > "Mike MacIsaac"(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 > > -- > This message w/attachments (message) may > be privileged, confidential or proprietary, and if you are > not an intended recipient, please notify the sender, do > not use or share it and delete it. Unless specifically > indicated, this message is not an offer to sell or a > solicitation of any investment products or other financial > product or service, an official confirmation of any > transaction, or an official statement of Merrill Lynch. > Subject to applicable law, Merrill Lynch may monitor, > review and retain e-communications (EC) traveling through > its networks/systems. The laws of the country of each > sender/recipient may impact the handling of EC, and EC may > be archived, supervised and produced in countries other > than the country in which you are located. This message > cannot be guaranteed to be secure or error-free. > References to "Merrill Lynch" are references to any > company in the Merrill Lynch & Co., Inc. group of > companies, which are wholly-owned by Bank of America > Corporation. Securities and Insurance Products: * Are Not > FDIC Insured * Are Not Bank Guaranteed * May Lose Value * > Are Not a Bank Deposit * Are Not a Condition to Any > Banking Service or Activity * Are Not Insured by Any > Federal Government Agency. Attachments that are part of > this E-communication may have additional important > disclosures and disclaimers, which you should read. This > message is subject to terms available at the following > link: http://www.ml.com/e-co
Re: When will CMMA be removed from the kernel?
We tried CMM-1 a month or two ago on a single guest. Without VMRM, there's nothing for it to talk to, so it does nothing. (It works by having VMRM send it notices to decrease working set size.) With it enabled on one guest, on a machine slightly memory constrained, it drove the memory utilization of the guest down to the point that it wouldn't run at all. Obviously, it has to be enabled on a significant percentage of your guests to be useful. Most of ours are RHEL4 though, so (I believe) that's out of the question. We're still evaluating. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Michael MacIsaac Sent: Wednesday, September 23, 2009 10:51 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] When will CMMA be removed from the kernel? Sam, > We load the CMM module via > /etc/sysconfig/kernel > MODULES_LOADED_ON_BOOT="vmcp cmm" > > So what is it that we have turned on? Good question. You've turned on CMM1 on Linux, but as I understand it, there must also be a *collaborative* piece enabled on z/VM. In both the latest Virtualization Cookbooks (ibm.com/redbooks), and the SLES 10 SP2 "read-only" root paper (linuxvm.org/present), there is a writeup on how to use CMM1 (much of this section was written by Ray Mansell - thanks Ray!). Search for "Enabling Collaborative Memory Management". It discusses how to also enable the collaborative piece: VMRM on z/VM. I'm curious that Barton wrote on August 28th: > VMRM has taken so much storage away from servers that the > server or application dies. I would HIGHLY recommend against using it. But he wrote today: > CMM-1 has very positive results So does CMM-1 have positive results without the collaborative piece? Barton, could you point to some numbers showing CMM-1 with positive results without VMRM? Did you use a different z/VM collaborative piece? Thanks. "Mike MacIsaac"(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 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Dasd_diag_mod question
It's a religious debate at this point. We had our reasons for doing it the way we did at the time. YMMV. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of O'Brien, Dennis L Sent: Friday, September 11, 2009 2:52 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Dasd_diag_mod question I prefer running SWAPGEN under CMS before starting Linux. If my primary background were Linux, I might feel differently. Adam's fix to pick up the disk size from the directory certainly makes things easier. Dennis O'Brien My computer beat me at chess, but it was no match for me in kickboxing. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of David Boyes Sent: Friday, September 11, 2009 10:59 To: LINUX-390@VM.MARIST.EDU Subject: Re: Dasd_diag_mod question > I guess my question would be why is a complex EXEC needed to do a > normal system administration task? It's a multi-step process whether you do it at the hypervisor level or inside the Linux guest, so you're going to need some kind of scripting either way. The basic Unix philosophy is write tools that do one thing well, then use scripting to sequence the execution of the one-thing tools to accomplish bigger tasks. You could write a custom tool that did it all -- but you'd be duplicating a lot of work and you'd have to maintain it over time. Big PITA. I happen to be of the school that it's easier and simpler for this kind of preparation work to be done at the hypervisor level, and let the guest OS concentrate on identifying stuff it can use and managing the process of devices coming and going in a rational way. In this case, also, having swap is kind of necessary to getting Linux to run decently, and it's hard to do Linux stuff without a running Linux system, so creating SWAPGEN was a way to do the deed before you had a running Linux system to do it with. > A second question is why didn't > Novell provide a straightforward method for doing this and document it > in a manual (without using a complex 3rd party EXEC) ? It sounds like the issue is more that it's a 3rd party tool than that it's done the way it's done. If either of the distributors wants to include SWAPGEN, we're open to discussing the idea. No one has asked. It would be nice if the documentation included the way to set up DIAG disk I/O, though. -- db David Boyes Sine Nomine Associates -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Dasd_diag_mod question
We use two vdisks, plus one DASD swap. If the guest overflows the first vdisk,
it's time to watch it. If it overflows the second, it's time to increase the
memory.
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Pat
Carroll
Sent: Friday, September 11, 2009 1:14 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Dasd_diag_mod question
Changing the size isn't an issue for me; I size memory so that we *barely* swap
anyway. I've never has to change the size of a vdisk.
Spelling courtesy of Blackberry
- Original Message -
From: Linux on 390 Port
To: LINUX-390@VM.MARIST.EDU
Sent: Fri Sep 11 13:02:54 2009
Subject: Re: Dasd_diag_mod question
My complaint with SWAPGEN going back to when it was first announced was
that it needs to know the number of blocks to format. This means that
if the size or number of the vdisk(s) changes in the directory, the VM
admin also has to go to the target machine's 191 disk and update the
PROFILE EXEC so the right number of blocks get formatted on the right
devices. Having to change things in multiple places seemed like
something to be avoided.
So I wrote a Linux init script that does the whole thing internally
within the guest. It finds all of the FBA disks, formats them, and runs
mkswap. It also enables them in increasing priority order, so they get
used before the default DASD swap partition, and it handles the diag
module and enabling access via diag. We use this on about 100 guests,
and it works very well. My only complaint with it is that it treats all
FBA disks as swap disks, which might be a problem if we had any real FBA
disks, but since we're entirely on 3390's and the odd FCP device, it's a
non issue. It also generates one bogus error message that I never got
around to suppressing.
This version is for Red Hat (RHEL5), but it shouldn't be hard to
customize for Suse.
#!/bin/bash
# $Id: vdswap,v 1.7 2007/11/06 20:44:38 root Exp $
#
# vdswapThis shell script does the following:
# 1) Looks in sysfs for any FBA disks
# 2) If they are not already enabled for swap, it formats
# them, and enables them for swap with a higher
priority
# than the default disk swap space
#
# Should run after filesystems are mounted, before starting required
daemons
# that might need to be configured
#
# chkconfig: 2345 01 99
# Description: Formats and enables vdisk swap spaces
#
prog=`basename $0`
start() {
SYSDEV=/sys/bus/ccw/drivers/dasd-fba
echo "Enabling vdisk swap spaces "
modprobe -q dasd_diag_mod
if ls $SYSDEV | grep -q 0.0 ; then
PRIO=1
for A in $SYSDEV/0.0.*
do
DEVICE=`ls $A/block* | grep dasd | head -n 1`
if lsmod | grep -q dasd_diag_mod ; then
echo 0 > $A/online
echo 1 > $A/use_diag
echo 1 > $A/online
sleep 1
fi
DEVBASE=${DEVICE:0:${#DEVICE}-1}
if ! swapon -s | grep -q $DEVBASE ; then
parted -s /dev/$DEVBASE mkpartfs primary swap 1
mkswap /dev/$DEVICE
swapon -p $PRIO /dev/$DEVICE
let PRIO=$PRIO+1
fi
done
fi
touch /var/lock/subsys/vdswap
}
stop() {
echo -n $"Shutting down $prog: "
rm -f /var/lock/subsys/vdswap
return 0
}
# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
status)
status vdswap
RETVAL=0
;;
restart|reload)
stop
start
RETVAL=$?
;;
condrestart)
RETVAL=0
;;
*)
echo $"Usage: $0 {start|stop|restart|condrestart|status}"
exit 1
esac
exit $RETVAL
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Adam Thornton
Sent: Friday, September 11, 2009 12:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Dasd_diag_mod question
On Sep 11, 2009, at 10:36 AM, Larry Uher wrote:
> I guess my question would be why is a complex EXEC needed to do a
> normal system administration task? A second question is why didn't
> Novell provide a straightforward method for doing this and document it
> in a manual (without using a complex 3rd party EXEC) ?
Complex?
After the description and the license and update comment blocks, it's
about 240 lines. Of those, about 120 are the various ways the program
can exit (with descriptive text) and the help message. That leaves
about 120 lines of actual code, and those lines are not dense (e.g.
one line per pipe stage). That handles both the raw FBA and the DIAG
device cases.
It's not a normal system administration task on any other Linux
architecture. It's really quite unusual for your swap d
Re: Dasd_diag_mod question
Didn't seem worth it. The scheme we use works fine, and didn't require us to change PROFILE EXEC on 50-odd servers. The package containing the script was rolled out with a scheduled update on the Linux side. The directory changes could be scripted through VMSecure. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Adam Thornton Sent: Friday, September 11, 2009 1:09 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Dasd_diag_mod question On Sep 11, 2009, at 12:02 PM, Hall, Ken (GTS) wrote: > My complaint with SWAPGEN going back to when it was first announced > was > that it needs to know the number of blocks to format. This means that > if the size or number of the vdisk(s) changes in the directory, the VM > admin also has to go to the target machine's 191 disk and update the > PROFILE EXEC so the right number of blocks get formatted on the right > devices. Having to change things in multiple places seemed like > something to be avoided. Hm. Did you ever send us a requirement for that? If so, I apologize for having missed it. Since we already look for the number of blocks in the "reuse" code, I think it should be pretty straightforward to do that check and then use the number of blocks detected if the user doesn't specify. Adam -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Dasd_diag_mod question
My complaint with SWAPGEN going back to when it was first announced was
that it needs to know the number of blocks to format. This means that
if the size or number of the vdisk(s) changes in the directory, the VM
admin also has to go to the target machine's 191 disk and update the
PROFILE EXEC so the right number of blocks get formatted on the right
devices. Having to change things in multiple places seemed like
something to be avoided.
So I wrote a Linux init script that does the whole thing internally
within the guest. It finds all of the FBA disks, formats them, and runs
mkswap. It also enables them in increasing priority order, so they get
used before the default DASD swap partition, and it handles the diag
module and enabling access via diag. We use this on about 100 guests,
and it works very well. My only complaint with it is that it treats all
FBA disks as swap disks, which might be a problem if we had any real FBA
disks, but since we're entirely on 3390's and the odd FCP device, it's a
non issue. It also generates one bogus error message that I never got
around to suppressing.
This version is for Red Hat (RHEL5), but it shouldn't be hard to
customize for Suse.
#!/bin/bash
# $Id: vdswap,v 1.7 2007/11/06 20:44:38 root Exp $
#
# vdswapThis shell script does the following:
# 1) Looks in sysfs for any FBA disks
# 2) If they are not already enabled for swap, it formats
# them, and enables them for swap with a higher
priority
# than the default disk swap space
#
# Should run after filesystems are mounted, before starting required
daemons
# that might need to be configured
#
# chkconfig: 2345 01 99
# Description: Formats and enables vdisk swap spaces
#
prog=`basename $0`
start() {
SYSDEV=/sys/bus/ccw/drivers/dasd-fba
echo "Enabling vdisk swap spaces "
modprobe -q dasd_diag_mod
if ls $SYSDEV | grep -q 0.0 ; then
PRIO=1
for A in $SYSDEV/0.0.*
do
DEVICE=`ls $A/block* | grep dasd | head -n 1`
if lsmod | grep -q dasd_diag_mod ; then
echo 0 > $A/online
echo 1 > $A/use_diag
echo 1 > $A/online
sleep 1
fi
DEVBASE=${DEVICE:0:${#DEVICE}-1}
if ! swapon -s | grep -q $DEVBASE ; then
parted -s /dev/$DEVBASE mkpartfs primary swap 1
mkswap /dev/$DEVICE
swapon -p $PRIO /dev/$DEVICE
let PRIO=$PRIO+1
fi
done
fi
touch /var/lock/subsys/vdswap
}
stop() {
echo -n $"Shutting down $prog: "
rm -f /var/lock/subsys/vdswap
return 0
}
# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
status)
status vdswap
RETVAL=0
;;
restart|reload)
stop
start
RETVAL=$?
;;
condrestart)
RETVAL=0
;;
*)
echo $"Usage: $0 {start|stop|restart|condrestart|status}"
exit 1
esac
exit $RETVAL
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Adam Thornton
Sent: Friday, September 11, 2009 12:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Dasd_diag_mod question
On Sep 11, 2009, at 10:36 AM, Larry Uher wrote:
> I guess my question would be why is a complex EXEC needed to do a
> normal system administration task? A second question is why didn't
> Novell provide a straightforward method for doing this and document it
> in a manual (without using a complex 3rd party EXEC) ?
Complex?
After the description and the license and update comment blocks, it's
about 240 lines. Of those, about 120 are the various ways the program
can exit (with descriptive text) and the help message. That leaves
about 120 lines of actual code, and those lines are not dense (e.g.
one line per pipe stage). That handles both the raw FBA and the DIAG
device cases.
It's not a normal system administration task on any other Linux
architecture. It's really quite unusual for your swap device to be
destroyed and recreated every time you power on the machine. In the
normal case the swap signature sits there between power cycles.
That's why Dave and I wrote the thing in the first place--Linux does
not generally consider needing to format the swap device as part of
its normal bootup routine and rather than mess with system startup
scripts and their ordering, we thought it was a lot easier to just
take care of it in CMS before handing control to Linux, so that the
swap device was pre-prepared like it expected.
And that, by the way, is the reason Novell doesn't do it: it's not a
task that's necessary on other architectures, and Novell, not
surprisingly, likes to keep as much the same between p
Re: vmpoff=LOGOFF not working in RHEL 5.3?
The message below indicates the guest is still logged onto a terminal. I was told early on that the guest will ONLY logoff if it's running disconnected, no matter what parms you pass. It (signal shut) works fine for us with all our disconnected machines, but if I shut down from the 3270 console, I always get the disabled wait, like you show below. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Brad Hinson Sent: Friday, August 14, 2009 12:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] vmpoff=LOGOFF not working in RHEL 5.3? Michael MacIsaac wrote: > Clovis, > >> Please, try with vmphalt too. >> >> root=LABEL=/ vmpoff=LOGOFF vmphalt=LOGOFF BOOT_IMAGE=0 > > Thanks for the suggestion. I tried that and there was no difference: > > # cat /proc/cmdline > cat /proc/cmdline > root=LABEL=/ vmpoff=LOGOFF vmphalt=LOGOFF BOOT_IMAGE=0 > # halt > halt > That should be vmhalt, not vmphalt. The reason vmpoff didn't work the first time is that '/sbin/halt' halts the system without doing a true poweroff instruction (thus leaving the system halted but on), whereas '/sbin/poweroff' does a halt+poweroff. 'shutdown -h now' does a poweroff also, which is why that worked the 2nd time. If you have vmpoff=LOGOFF vmhalt=LOGOFF, you have all your bases covered. Any time the system halts, it'll logoff, regardless of whether you run the command to perform an actual poweroff. -Brad > Broadcast message from root (console) (Fri Aug 14 12:01:52 2009): > > The system is going down for system halt NOW! > ... > 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP > stop from > CPU 01. > 01: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP > stop and > store status from CPU 01. > > The user ID remains logged on. Then I reboot and try a "shutdown -h now" > and the behavior is different (I naively thought that "halt" and "shutdown > -h now" were the same): > # shutdown -h now > ... > And in fact the system does get logged off > > Then I reboot again and go to MAINT and do a: > ==> signal shutdown rh5rwmnt > > And I see the system go down on the 3270 session, however it does not > logoff, it goes to disabled wait: > 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP > stop from > CPU 01. > 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 > 0FFF > > Back on MAINT I see: > > HCPSIG2113I User RH5RWMNT has reported successful termination > > However, the user ID remains running: > q rh5rwmnt > RH5RWMNT -L0006 > > So now I'm even more confused. But something does not seem to be working > correctly. > > "Mike MacIsaac"(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 -- Brad Hinson Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 www.redhat.com/z -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. --
Re: Lin_tape and IBMtapeutil
Try using /dev/IBMtape0n. I believe that's the "no-rewind" node. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Edmund R. MacKenty Sent: Tuesday, June 23, 2009 12:21 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Lin_tape and IBMtapeutil On Tuesday 23 June 2009 11:51, Spann, Elizebeth (Betsie) wrote: >I am trying to tar several directories to an LTO-3 tape using lin_tape, >IBMtapeutil and tar. >I open the tape device and then issue the tar commands. When I check >the tape contents with tar tvf, I only see the last directory. >I am not sure if I am not using the tar command correctly or if the tape >is rewinding after each tar command. > >IBMtapeutil -f /dev/IBMtape0 rewind >tar cvf /dev/IBMtape0 /directory1 >tar cvf /dev/IBMtape0 /directory2 > >tar tvf /dev/IBM/tape0 --- reports only on /directory2 > >Any suggestions, please? I think you're right about it rewinding the tape. I'm not sure how that tape driver works, but old-time UNIX tape drivers would rewind when the device was closed. Try writing using a single tar command: tar -cvf /dev/IBMtape0 /directory1 /directory2 That puts everything into one big tarfile onto that tape. You can list as many directories you want on the tar command line. - MacK. - Edmund R. MacKenty Software Architect Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.4321 Email: m...@rs.com Web: www.rocketsoftware.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 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Fedora 11 s390x preview
I run the same OS images on both my laptop (Vista), and a dedicated machine at home that runs Fedora 9. I move the disk image files back and forth as needed. I change one line in the Hercules config file to switch between hosts. Yes, Winpcap is required, and under Vista, you have to run Hercules as administrator, but otherwise, it's pretty straightforward. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Shockley, Gerard C Sent: Friday, June 19, 2009 1:38 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Fedora 11 s390x preview Got it working with WinPcap http://www.winpcap.org/ Then immediately switched to Linux. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Rob van der Heij Sent: Friday, June 19, 2009 8:20 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Fedora 11 s390x preview On Fri, Jun 19, 2009 at 2:12 PM, Hall, Ken (GTS) wrote: > Yes, there definitely is a Windows version of Hercules. It's linked > from the Hercules home page. > > Works pretty much like the Linux version. Once it works, maybe... If I may judge from the threads on the hercules mailing list, the windows version is making it very hard to get the network done. If you're serious about it, I'd look for a spare PC with Linux and do it there. -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 -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Fedora 11 s390x preview
Networking on the Windows version isn't terrible, but it's a bit trickier than the Linux version. If you use LCS, and have all the pieces in place, it works well enough. The documentation isn't very good though. I have it on my laptop here under Vista. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Rob van der Heij Sent: Friday, June 19, 2009 8:20 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Fedora 11 s390x preview On Fri, Jun 19, 2009 at 2:12 PM, Hall, Ken (GTS) wrote: > Yes, there definitely is a Windows version of Hercules. It's linked > from the Hercules home page. > > Works pretty much like the Linux version. Once it works, maybe... If I may judge from the threads on the hercules mailing list, the windows version is making it very hard to get the network done. If you're serious about it, I'd look for a spare PC with Linux and do it there. -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 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Fedora 11 s390x preview
Yes, there definitely is a Windows version of Hercules. It's linked from the Hercules home page. Works pretty much like the Linux version. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Phil Knirsch Sent: Friday, June 19, 2009 8:12 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Fedora 11 s390x preview On 06/19/2009 02:24 AM, Bernie Saward wrote: > Two questions > > Is this the "Zedora" that I have heard about ??? > Nope. This is the "real deal", meaning we're currently getting s390x ready as an official secondary arch for Fedora again. It took quite a bit of time and lots of politics/religion. Right now only a few minor things missing (like a proper spot for our secondary arch koji hub) until we're set in regard to infrastructure. Technically as you can see we're pretty close to being done. There are only a few hundred build failures remaining, some anaconda, NetworkManager and parted work needs to be done but other than that it's working. > Has anyone done a Windows version of the Hercules image?? As in the .init > and .cfg files and a brief howto ?? > At least i haven't looked into that yet. You might find more info how to do that on in the hercules docu and/or forums i suspect, but it shouldn't be too hard. As long as you don't need any external connection for your guest it's easy as you can simply connect to the interface via putty from your local machine. How to set up NAT/Bridging/ProxyARP on Windows though i have no clue. Regards, Phil -- Philipp Knirsch | Tel.: +49-711-96437-470 Team Lead Core Services | Fax.: +49-711-96437-111 Red Hat GmbH | Email: Phil Knirsch Hauptstaetterstr. 58 | Web: http://www.redhat.com/ D-70178 Stuttgart, Germany Motd: You're only jealous cos the little penguins are talking to me. -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: To kick or to clone ... that is the question
As I said in the beginning, we do the network configuration on first boot after cloning, so that advantage goes away too. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of William D Carroll Sent: Wednesday, June 17, 2009 2:40 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question In my original email I stated 'unless you're using flashcopy, not everyone can' EMC DASD though it can do flashcopy it cannot thru VM unless they finally added that function. the advantage I see with Kickstart is the ability to fully config the server IP, Hostname etc, plus addition of other packages beyond a default build the ability to apply customizations via script, before the server is ever brought onto the network. again, not saying cloning is better or worse, not saying Kickstarting is better or worse saying both have advantages over cloning. cloning is cool and can be very fast. I'm equally a VM and Linux person, I like taking advantage of platform features we came up with PHP scripts and a MySQL DB to manage servers point Kickstart to the php script with passed parms. look it up in the DB to pull the network info, packages to add, custom scripts and configs worked great. William 'Doug' Carroll Mainframe Systems Eng Sr I Global Technology Infrastructure ECS Core Services z/Software Group / Emerging Technologies -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of RPN01 Sent: Wednesday, June 17, 2009 2:24 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: To kick or to clone ... that is the question Another point is that cloning can take advantage of the IBM DASD Flashcopy, which Kickstart cannot. In our cloning process, copying the volumes with DDR takes roughly 8 seconds or so, for two 3390-27's. Kickstart can't copy the data onto the DASD that fast, so I don't see how it could be quicker in any sense. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 6/10/09 7:55 AM, "Scott Rohling" wrote: > Hi Doug -- Yep, we sure had some fun kicking Linux servers! > > Not sure how Linux not doing restarting itself is an IBM issue... but that > 'is' a nasty downside to kickstarting -- ending up at a 'You may safely > reboot' screen doesn't help automation. > > And we should add that kickstarting is faster than cloning 'if' the DASD is > already Linux formatted.. if not, the kickstart does the formatting, adding > time to the install. > > Scot > > On Tue, Jun 9, 2009 at 11:39 PM, WILLIAM CARROLL wrote: > >> Hi Scott, >> >> I'll jump on your bandwagon but then again you already know I perfer >> Kickstarting over cloning >> you should also mention that unless you have Flashcopy for your DASD >> Kickstarting is actually faster than cloning. >> unless your clone master is very small. >> >> as you recall ours was on a mod3 (lots of required garbage) and cloning >> that mod3 was slower than kickstarting >> also after the kickstart was done the server was ready, no additional >> steps >> to change IP's or anything. >> >> if only redhat would fix that re-ipl after the reboot. >> they say it's an IBM issue not thiers >> >> Doug Carroll >> >> >> >> - Original Message - >> From: "Scott Rohling" >> To: >> Sent: Wednesday, June 10, 2009 12:00 AM >> Subject: To kick or to clone ... that is the question >> >> >> This is a blatant request for discussion about the pros and cons of using >>> an >>> automated installation (e.g. RH kickstart - Suse autoyast (though maybe >>> this >>> has changed - I'm not current on Suse) - vs cloning a system from a >>> 'golden >>> image'... and I should say: on zSeries. >>> >>> I'm a fan of kickstart - and I'll list my reasons in approximate order of >>> importantance to me (most to least): >>> >>> - kickstart forces a scripted and recreatable installation. You specify >>> the rpm's and can do some limited scripting within the kickstart file >>> itself >>> to end up with (hopefully) a working Linux system that requires no manual >>> tweaking (at least - if you do it 'right'). The alternative is a cloned >>> system that the Linux SA's have been on, and perhaps several other teams - >>> all performing manual tasks to end up with the final product - all sorts >>> of >>> shoeprints and no good detectives. Whereas a kickstart config is >>> self-documenting - a clone is not. With good scripting and good use of >>> rpm >>> packaging for your 'local' or even 'vendor' products - you can end up with >>> a >>> very KISS config file that might even go multiplatform. (e.g. arch=`uname >>> -m` ) >>> >>> - with a proper building of conf and parm files on z/VM - a guest can be >>> kicked already configured w
Re: To kick or to clone ... that is the question
Doesn't happen if the disk is CP or CMS formatted. Doesn't happen if there's a partition table there. Only seems to happen if I've cancelled an in-progress format. I suspect it might happen if I've completed the format, but haven't partitioned yet, although I haven't tested that. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of William D Carroll Sent: Monday, June 15, 2009 3:38 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question The Console confirmation for RH was opened by me some time back as I recall the reply was it's a VM issue and only occurs if the DASD is not formatted Not DASDFMT but CMS formatted or CPFMTXA if a full pack it's really only looking for a non-blank cyl 0 if I recall so all i write something there William 'Doug' Carroll Mainframe Systems Eng Sr I Global Technology Infrastructure -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Hall, Ken (GTS) Sent: Monday, June 15, 2009 7:45 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: To kick or to clone ... that is the question Not the point. *I* know where it reboots from, I've tested it. The point was, it's not documented, along with a lot of other behaviors unique to the z platform. As I said, the kickstart doc is Intel-centric, and doesn't cover z very well. That makes it tricky to set up and maintain. I notice no one ever responded on my issue about it prompting the console for confirmation when the disk has been formatted but not partitioned. I suppose I should open an issue for that, but it's not a big priority at the moment. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of John Summerfield Sent: Saturday, June 13, 2009 7:53 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question Hall, Ken (GTS) wrote: > > "Reboot" triggers a reboot, but from where? I loaded the install kernel > from the VM reader, there's nothing there to reboot. I assume it goes > where it installed zipl, from the "bootloader" line, but it doesn't SAY > that. Where ever the system is set to boot from. On Intellish system, it's whatever the boot device is set is to. Except that, from what Brad said, it _might_ be different on z, not by design but by crude hack. Did he say, "it uses an IPL CCW?" -- Cheers John -- spambait 1...@coco.merseine.nu z1...@coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any
Re: To kick or to clone ... that is the question
Under zVM, it's a command ("IPL 100"), that that's where the confusion occurs.
At the point where the install is done, the install kernel is booted from the
VM reader. The ONLY hint of where the target system will eventually IPL from
is where you tell kickstart to install the bootloader.
But as I said, that's not specified anywhere in the doc. If I were following
the logic rigidly, I might expect it to try to boot from the reader again, but
that's obviously wrong.
I never said it behaved improperly, it works as it should. It's just not
documented very well, I think we're agreed on that.
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of John
Summerfield
Sent: Monday, June 15, 2009 1:06 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] To kick or to clone ... that is the question
Hall, Ken (GTS) wrote:
> Not the point. *I* know where it reboots from, I've tested it. The point
> was, it's not documented, along with a lot of other behaviors unique to the z
> platform.
>
> As I said, the kickstart doc is Intel-centric, and doesn't cover z very well.
> That makes it tricky to set up and maintain.
The docs are orientated towards intellish systems, true. Booting from
the default device is expected behaviour, and there has been much
discussion over the years about how to avoid install loops.
In the matter of which device a z system IPLs from, I have no experiece,
but when I last used a S/370, there was indeed a default IPL drive. We
set it with hex twist knobs. Facom systems I used were similar, except
it was done on a console, with a light pen.
>
> I notice no one ever responded on my issue about it prompting the console for
> confirmation when the disk has been formatted but not partitioned. I suppose
> I should open an issue for that, but it's not a big priority at the moment.
I thought Brad did.
>
> -Original Message-
> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of John
> Summerfield
> Sent: Saturday, June 13, 2009 7:53 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] To kick or to clone ... that is the question
>
> Hall, Ken (GTS) wrote:
>
>> "Reboot" triggers a reboot, but from where? I loaded the install kernel
>> from the VM reader, there's nothing there to reboot. I assume it goes
>> where it installed zipl, from the "bootloader" line, but it doesn't SAY
>> that.
>
> Where ever the system is set to boot from. On Intellish system, it's
> whatever the boot device is set is to.
>
> Except that, from what Brad said, it _might_ be different on z, not by
> design but by crude hack. Did he say, "it uses an IPL CCW?"
>
>
>
>
> --
>
> Cheers
> John
>
--
This message w/attachments (message) may be privileged, confidential or
proprietary, and if you are not an intended recipient, please notify the
sender, do not use or share it and delete it. Unless specifically indicated,
this message is not an offer to sell or a solicitation of any investment
products or other financial product or service, an official confirmation of any
transaction, or an official statement of Merrill Lynch. Subject to applicable
law, Merrill Lynch may monitor, review and retain e-communications (EC)
traveling through its networks/systems. The laws of the country of each
sender/recipient may impact the handling of EC, and EC may be archived,
supervised and produced in countries other than the country in which you are
located. This message cannot be guaranteed to be secure or error-free.
References to "Merrill Lynch" are references to any company in the Merrill
Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America
Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are
Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a
Condition to Any Banking Service or Activity * Are Not Insured by Any Federal
Government Agency. Attachments that are part of this E-communication may have
additional important disclosures and disclaimers, which you should read. This
message is subject to terms available at the following link:
http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you
consent to the foregoing.
--
Re: To kick or to clone ... that is the question
Not the point. *I* know where it reboots from, I've tested it. The point was, it's not documented, along with a lot of other behaviors unique to the z platform. As I said, the kickstart doc is Intel-centric, and doesn't cover z very well. That makes it tricky to set up and maintain. I notice no one ever responded on my issue about it prompting the console for confirmation when the disk has been formatted but not partitioned. I suppose I should open an issue for that, but it's not a big priority at the moment. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of John Summerfield Sent: Saturday, June 13, 2009 7:53 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question Hall, Ken (GTS) wrote: > > "Reboot" triggers a reboot, but from where? I loaded the install kernel > from the VM reader, there's nothing there to reboot. I assume it goes > where it installed zipl, from the "bootloader" line, but it doesn't SAY > that. Where ever the system is set to boot from. On Intellish system, it's whatever the boot device is set is to. Except that, from what Brad said, it _might_ be different on z, not by design but by crude hack. Did he say, "it uses an IPL CCW?" -- Cheers John -- spambait 1...@coco.merseine.nu z1...@coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. --
Re: To kick or to clone ... that is the question
So you get the 5 minutes down to what? 3-4? -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of David Boyes Sent: Wednesday, June 10, 2009 1:50 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question > David Boyes wrote: > >> Are you using NFS to host the install tree? In some recent tests, I > >> noticed a huge improvement installing over NFS when tweaking the NFS > >> mount options (rsize, wsize, tcp instead of udp, timeout). > > > > This is also one of the few cases where memory-mapping the install > repository filesystem in XSTORE on the kickstart server is worth > considering. Speeds up the process enormously at the cost of paging > space and operations. > Hmm, interesting.. do you mean creating a DCSS for the install tree? > That would be blazing fast. That's one idea (and since that filesystem usually doesn't change all that often, it'd be a nifty way to share a single copy between multiple servers -- just treat the DCSS as local disk for installation purposes). If you have a lot of install/change traffic, that might be really spiffy. I was just experimenting with ramdisks/the xpram driver and copying the install files from real disk to ramdisk at system startup. Causes lots and lots of I/O initially, but once the ramdisk is populated and exported, it's *really really really* fast to do jumpstart installs. -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: To kick or to clone ... that is the question
I don't think the documentation (from Red Hat) is all that bad in itself, it's just very Intel-centric. For example, the "clearpart" command doesn't clearly say what happens on any architecture but Intel and Itanium. Does "--initlabel" trigger dasdfmt? Yes, it does, but that's not clear. Does it clear ALL partitions? Even the 191 disk? I have other disks off to the side that I want left alone. Leaving them out of the "driveorder" list on the "bootloader" statement causes them to be ignored, but nothing says that. "cmdline" doesn't stop prompting, as my other email shows. Maybe it does on Intel, but not on Z. "Reboot" triggers a reboot, but from where? I loaded the install kernel from the VM reader, there's nothing there to reboot. I assume it goes where it installed zipl, from the "bootloader" line, but it doesn't SAY that. I could go on, but you get the idea. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of R P Herrold Sent: Wednesday, June 10, 2009 1:31 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question On Wed, 10 Jun 2009, Hall, Ken (GTS) wrote: > My main gripe with kickstart is that it's complicated, buggy (on z), and > badly documented (on z) no worries there .. it is poorly documented _everywhere_ -- as it changes and evolves per RHEL major version, and indeed within point releases, doco attempts have the attribute of chasing a changing and moving target. ;) I've written a lot about it: http://www.owlriver.com/tips/ and the LW presentation materials of Chip Shabazian's LW 2007 presentation is Highly recommended http://www.shabazian.com/lw2007.pdf There are also lively mailing lists for both anaconda and kickstart. -- Russ herrold -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: To kick or to clone ... that is the question
Tried zerombr, according to the doc, "yes" is deprecated. Doesn't help. zerombr clearpart --all --initlabel part /boot --asprimary --bytes-per-inode=4096 --fstype="ext3" --grow --ondisk=dasda --size=88 part / --asprimary --bytes-per-inode=4096 --fstype="ext3" --grow --ondisk=dasdb --size=1 part /var --asprimary --bytes-per-inode=4096 --fstype="ext3" --grow --ondisk=dasdc --size=1 part swap --asprimary --bytes-per-inode=4096 --fstype="swap" --grow --ondisk=dasdd --size=1 part pv.01 --asprimary --grow --ondisk=dasde --size=1 part pv.02 --asprimary --grow --ondisk=dasdf --size=1 part pv.03 --asprimary --grow --ondisk=dasdg --size=1 >From the kickstart documentation: zerombr (optional) If zerombr is specified any invalid partition tables found on disks are initialized. This destroys all of the contents of disks with invalid partition tables. Note that in previous versions of Red Hat Enterprise Linux, this command was specified as zerombr yes. This form is now deprecated; you should now simply specify zerombr in your kickstart file instead. -- The problem at the moment is that dasdb was partially formatted, so there actually shouldn't be any partition table there (so why is it asking?). Admittedly this isn't a "normal" situation, but it could come up where there was residual data in the minidisk space, or something crashed. And for Doug's point, by that logic, I can reduce my build time to zero by simply cloning a ready system over every disk instead of formatting. We configure instances on first-boot anyway. But this doesn't work unless you're using full volumes. Those of us using minidisks don't have the option of preformatting, so this becomes an apples-to-oranges comparison. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Brad Hinson Sent: Wednesday, June 10, 2009 1:28 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question Hall, Ken (GTS) wrote: > Even if you "preformat" the DASD, it still has to be done, so it does > take time. And if you're using minidisks, you have to format it at the > point where the guest is created. > > On a related note, anyone know how to eliminate the prompt during > kickstart?: > > Can't have a question in command line mode! > > Warning > > The partition table on device dasdb (0.0.0101) was unreadable. To create > new par > titions it must be initialized, causing the loss of ALL DATA on this > drive. > > > This operation will override any previous installation choices about > which drive > s to ignore. > > > > Would you like to initialize this drive, erasing ALL DATA? > > yesno [] > > > > I tried to format over a partially formatted minidisk, and got this. > There doesn't seem to be an option to override and just go ahead and > write. > > This is RHEL5.3. > The combination of kickstart options: clearpart --all --initlabel zerombr yes will instruct the installer to go ahead and format the DASD without prompting. To your first point, I think Doug was pointing out that you don't have to do this format every time. If you have a DASD that was formatted for Linux use in the past, you can just specify: clearpart --all and Anaconda will happily skip the dasdfmt. This works great for DASD used by Linux in the past. For unknown or new DASD, it's best to use the slow approach (dasdfmt during install), that way you know for sure. -Brad -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Ag
Re: To kick or to clone ... that is the question
Even if you "preformat" the DASD, it still has to be done, so it does take time. And if you're using minidisks, you have to format it at the point where the guest is created. On a related note, anyone know how to eliminate the prompt during kickstart?: Can't have a question in command line mode! Warning The partition table on device dasdb (0.0.0101) was unreadable. To create new par titions it must be initialized, causing the loss of ALL DATA on this drive. This operation will override any previous installation choices about which drive s to ignore. Would you like to initialize this drive, erasing ALL DATA? yesno [] I tried to format over a partially formatted minidisk, and got this. There doesn't seem to be an option to override and just go ahead and write. This is RHEL5.3. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of William D Carroll Sent: Wednesday, June 10, 2009 12:57 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question As I have said though kickstart is faster if you do not need to format. In our case we preformat dasd when we get it so this is not needed. a point that seems to keep getting over looked. and point out your test becomes 5 min for kickstart and 16 min for clone if dasd is performated. William 'Doug' Carroll Mainframe Systems Eng Sr I Global Technology Infrastructure -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Hall, Ken (GTS) Sent: Wednesday, June 10, 2009 12:51 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: To kick or to clone ... that is the question Okay, I gave up and ran timings. Our base system consists of 7 minidisks, for a total of 22,744 cylinders. About half of that (three volumes) is empty space in an LV for a product that generates data after the system is up. The actual base system is three minidisks, plus one swap disk, that roughly fits on a 3390-9. It all has to be either formatted or copied. Kickstart took 21 minutes to format all that, plus an additional 5 minutes (surprisingly) to install 491 packages, for a total of 26 minutes. The process failed in the end because of a bug in my post-install script, but the system was manually bootable. Our clone process took 16 minutes to sequentially copy the same 7 disks via DDR. If you're clever, you can set up parallel service machines to perform the copies at once and get it down to maybe 5 minutes total (assuming your system isn't all on one disk). We had done this in a previous incarnation of the Linux project, but our current method is sequential. As I said, the difference is significant in itself, but we're talking minutes. Different combinations of disks with different numbers of packages, and amounts of empty space will affect the results, so Your Mileage May DEFINITELY Vary. My main gripe with kickstart is that it's complicated, buggy (on z), and badly documented (on z). I spent a lot of time fooling with it during our original setup (gave up), once again later (when I was finally able to get it to work), and because we may have to switch to using it, I'm still trying to get it working properly in my "spare" time. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of William D Carroll Sent: Wednesday, June 10, 2009 11:04 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question I cannot agree with your statement "Any way you cut it, there's still more overhead in kickstart, and it still takes longer" as I've stated unless you're using flashcopy (not available to everyone) a DDR can take longer than a Kickstart, Real experience here with kickstarting being faster than DDR's kickstarting can be real simple as well. php to create the kickstart pull IP and info from a DB/flatfile. server kickstarted and up in <5min (if no dasdfmt needed) I'm curious, how many have actually tried kickstarting servers and really dived into it? not just a sample kickstart and then didn't' like it. really looked at it? William 'Doug' Carroll Mainframe Systems Eng Sr I Global Technology Infrastructure RedHat Certified Engineer: 805008304430937 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Hall, Ken (GTS) Sent: Wednesday, June 10, 2009 10:31 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: To kick or to clone ... that is the question Well, actually, all our guests use hipersockets, for reasons I won't get into, but we also use vswitch, and ping times going between two guests on a vswitch are comparable to guests on the hipersocket. Any way you cut it, there's still more overhead in kickstart, and it still takes longer. Even cutting out the formatting time, you still have
Re: To kick or to clone ... that is the question
There was a known bug in RHEL5.1 and (I believe) 5.2 where if the target disks already contained a filesystem, anaconda hung before it actually got into doing anything. During my last round of testing, I had to reformat the disks before repeating the kickstart. I just tested with 5.3, and it appears to be working. It's formatting over the old filesystems. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Shawn Wells Sent: Wednesday, June 10, 2009 12:49 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question Hall, Ken (GTS) wrote: > Which distro/version? Apparently this was a known problem with RHEL5, but > might have been fixed by now. > I haven't heard of this one. I'd love to hear about any details if you have them still. Actually, I lie. I've heard of customers taking a non-Linux formatted DASD to install Linux on and having issues. You can use the 'zerombr' to clear out pre-existing partition information. Especially useful on new disks, since the partition table on them is bogus (if one is present) -- Shawn Wells Global System z Platform Manager Cell: (+1) 443-534-0130 (GMT -5) -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. --
Re: To kick or to clone ... that is the question
Okay, I gave up and ran timings. Our base system consists of 7 minidisks, for a total of 22,744 cylinders. About half of that (three volumes) is empty space in an LV for a product that generates data after the system is up. The actual base system is three minidisks, plus one swap disk, that roughly fits on a 3390-9. It all has to be either formatted or copied. Kickstart took 21 minutes to format all that, plus an additional 5 minutes (surprisingly) to install 491 packages, for a total of 26 minutes. The process failed in the end because of a bug in my post-install script, but the system was manually bootable. Our clone process took 16 minutes to sequentially copy the same 7 disks via DDR. If you're clever, you can set up parallel service machines to perform the copies at once and get it down to maybe 5 minutes total (assuming your system isn't all on one disk). We had done this in a previous incarnation of the Linux project, but our current method is sequential. As I said, the difference is significant in itself, but we're talking minutes. Different combinations of disks with different numbers of packages, and amounts of empty space will affect the results, so Your Mileage May DEFINITELY Vary. My main gripe with kickstart is that it's complicated, buggy (on z), and badly documented (on z). I spent a lot of time fooling with it during our original setup (gave up), once again later (when I was finally able to get it to work), and because we may have to switch to using it, I'm still trying to get it working properly in my "spare" time. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of William D Carroll Sent: Wednesday, June 10, 2009 11:04 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question I cannot agree with your statement "Any way you cut it, there's still more overhead in kickstart, and it still takes longer" as I've stated unless you're using flashcopy (not available to everyone) a DDR can take longer than a Kickstart, Real experience here with kickstarting being faster than DDR's kickstarting can be real simple as well. php to create the kickstart pull IP and info from a DB/flatfile. server kickstarted and up in <5min (if no dasdfmt needed) I'm curious, how many have actually tried kickstarting servers and really dived into it? not just a sample kickstart and then didn't' like it. really looked at it? William 'Doug' Carroll Mainframe Systems Eng Sr I Global Technology Infrastructure RedHat Certified Engineer: 805008304430937 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Hall, Ken (GTS) Sent: Wednesday, June 10, 2009 10:31 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: To kick or to clone ... that is the question Well, actually, all our guests use hipersockets, for reasons I won't get into, but we also use vswitch, and ping times going between two guests on a vswitch are comparable to guests on the hipersocket. Any way you cut it, there's still more overhead in kickstart, and it still takes longer. Even cutting out the formatting time, you still have to read the packages, send them over the network, and install them, but in the end you're talking minutes. There are other advantages to kickstart, I just wish it worked better and was better documented for zSeries. I had a terrible time figuring out how to get it working the first time, and a few of the parameters don't seem to work as advertised (or at least didn't with RHEL5.2). If you could put the kickstart file on the 191 disk, IPL the kernel, have it install headless, and reboot properly afterward, it would be worthwhile, but I could never get it to do that, and the kickstart file has to be on a server somewhere. At the moment, we control everything from VM, and creating instances is as simple as it can get. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Pace Sent: Wednesday, June 10, 2009 10:12 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question Unless your installation source is on a Hipersocket connection, then the network time is near zilch. On Wed, Jun 10, 2009 at 10:02 AM, Hall, Ken (GTS) wrote: > The small addition of the read time for DDR is nothing compared to the > time required to install the packages over the network. That's at least > the same amount of reading, plus network time. > > I agree about the problem of keeping multiple masters. We keep just one > per version, and use a first-boot process to install additional packages > via yum as needed, or let the admins install what they need manually. > > It's still faster, by quite a lot. Unfortunately, I don't have time > today to run m
Re: To kick or to clone ... that is the question
I doubt there would be much improvement. See my previous email, the actual package install was much faster than I expected. It's the setup and format that take the time. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Brad Hinson Sent: Wednesday, June 10, 2009 12:49 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question David Boyes wrote: >> Are you using NFS to host the install tree? In some recent tests, I >> noticed a huge improvement installing over NFS when tweaking the NFS >> mount options (rsize, wsize, tcp instead of udp, timeout). > > This is also one of the few cases where memory-mapping the install repository filesystem in XSTORE on the kickstart server is worth considering. Speeds up the process enormously at the cost of paging space and operations. > Hmm, interesting.. do you mean creating a DCSS for the install tree? That would be blazing fast. > -- > 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 -- Brad Hinson Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 www.redhat.com/z -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: To kick or to clone ... that is the question
In fairness, there's a script mechanism in kickstart that allows you to make whatever post-install customizations are needed. I spent a lot of time trying to duplicate our clone process using kickstart, and in the end I got VERY close. I'm still not convinced it's faster unless your base system is VERY small package-wise, and your target system has a lot of empty space. I'm setting up to do timings, just to get an idea, and also to see if any of the bugs I'd seen before have been fixed. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Marcy Cortes Sent: Wednesday, June 10, 2009 11:10 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question One other thing to consider is that cloning allows you to bring up an already patched server [some of us can't bring up unpatched servers on the prod network]. You can also have all of your customization done and other layered products and packages installed. For those reasons we clone. Marcy -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. --
Re: To kick or to clone ... that is the question
Well, actually, all our guests use hipersockets, for reasons I won't get into, but we also use vswitch, and ping times going between two guests on a vswitch are comparable to guests on the hipersocket. Any way you cut it, there's still more overhead in kickstart, and it still takes longer. Even cutting out the formatting time, you still have to read the packages, send them over the network, and install them, but in the end you're talking minutes. There are other advantages to kickstart, I just wish it worked better and was better documented for zSeries. I had a terrible time figuring out how to get it working the first time, and a few of the parameters don't seem to work as advertised (or at least didn't with RHEL5.2). If you could put the kickstart file on the 191 disk, IPL the kernel, have it install headless, and reboot properly afterward, it would be worthwhile, but I could never get it to do that, and the kickstart file has to be on a server somewhere. At the moment, we control everything from VM, and creating instances is as simple as it can get. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Pace Sent: Wednesday, June 10, 2009 10:12 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question Unless your installation source is on a Hipersocket connection, then the network time is near zilch. On Wed, Jun 10, 2009 at 10:02 AM, Hall, Ken (GTS) wrote: > The small addition of the read time for DDR is nothing compared to the > time required to install the packages over the network. That's at least > the same amount of reading, plus network time. > > I agree about the problem of keeping multiple masters. We keep just one > per version, and use a first-boot process to install additional packages > via yum as needed, or let the admins install what they need manually. > > It's still faster, by quite a lot. Unfortunately, I don't have time > today to run measurements, but our base system clone process takes less > than 30 minutes from beginning to end. > > All this said, we have been seriously considering going to a kickstart > based method, but my experience with it has not been encouraging. Aside > from taking longer, it seems to be fairly fragile and requires more > manual effort. Our clone method consists of running a VM-based dialog, > waiting for the copies to finish (run asynchronously in a service > machine), and then autologging the new guest. > > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > Rob van der Heij > Sent: Wednesday, June 10, 2009 9:16 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] To kick or to clone ... that is the question > > On Wed, Jun 10, 2009 at 2:54 PM, Hall, Ken (GTS) wrote: > > > How could it be faster? > > > > Cloning involves simply copying the disks, that's one pass with DDR. > > Copying a disk requires reading and writing. Formatting just requires > (short) writes. Depending on your configuration, you may not notice > the extra resource usage in the elapsed time. > > But it's probably more whether you spend the time while you're waiting > for it. Once you get into the business of holding several different > golden masters to copy from, things get more complicated. > > Back then we used a very bare minimum that was copied to the new root > disk, and the required additional packages were added on top of it. > That approach allows for a stock supply of copied root disks ready to > use. > > -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 > > -- > This message w/attachments (message) may be privileged, confidential or > proprietary, and if you are not an intended recipient, please notify the > sender, do not use or share it and delete it. Unless specifically indicated, > this message is not an offer to sell or a solicitation of any investment > products or other financial product or service, an official confirmation of > any transaction, or an official statement of Merrill Lynch. Subject to > applicable law, Merrill Lynch may monitor, review and retain > e-communications (EC) traveling through its networks/systems. The laws of > the country of each sender/recipient may impact the handling of EC, and EC > may be archived, supervised and produced in countries other than the country > in which you are located. This message cannot be guaranteed to be
Re: To kick or to clone ... that is the question
The small addition of the read time for DDR is nothing compared to the time required to install the packages over the network. That's at least the same amount of reading, plus network time. I agree about the problem of keeping multiple masters. We keep just one per version, and use a first-boot process to install additional packages via yum as needed, or let the admins install what they need manually. It's still faster, by quite a lot. Unfortunately, I don't have time today to run measurements, but our base system clone process takes less than 30 minutes from beginning to end. All this said, we have been seriously considering going to a kickstart based method, but my experience with it has not been encouraging. Aside from taking longer, it seems to be fairly fragile and requires more manual effort. Our clone method consists of running a VM-based dialog, waiting for the copies to finish (run asynchronously in a service machine), and then autologging the new guest. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Rob van der Heij Sent: Wednesday, June 10, 2009 9:16 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question On Wed, Jun 10, 2009 at 2:54 PM, Hall, Ken (GTS) wrote: > How could it be faster? > > Cloning involves simply copying the disks, that's one pass with DDR. Copying a disk requires reading and writing. Formatting just requires (short) writes. Depending on your configuration, you may not notice the extra resource usage in the elapsed time. But it's probably more whether you spend the time while you're waiting for it. Once you get into the business of holding several different golden masters to copy from, things get more complicated. Back then we used a very bare minimum that was copied to the new root disk, and the required additional packages were added on top of it. That approach allows for a stock supply of copied root disks ready to use. -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 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: To kick or to clone ... that is the question
Which distro/version? Apparently this was a known problem with RHEL5, but might have been fixed by now. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Scott Rohling Sent: Wednesday, June 10, 2009 9:09 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question I haven't experienced that myself -- in fact, we would kickstart a server over and over again doing testing, and it always had an existing Linux system on it when we did the kickstartI guess YMMV. Scott On Wed, Jun 10, 2009 at 6:59 AM, Hall, Ken (GTS) wrote: > And you're almost stuck with letting kickstart format the disks. There are > conditions that will cause kickstart to hang if the disks have anything that > looks Linux-like on them, so the safest thing is to CP format them first. > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > Scott Rohling > Sent: Wednesday, June 10, 2009 8:56 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] To kick or to clone ... that is the question > > Hi Doug -- Yep, we sure had some fun kicking Linux servers! > > Not sure how Linux not doing restarting itself is an IBM issue... but that > 'is' a nasty downside to kickstarting -- ending up at a 'You may safely > reboot' screen doesn't help automation. > > And we should add that kickstarting is faster than cloning 'if' the DASD is > already Linux formatted.. if not, the kickstart does the formatting, adding > time to the install. > > Scot > > On Tue, Jun 9, 2009 at 11:39 PM, WILLIAM CARROLL > wrote: > > > Hi Scott, > > > > I'll jump on your bandwagon but then again you already know I perfer > > Kickstarting over cloning > > you should also mention that unless you have Flashcopy for your DASD > > Kickstarting is actually faster than cloning. > > unless your clone master is very small. > > > > as you recall ours was on a mod3 (lots of required garbage) and cloning > > that mod3 was slower than kickstarting > > also after the kickstart was done the server was ready, no additional > > steps > > to change IP's or anything. > > > > if only redhat would fix that re-ipl after the reboot. > > they say it's an IBM issue not thiers > > > > Doug Carroll > > > > > > > > - Original Message - > > From: "Scott Rohling" > > To: > > Sent: Wednesday, June 10, 2009 12:00 AM > > Subject: To kick or to clone ... that is the question > > > > > > This is a blatant request for discussion about the pros and cons of > using > >> an > >> automated installation (e.g. RH kickstart - Suse autoyast (though maybe > >> this > >> has changed - I'm not current on Suse) - vs cloning a system from a > >> 'golden > >> image'... and I should say: on zSeries. > >> > >> I'm a fan of kickstart - and I'll list my reasons in approximate order > of > >> importantance to me (most to least): > >> > >> - kickstart forces a scripted and recreatable installation. You > specify > >> the rpm's and can do some limited scripting within the kickstart file > >> itself > >> to end up with (hopefully) a working Linux system that requires no > manual > >> tweaking (at least - if you do it 'right'). The alternative is a cloned > >> system that the Linux SA's have been on, and perhaps several other teams > - > >> all performing manual tasks to end up with the final product - all sorts > >> of > >> shoeprints and no good detectives. Whereas a kickstart config is > >> self-documenting - a clone is not. With good scripting and good use of > >> rpm > >> packaging for your 'local' or even 'vendor' products - you can end up > with > >> a > >> very KISS config file that might even go multiplatform. (e.g. > arch=`uname > >> -m` ) > >> > >> - with a proper building of conf and parm files on z/VM - a guest can be > >> kicked already configured with a working network -- no need for some > >> outside > >> scripting or manual config. > >> > >> - you can have different kickstart files for different server 'types' > >> (web, > >> app, db, etc) - these can even be built dynamically and requested via a > >> URL > >> to to the kickstart ( e.g. > >> http://mykicker/kick.web&ip=xx.xx.xx.xx+etc+etc.) > >&g
Re: To kick or to clone ... that is the question
And you're almost stuck with letting kickstart format the disks. There are conditions that will cause kickstart to hang if the disks have anything that looks Linux-like on them, so the safest thing is to CP format them first. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Scott Rohling Sent: Wednesday, June 10, 2009 8:56 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question Hi Doug -- Yep, we sure had some fun kicking Linux servers! Not sure how Linux not doing restarting itself is an IBM issue... but that 'is' a nasty downside to kickstarting -- ending up at a 'You may safely reboot' screen doesn't help automation. And we should add that kickstarting is faster than cloning 'if' the DASD is already Linux formatted.. if not, the kickstart does the formatting, adding time to the install. Scot On Tue, Jun 9, 2009 at 11:39 PM, WILLIAM CARROLL wrote: > Hi Scott, > > I'll jump on your bandwagon but then again you already know I perfer > Kickstarting over cloning > you should also mention that unless you have Flashcopy for your DASD > Kickstarting is actually faster than cloning. > unless your clone master is very small. > > as you recall ours was on a mod3 (lots of required garbage) and cloning > that mod3 was slower than kickstarting > also after the kickstart was done the server was ready, no additional > steps > to change IP's or anything. > > if only redhat would fix that re-ipl after the reboot. > they say it's an IBM issue not thiers > > Doug Carroll > > > > - Original Message - > From: "Scott Rohling" > To: > Sent: Wednesday, June 10, 2009 12:00 AM > Subject: To kick or to clone ... that is the question > > > This is a blatant request for discussion about the pros and cons of using >> an >> automated installation (e.g. RH kickstart - Suse autoyast (though maybe >> this >> has changed - I'm not current on Suse) - vs cloning a system from a >> 'golden >> image'... and I should say: on zSeries. >> >> I'm a fan of kickstart - and I'll list my reasons in approximate order of >> importantance to me (most to least): >> >> - kickstart forces a scripted and recreatable installation. You specify >> the rpm's and can do some limited scripting within the kickstart file >> itself >> to end up with (hopefully) a working Linux system that requires no manual >> tweaking (at least - if you do it 'right'). The alternative is a cloned >> system that the Linux SA's have been on, and perhaps several other teams - >> all performing manual tasks to end up with the final product - all sorts >> of >> shoeprints and no good detectives. Whereas a kickstart config is >> self-documenting - a clone is not. With good scripting and good use of >> rpm >> packaging for your 'local' or even 'vendor' products - you can end up with >> a >> very KISS config file that might even go multiplatform. (e.g. arch=`uname >> -m` ) >> >> - with a proper building of conf and parm files on z/VM - a guest can be >> kicked already configured with a working network -- no need for some >> outside >> scripting or manual config. >> >> - you can have different kickstart files for different server 'types' >> (web, >> app, db, etc) - these can even be built dynamically and requested via a >> URL >> to to the kickstart ( e.g. >> http://mykicker/kick.web&ip=xx.xx.xx.xx+etc+etc.) >> >> - The size of the DASD can be flexible.. cloning requires copying the >> same >> size DASD as the source.. >> >> - The latest fixes can be applied by keeping the repository the kickstart >> uses current - rather than updating a clone source. (of course - testing >> is >> still required and would require kickstarting a guest to truly do any >> testing - a good thing imo) >> >> - It encourages packing by rpm rather than manual 'tarball' methods.. >> this >> is in line with a 'recreatable' install. Yes, you can still do 'tar' >> commands in the kickstart file itself.. but specifying an rpm package is >> oh >> so much easier. >> >> - Servers start 'clean' - ie no old log files from the clone source and >> no >> need to try and script a 'cleanup' >> >> - No worrying about whether a clone source is 'up' when a new server is >> clone and possibly clone a live system >> >> >> There are downsides.. but I'll leave those to the rest of you to expound >> on, since I'm taking a position of 'kickstart good, Jane' >> >> Thanks and hope this is valuable to some .. >> >> Scott >> http://www.marist.edu/htbin/wlvindex?LINUX-390 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official c
Re: To kick or to clone ... that is the question
How could it be faster? Cloning involves simply copying the disks, that's one pass with DDR. Kickstart involves running Linux format on the disks first, then copying all the packages via network. The format alone takes as much time as the DDR copies. I've tried both ways. We started with cloning originally because the kickstart process was pretty troublesome early on, and because the NFS server was out on the network, it took a LONG time. With the repository on the same VM system, now the install part is fast, but cloning is still MUCH faster. We developed scripting mechanisms to handle first-boot customizations, so we get the same effect in much less time. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of WILLIAM CARROLL Sent: Wednesday, June 10, 2009 1:40 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] To kick or to clone ... that is the question Hi Scott, I'll jump on your bandwagon but then again you already know I perfer Kickstarting over cloning you should also mention that unless you have Flashcopy for your DASD Kickstarting is actually faster than cloning. unless your clone master is very small. as you recall ours was on a mod3 (lots of required garbage) and cloning that mod3 was slower than kickstarting also after the kickstart was done the server was ready, no additional steps to change IP's or anything. if only redhat would fix that re-ipl after the reboot. they say it's an IBM issue not thiers Doug Carroll - Original Message - From: "Scott Rohling" To: Sent: Wednesday, June 10, 2009 12:00 AM Subject: To kick or to clone ... that is the question > This is a blatant request for discussion about the pros and cons of using > an > automated installation (e.g. RH kickstart - Suse autoyast (though maybe > this > has changed - I'm not current on Suse) - vs cloning a system from a > 'golden > image'... and I should say: on zSeries. > > I'm a fan of kickstart - and I'll list my reasons in approximate order of > importantance to me (most to least): > > - kickstart forces a scripted and recreatable installation. You specify > the rpm's and can do some limited scripting within the kickstart file > itself > to end up with (hopefully) a working Linux system that requires no manual > tweaking (at least - if you do it 'right'). The alternative is a cloned > system that the Linux SA's have been on, and perhaps several other teams - > all performing manual tasks to end up with the final product - all sorts > of > shoeprints and no good detectives. Whereas a kickstart config is > self-documenting - a clone is not. With good scripting and good use of > rpm > packaging for your 'local' or even 'vendor' products - you can end up with > a > very KISS config file that might even go multiplatform. (e.g. arch=`uname > -m` ) > > - with a proper building of conf and parm files on z/VM - a guest can be > kicked already configured with a working network -- no need for some > outside > scripting or manual config. > > - you can have different kickstart files for different server 'types' > (web, > app, db, etc) - these can even be built dynamically and requested via a > URL > to to the kickstart ( e.g. > http://mykicker/kick.web&ip=xx.xx.xx.xx+etc+etc.) > > - The size of the DASD can be flexible.. cloning requires copying the > same > size DASD as the source.. > > - The latest fixes can be applied by keeping the repository the kickstart > uses current - rather than updating a clone source. (of course - testing > is > still required and would require kickstarting a guest to truly do any > testing - a good thing imo) > > - It encourages packing by rpm rather than manual 'tarball' methods.. > this > is in line with a 'recreatable' install. Yes, you can still do 'tar' > commands in the kickstart file itself.. but specifying an rpm package is > oh > so much easier. > > - Servers start 'clean' - ie no old log files from the clone source and > no > need to try and script a 'cleanup' > > - No worrying about whether a clone source is 'up' when a new server is > clone and possibly clone a live system > > > There are downsides.. but I'll leave those to the rest of you to expound > on, since I'm taking a position of 'kickstart good, Jane' > > Thanks and hope this is valuable to some .. > > Scott > > -- > 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 message w/attachmen
Re: How can i share disks with FCP ?
You have to use NPIV, which must be supported by the hardware, zVM, and Linux. SLES10 should be fine, and zVM 5.4 I know works, but your channels must be configured for it, along with the switch fabric and storage subsystem. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Yoon-suk Cho Sent: Tuesday, June 09, 2009 10:10 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] How can i share disks with FCP ? Hi. all. Anyone who know how to share the disks between A and B zlinux? We have two z hardware. 2094(z/VM 5.4 fcp) and 2097(z/VM 5.4 fcp). I made a z/VM and SLES 8,9,10 with FCP in sucessfully on new z/VM and hardware. I want to make two LINUX (SLES10) in each z/VM to shared disks by ocfs2. and I want to share one disk to another zLINUX. that is, another zlinux is cold stand by server. If the first linux server is crash , I have to detach the fcp disk in first linux to attach another server. How can i make shared F/S with FCP? I couldn't find some books or redpaper. thanks in advance. -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Tape drives for zLinux servers
We're using 3592 drives, with 3494 library (TS3500), via FCP attach. There's a document from IBM that lists everything supported: ftp://ftp.software.ibm.com/storage/devdrvr/Doc/IBM_Tape_Driver_IUG.pdf -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Spann, Elizebeth (Betsie) Sent: Wednesday, May 27, 2009 11:08 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Tape drives for zLinux servers Hello VM/zLinux users, We are trying to identify the tape drive models that can be used natively by a zLinux server; i.e. FCP attached. I believe that the list includes TS1120 tape drives, 3592 J1A tape drives. What else, please? Do you use a tape library? Betsie -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Stateless Linux for zSeries
There's a project page on Sourceforge for it, but it hasn't been updated since 2005. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Marcy Cortes Sent: Friday, May 15, 2009 12:25 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Stateless Linux for zSeries Ah! I didn't know that! Thanks for the PoE. It is opensourced, right? 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 Phil Smith III Sent: Thursday, May 14, 2009 9:20 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Stateless Linux for zSeries Marcy Cortes wrote: >We used to use Levanta (now out of business) whose mapfs was based on >unionfs. We didn't see any CPU reduction when we converted off of it. >It did use a lot of CPU at shutdown time, but that may have been more >of a bug than a necessity ;) For PoE* reasons, I'm obliged to point out that MapFS was not based on UnionFS -- it predated its existence and was developed entirely in-house, by Nate Stahl. Not that it matters, or that anyone (quite possibly including Nate) cares any more... ...phsiii * Purity of Essence -- Google it. -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Stateless Linux for zSeries
I would think then that bind mounts would have similar issue. Has anyone looked into this? -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Rob van der Heij Sent: Thursday, May 14, 2009 11:53 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Stateless Linux for zSeries On Thu, May 14, 2009 at 5:01 PM, Hall, Ken (GTS) wrote: > Most of the "stateless" implementations I've seen seem to rely on "bind > mounts", but that seems to be a bit of a hack. "Union" mounting, such > as "Unionfs" look like it would be a cleaner approach, but I can't find > out if there's a workable implementation of that. Any ideas? > > I've pulled the unionfs patch, but I'm reluctant to go to the trouble of > maintaining yet another custom kernel module. Last time I looked at unionfs was probably 3 years ago. It still had some functional issues, but some of those may have been addressed since then. I initially used it for my "Penguins on a Pin Head" project. One of my my concerns back then was the extra CPU time spent in dealing with the unionfs layers. That is not an issue on dedicated hardware because you don't notice a few percent extra CPU when the data must come from disk or NFS mounted devices. 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 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Stateless Linux for zSeries
We're on Red Hat, so same question applies to that distro, if anyone knows. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Edmund R. MacKenty Sent: Thursday, May 14, 2009 11:18 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Stateless Linux for zSeries On Thursday 14 May 2009 11:01, Hall, Ken (GTS) wrote: >Most of the "stateless" implementations I've seen seem to rely on "bind >mounts", but that seems to be a bit of a hack. "Union" mounting, such >as "Unionfs" look like it would be a cleaner approach, but I can't find >out if there's a workable implementation of that. Any ideas? > >I've pulled the unionfs patch, but I'm reluctant to go to the trouble of >maintaining yet another custom kernel module. That's the same reason I'm not using unionfs, although I'd very much like to. It would make a lot of the stuff I do with shared DASD *much* easier. Mark, do you know if Novell plans to make unionfs (or anything like it) available in SLES anytime soon? Can we nudge them in that direction? - MacK. - Edmund R. MacKenty Software Architect Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.4321 Email: m...@rs.com Web: www.rocketsoftware.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 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Stateless Linux for zSeries
I'm working with Alan on this too, and a lot of the issues revolve around the definition of "stateless" and what's expected from it. If it's the ability to move apps between servers transparently, we already have that. Just shut down the instance, and IPL on another VM image. If it's the ability to move apps between servers without an outage, ala VMWare ESX, we don't have that (yet). If it's to save disk space by sharing the base filesystems, we're still debating that. It's up in the air whether the saving would be enough to justify heavily customizing our build and taking on the maintenance issues. "Stateless" also seems to make the most sense if you're rolling out large numbers of identical commodity servers, but we're not doing that, almost all of our servers have packages added above the base build that would affect that "shared" filesystem. Most of the "stateless" implementations I've seen seem to rely on "bind mounts", but that seems to be a bit of a hack. "Union" mounting, such as "Unionfs" look like it would be a cleaner approach, but I can't find out if there's a workable implementation of that. Any ideas? I've pulled the unionfs patch, but I'm reluctant to go to the trouble of maintaining yet another custom kernel module. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Edmund R. MacKenty Sent: Thursday, May 14, 2009 10:38 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Stateless Linux for zSeries On Wednesday 13 May 2009 20:10, David Boyes wrote: >On 5/13/09 3:16 PM, "Alan Ackerman" >wrote: >> Someone here says we should not do Linux on zSeries because you cannot do >> "stateless computing" on zSeries. > >In a word: bunk. > >> Has anyone had any experience with building a stateless Linux on zSeries? > >The Novell starter system is a good example. Any of our Debian deployment >tools are examples. The stuff we're doing with OpenSolaris diskless virtual >machines is an example. > >Can't do it -- pah. We (the mainframe) *invented* it. Exactly. I've read up on this buzz-phrase a bit now (great links folks! thanks!) and I can't see how "stateless computing" is much different from a z/VM guest running Linux applications and mounting its data filesystems via NFS from some network storage appliance. If there's a problem with the guest, you just configure another one and replace it. Lots of people on this list have been doing that for years, as have I. There're products around that will help you implement this (contact me off-list). So Alan, tell that "someone" that they're very wrong. - MacK. - Edmund R. MacKenty Software Architect Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.4321 Email: m...@rs.com Web: www.rocketsoftware.com -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Excessive time for login
Is this a product (such as Vintela), or a home-grown solution? If the authentication succeeds, but the shell prompt doesn't complete for a while after, I'd be inclined to blame either the LDAP query that pulls the UID/GID/DIR/SHELL info from AD, or a page-swap-in delay. If your users are defined locally, and you're just using pam_krb5 to authenticate, check your pam stack and see if you can eliminate the culprit by temporarily taking out modules from the "account" and "session" stacks. Some of the modules also have debug parms and log entries that might help. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Friday, March 20, 2009 1:39 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Excessive time for login >>> On 3/20/2009 at 1:28 PM, "Shedlock, George" wrote: > We are running SUSE SLES 10 SP 2. When we login to the server via SSH, our > pam module that validates the userid against Active Directory completes with > a successful logon (as seen on the syslog), but it is some 40-50 seconds > before we see the logon prompt to the user. I've seen this happen when your DNS isn't set up right, or the system cannot reach the DNS server for some reason. 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 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: starting 'at the begining' to install linux on z/os
That assumes you have access to the HMC in the first place. I don't know what his environment is like, but I'm 1000 miles away from the data center, and in any case, they don't allow anyone NEAR the HMC during business hours. Setting up VM initially might take a little longer (like one day if you know what you're doing), but the benefits come back quickly. The one thing I did forget to mention before is that if you're going to set up an LPAR, it helps to carve out a subset of DASD defined only to that LPAR, and try to standardize the addresses. When you're dealing with real addresses, you can't move them around as easily as you can with virtual minidisks, and Linux will scan ALL available DASD devices on IPL. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of David Andrews Sent: Friday, March 13, 2009 12:01 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] starting 'at the begining' to install linux on z/os On Fri, 2009-03-13 at 11:23 -0400, Hall, Ken (GTS) wrote: > The installation on bare metal is tricky (as those of us who have > installed under Hercules have found) and requires access to the HMC for > possibly many sessions to get things right so it will come up and > install. Installing Debian from the HMC cupholder was pretty easy; I got it done in an afternoon. What's more time-consuming is getting the LPAR defined, with the DASD device addresses properly isolated from your production system(s). Took me several iterations with HCD to get it right, and much longer than it took to install Debian itself. (HCD and I don't get along all that well.) There might be some downtime associated with creating a new LPAR, depending on your dynamic-reconfiguration-fu and whether you've got spare memory to carve out. I'm not VM-literate, so it took me less time to build the LPAR than it would have taken me to install and learn VM. (Not to mention that I'd have had to convince someone to pay for it.) DB has a litany of reasons for using z/VM in your Linux farm, and you should generally listen to anything he says... but for my modest purposes a single little LPAR works just fine. -- David Andrews A. Duda and Sons, Inc. david.andr...@duda.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 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: starting 'at the begining' to install linux on z/os
First of all, you don't install Linux on zOS, you install it on either the zSeries processor, or under zVM. About the only part you might need zOS for is to create an IPL tape if you want to install in an LPAR. This isn't recommended though, and I think a lot of folks on this list will echo that, particularly Mr. Boyes, who has a lot of experience with this. The installation on bare metal is tricky (as those of us who have installed under Hercules have found) and requires access to the HMC for possibly many sessions to get things right so it will come up and install. zVM gives you a much more manageable environment to work under, and if you talk to IBM, they're usually more than willing to help with getting it going. The learning curve for getting zVM installed has some bumps, but following the one-page instructions, you can have a basic system up in a couple of hours. Another option, if you're determined to go the LPAR route would be to try it out on your desktop under Hercules (the zSeries emulator), and once you have the process down, go back to the real thing. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Gear, Steven Sent: Friday, March 13, 2009 11:06 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] starting 'at the begining' to install linux on z/os Hello, I am at the beginning of installing Linux on z/os. I thinking just in an Lpar or two for now, z/vm later. This is an R&D project just to get it up and running. I have a Z9 and a copy of SUSE. Now what? What would be the best redbook or manual? Thanks, steve -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Creating RAID Arrays on zLinux / zVM minidisks
>From s390utils-1.3.2-2.40.16: Disk /dev/dasdc: 5700 cylinders, 15 tracks per cylinder, 12 blocks per track 4096 bytes per block volume label: VOL1, volume identifier: 0X0109 maximum partition number: 3 --- tracks --- Device start end length Id System /dev/dasdc1 285499854981 Linux native change partition type partition id (use 0 to exit): 1 current partition type is: Linux native 1 Linux native 2 Linux swap 3 Linux raid new partition type: -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Dan Horák Sent: Monday, March 09, 2009 3:38 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Creating RAID Arrays on zLinux / zVM minidisks Mark Post píše v Ne 08. 03. 2009 v 20:02 -0600: > >>> On 3/5/2009 at 4:43 PM, "Hall, Ken (GTS)" wrote: > > Option "t" in fdasd can be used to change the partition type to > > "Linux raid". > > Not that I'm aware of. I've only seen Linux native and Linux swap for fdasd, > including the one from s390-tools 1.8.0. We are patching fdasd to support the "Linux Raid" type since RHEL 3 times (2003). -- Dan Horák, RHCE Software Engineer, BaseOS Red Hat Czech s.r.o., Purkyňova 99, 612 45 Brno -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: RHEL YUM Question
The URL for the repository has to point to the directory that contains the "repodata" directory. You create that by using "createrepo", or there's one pre-packaged on the CD. This directory can be either in the directory that contains packages, or above it, since createrepo searches down. You also have to make sure that the web server has permission to read the repodata directory and the files in it. The apache error log should tell you what the actual error was. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of John Summerfield Sent: Thursday, March 05, 2009 7:10 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] RHEL YUM Question Dave Myers wrote: > Given this YUM repos conf file..can anyone see why I am getting the > following error? > > [RHEL5.3] > name=Red Hat Enterprise Linux 5.3 > baseurl=FTP://ftpuser:ftpu...@10.100.105.12/mnt2/Server/ > > > > (error msgs) > > ftp://ftpuser:ftpu...@10.100.105.12/mnt2/Server/repodata/repomd.xml: > [Errno 4] > IOError: [Errno ftp error] 550 Failed to change directory. This means the directory doesn't exist (or maybe permissions don't allow access). I think Andrew's given the right answer. > Trying other mirror. > Error: Cannot retrieve repository metadata (repomd.xml) for repository: > RHEL5.3. Please verify its path and try again > > -- > 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 > -- Cheers John -- spambait 1...@coco.merseine.nu z1...@coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. --
Re: Creating RAID Arrays on zLinux / zVM minidisks
Yes. It works pretty much the same way as it does on Intel. You use the mdadm package to create raid arrays, but it's done at the partition level. Option "t" in fdasd can be used to change the partition type to "Linux raid". Typically, minidisk devices only have a single partition because it doesn't make much sense to have more (just have more minidisks), but in practice you can have up to three. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of CHAPLIN, JAMES (CTR) Sent: Thursday, March 05, 2009 4:16 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Creating RAID Arrays on zLinux / zVM minidisks Okay, this is not real work, been working on my RHCT, and decided to test what I can do on a PC to the zLinux platform. I am trying to create a RAID-1 Array (two disks mirroring each other) in a zVM environment. I created two minidisks in zVM and am trying to format them on the zLinux side, using fdasd (instead of fdisk on the PC side). But I see no option to format "fd" the disks, with the interactive, it keeps asking for partition number (here is the display): (/root)#fdasd /dev/dasdk reading volume label ..: VOL1 reading vtoc ..: ok Command action m print this menu p print the partition table n add a new partition d delete a partition v change volume serial t change partition type r re-create VTOC and delete all partitions u re-create VTOC re-using existing partition sizes s show mapping (partition number - data set name) q quit without saving changes w write table to disk and exit Command (m for help): t Disk /dev/dasdk: cylinders : 750 tracks per cylinder ..: 15 blocks per track .: 12 bytes per block ..: 4096 volume label .: VOL1 volume serial : 0X0205 max partitions ...: 3 --- tracks --- Device start end length Id System 21124911248 unused change partition type partition id (use 0 to exit): Has anyone played with "software" RAID on the mainframe Linux? James Chaplin Systems Programmer, MVS, zVM & zLinux Base Technologies, Inc -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Why does one need to mkinitrd/zipl ? (WAS : Broken logical volume group)
I haven't found any other way to define them in Red Hat. If they're not in the parm list in the initrd, they're not seen (although I actually haven't tested this in a long time, and I should probably revisit it). If they're attached after the fact, though, they do appear to come online automatically. FCP disks are a whole other thing. There were some early race-condition bugs in udev that might have caused out-of-sequence startup, but with the list in the parm, we've never seen that. We know about the problem because we have FCP-attached tape drives on an old level of RHEL4, and it's an ongoing problem. Like I said, we just put placeholders in the parm list, and reserve the slots, plus we use mount-by-label, and LVM extensively. I haven't looked at Suse in some time, but I understand the mechanism is somewhat different. YMMV. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Richard Troth Sent: Monday, February 23, 2009 9:23 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Why does one need to mkinitrd/zipl ? (WAS : Broken logical volume group) Ken -- In the thread, we may have not specifically mentioned that list of devices. Nice catch. But ... be aware that the list-o-devices may not always be needed. In particular, once the root is mounted, especially if UDEV is then also available, additional disks can be marked online via magical stuff under /etc/sysconfig. (I speak from SLES experience having been away from RH for a while, though I know RH generally does also utilize /etc/sysconfig.) I find it immensely useful to have the devices listed in an after-the-initrd kind of file. The value of NOT having to re-stamp INITRD for some 500 penguins is ... well ... it's huge. Also, just FYI, somewhere in the history of 2.6, the dasda-dasdp slots became less consistent. What I mean is that even if I code 100-10F, the latter disks are NOT slotted where I expect them if they do not exist when the driver is loaded. Bad bad ... but water under the bridge now. [sigh] UDEV helps. (But this is a whole nutha subject and thread.) -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Help with zLinux DASD using multiple paths
It's a characteristic of the architecture that all eight paths will be used under the covers, PROVIDING you can drive eight I/O operations at the same time to different volumes (or cache, for some subsystems, when reading). Normally you can't do this from a single guest. What you ARE getting is alternative to contention from OTHER guests going against the same storage subsystem. But if the database is on a single device, no matter how many paths you use, it will still only be one I/O at a time. Even with PAV and multipath, you won't get much help. On FCP, for example, we were advised not to use multibus mode (which load balances) due to overhead. The same issues probably apply to using PAV's with DASD (never mind the configuration issues). What you CAN do is use LVM to create a striped filesystem spread over eight smaller volumes (minidisks). We've run tests on this configuration and the performance was so much better, it's become our standard configuration for large data filesystems. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of David K. Kelly Sent: Monday, February 23, 2009 3:41 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Help with zLinux DASD using multiple paths Thank you David and Ron for the quick responses. Let me explain what I'm trying to do. In zLinux I have a DB2 file system that is setup on one large 3390-27 disk pack. And when I use Linux tools like iostat I see one disk with one path to the Shark. What I would like to do is use the eight paths to this single disk (yes, I would like multiple exposures to the disks). How do I do that? Or maybe I already have this configured or CP is doing it but I can not tell this with my limited Linux commands? We do have Velocity and I can see lots of IO going through. Also we don't used PAV and from what I understand that is more of a zOS thing and we are a zVM shop. Thank you David K. David Boyes To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc Subject Re: Help with zLinux DASD using multiple paths 02/23/2009 11:19 AM Please respond to Linux on 390 Port On 2/23/09 11:12 AM, "David K. Kelly" wrote: > How can I configure multiple paths to a single disk in SUSE zLinux? I have > 8 paths to our Shark and I¹m running zLinux SUSE 10 in zVM V5.3 on > a z9 and I want to configure multiple paths to a single > 22.8 GB 3390-27 disk. Just to be sure, do you want the Linux guest to see multiple exposures to the disk? If so, you need the PAV microcode to do that. If you just want it to exploit the physical paths, give the disk to CP as a user volume, allocate the disk as a minidisk in the Linux directory entry, and let CP worry about it. If the paths are in your IOCP, CP will automagically use them. -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/syste
Re: Why does one need to mkinitrd/zipl ? (WAS : Broken logical volume group)
LVM gives you the option of swapping around the device numbers transparently too. It will alway be able to build the volumes, even if the nodes change. Red Hat also, by convention, sets up everything to mount by label, giving the same flexibility to non-LVM devices. The only one that NEEDS to be on a particular address is the one you boot from. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Scott Rohling Sent: Monday, February 23, 2009 9:31 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Why does one need to mkinitrd/zipl ? (WAS : Broken logical volume group) Good point.. I've always advised giving ranges in modprobe.conf and allowing for growth so you don't have to worry about initrd in most cases. Also - use the ranges as an indicator of what's there.. example: 100 -- /boot 101-110 -- swap 120-130 -- OS disks ( / ) - LVMs for the base OS 200-21F-- Application code LVMs, config, etc (often mounted /opt) 300-31F-- Data (database LVMs, whatever) Things often don't break down in such clean lines - but you get the idea. One advantage is that if you are dealing with LVMs -- and need to do some recovery -- you know by the ranges which disks you'll need to get to make sure you have all the disks for the Linux system LVMs you're trying to fix. I'm sure there are similar schemes buried in the archives, too ;-) Scott On Mon, Feb 23, 2009 at 7:11 AM, Hall, Ken (GTS) wrote: > If this was covered in previous notes, sorry, but I didn't see it, and > I've been out for a few days so I didn't get into this at the beginning. > > In Red Hat (and probably Suse too), there's a chicken-egg problem. The > DASD driver gets its list of valid devices from a parm that's passed to > the driver in /etc/modprobe.conf. But at the time the module is loaded, > the running root filesystem is the initrd. The regular root filesystem > can't be mounted till AFTER the dasd driver is loaded. You only need to > make the initrd if you change the list of devices. > > We coded a list of placeholder device numbers in our base configuration > going out to dasdzz, so we don't have to fiddle going forward. Note > that this list is ONLY devices that are visible automatically at boot > time, and reserves the device node assignments for them. Additional > devices outside the range can be added later via attach and chccwdev, > and device nodes will be built starting after the list built from the > parameter. (i.e., if modprobe.conf contains 100-10F, that reserves > dasda-dasdp, even if some of them don't exist, and the first dynamically > added disk will be dasdq.) > > As far as bare metal goes, we did try some tests in a bare LPAR, and it > works fine with thousands of devices visible, but it takes a LONG time > to scan them all. Also, at the time we tested, there was some quirk > with coding the actual devices in modprobe.conf, and filtering that way > caused the system to hang coming up. It might have been an error in > configuration somewhere, we were on a schedule, so we simply removed the > filter, and brought it up seeing all devices. > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > Ivan Warren > Sent: Thursday, February 19, 2009 9:37 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Why does one need to mkinitrd/zipl ? (WAS : > Broken logical volume group) > > Richard Troth wrote: > > Ivan ... hear this: > > With SLES10, unless you are changing something about the root FS, you > > do not need to re-stamp your INITRD. It is exactly as you say it > > should be. > > > > > > -- R; <>< > > > > > That's good enough for me ;) > > At least the idea that I would have gave me fodder for a tantrum :P > > --Ivan > > -- > 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 message w/attachments (message) may be privileged, confidential or > proprietary, and if you are not an intended recipient, please notify the > sender, do not use or share it and delete it. Unless specifically indicated, > this message is not an offer to sell or a solicitation of any investment > products or other financial product or service, an official confirmation of > any transaction, or an official statement of Merrill Lynch. Subject to > applicable law, Merrill Lynch may monitor, review and retain > e-c
Re: Why does one need to mkinitrd/zipl ? (WAS : Broken logical volume group)
If this was covered in previous notes, sorry, but I didn't see it, and I've been out for a few days so I didn't get into this at the beginning. In Red Hat (and probably Suse too), there's a chicken-egg problem. The DASD driver gets its list of valid devices from a parm that's passed to the driver in /etc/modprobe.conf. But at the time the module is loaded, the running root filesystem is the initrd. The regular root filesystem can't be mounted till AFTER the dasd driver is loaded. You only need to make the initrd if you change the list of devices. We coded a list of placeholder device numbers in our base configuration going out to dasdzz, so we don't have to fiddle going forward. Note that this list is ONLY devices that are visible automatically at boot time, and reserves the device node assignments for them. Additional devices outside the range can be added later via attach and chccwdev, and device nodes will be built starting after the list built from the parameter. (i.e., if modprobe.conf contains 100-10F, that reserves dasda-dasdp, even if some of them don't exist, and the first dynamically added disk will be dasdq.) As far as bare metal goes, we did try some tests in a bare LPAR, and it works fine with thousands of devices visible, but it takes a LONG time to scan them all. Also, at the time we tested, there was some quirk with coding the actual devices in modprobe.conf, and filtering that way caused the system to hang coming up. It might have been an error in configuration somewhere, we were on a schedule, so we simply removed the filter, and brought it up seeing all devices. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Ivan Warren Sent: Thursday, February 19, 2009 9:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Why does one need to mkinitrd/zipl ? (WAS : Broken logical volume group) Richard Troth wrote: > Ivan ... hear this: > With SLES10, unless you are changing something about the root FS, you > do not need to re-stamp your INITRD. It is exactly as you say it > should be. > > > -- R; <>< > > That's good enough for me ;) At least the idea that I would have gave me fodder for a tantrum :P --Ivan -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Checking for tape drives within a script
Assuming they're using a recent version of lin_tape. IIRC, that file didn't appear till about 1.9 of lin_tape (at our request, I believe). At that kernel level, they're more likely using ibmtape drivers, and the amount of status information is limited to what they can scrape out of the mostly-undocumented sysfs files. Easy to find out. Gary, what tape drivers are you using? -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Harder, Pieter Sent: Wednesday, February 11, 2009 11:26 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Checking for tape drives within a script Cat /proc/scsi/IBMtape? Best regards, Pieter Harder pieter.har...@brabantwater.nl tel +31-73-6837133 / +31-6-47272537 -Oorspronkelijk bericht- Van: Linux on 390 Port [mailto:linux-...@vm.marist.edu] Namens Lee, Gary D. Verzonden: woensdag 11 februari 2009 17:07 Aan: LINUX-390@VM.MARIST.EDU Onderwerp: Checking for tape drives within a script Running suse sles9 kernel 2.6.5-7.314. I have a couple of 3592 drives connected via fiberchanel. These are not discovered during the normal boot process. I would like to check for their existance within a script which if they don't exist, will add them to the system during the startup process. I have confirmed adding them, just need to know how to test for their existance so as to put in error checking. Tried lszfcp, but will not work with this kernel version. Any suggestions welcome. __ Information from ESET NOD32 Antivirus, version of virus signature database 3846 (20090211) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.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 Brabant Water N.V. Postbus 1068 5200 BC 's-Hertogenbosch http://www.brabantwater.nl Handelsregister: 16005077 -- 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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 LVM
Yes, as long as you add the same number of physical volumes as you have stripes. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Livio Sousa Sent: Friday, January 16, 2009 2:41 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding dasd to LVM Does somebody know if is possible to extend an ext3 stripped volume? On Tue, Jan 13, 2009 at 3:45 PM, Tom Duerbusch wrote: > Thanks Mike > > I see that now. > > Page 185 shows a move of the old directory, onto the new LVM volume. That > stopped me (reading online instead of printing out the book). Two pages > down, it describes extending a current LVM. > > Tom Duerbusch > THD Consulting > > >>> Michael MacIsaac 1/13/2009 6:49 AM >>> > Tom, > > >> The Redbook "z/VM and Linux on IBM System z The Virtualization > > Cookbook for SLES 10 SP2" has a section "11.2 ... > > > It has the documentation for adding 2 volumes to a new logical > > group and moving an existing directory structure to that group. > Huh? Section 11.1 describes how to create a two volume LVM and mount it > over /home. Section 11.2 describes how to extend the volume group and the > same logical volume to three physical volumes. > > "Mike MacIsaac"(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 > > -- > 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 message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: SWAPGEN and PROFILE EXEC's
We don't use swapgen for exactly this reason. We define the vdisks in the directory, and have an init script that runs very early in the Linux boot that formats and enables the swap partitions. Works fine, and allows us to keep the configuration at a single point. Remember, there's nothing magical about enabling swap. It's done during rc.sysinit, and unless the guest is VERY small, it's unlikely any of the space will be required before the first init script is run. We also use boot-time scripts to configure the network interfaces from files stored on the 191 disk. This way, the IP address can be changed without bringing up the guest. Disadvantage is, every guest needs its own 191 disk, but we get a lot of flexibility this way. There are other ways to handle this I've thought of along the way, but the basic principle is sound. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Friday, January 16, 2009 11:56 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] SWAPGEN and PROFILE EXEC's >>> On 1/16/2009 at 7:57 AM, Michael MacIsaac wrote: >> I would rather control the VDISK sizes in the directory instead of > having PROFILE EXEC > Makes me wonder - can you pass parameters into PROFILE EXEC by setting the > directory? e.g. "IPL CMS 300 524288 301 1048576"? Then use those > parameters with SWAPGEN to make the correct vaddrs and swap space sizes > ... just a thought. This assumes that no one does anything other than use those values. Rob's point is that someone might do something different and hurt overall system performance. I think the idea of having the VDISK defined in the directory, and using SWAPGEN's REUSE option that Rich mentioned is the "safest" way to do this. As at least one person on the list has seen, if you allow "too much" VDISK to be defined and it _gets_used_, it can really hurt you. Regarding using PROFILE EXEC versus COMMAND statements in the CP directory, there is a place for both. One of the benefits of the COMMAND statement is that it gets executed, regardless of the privileges associated with the virtual machine. So, you can have arbitrary guests issue commands at logon time that they would not otherwise be able to in PROFILE EXEC. The conditional logic that PROFILE EXEC provides gives you all sorts of other flexibiltiy. 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 -- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- -- 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: Zfcp.conf
No, it's not necessary, if everything has been done properly. It has to do with when in the boot process the FCP devices are attached. If you ALLOW mkinitrd to put zfcp.conf in the initrd, those disks will be attached before the root filesystem is mounted. If you're okay with that, then it's fine. But if you want more flexibility, it might make more sense to remove zfcp.conf entirely before running mkinitrd. That way, NO FCP disks are attached before the root filesystem mounts, so it's all handled later in the boot process, and it all still works. There are a couple of gotchas with this. In versions prior to RHEL5.2, zfcpconf.sh was run out of /etc/rc.s/rc.sysinit. This resulted in a "chicken-egg" situation when multipath and/or LVM were used, and Red Hat went through several iterations trying to fix it, going all the way back to RHEL4.4. 5.2 triggers the script out of udev, which also nicely solves a race condition in rc.sysinit, where udev doesn't build the device nodes fast enough for LVM to catch them. Far as multipath goes, I don't see why changing the WWPN and Bus ID should have changed the identifier that's stored in the bindings file, but it's possible, since I forget how that's calculated. The simplest way to straighten it all out is to run "multipath -F", remove all entries from the bindings file, and then run "multipath", and let them rebuild. You might have to check to be sure you're mounting filesystems on the right places, though, if you're mounting by node. We're planning to standardize on either using LVM, or mount by label, to avoid this. Two other quick hints: The default location for the bindings file is in /var/lib. If /var is on a separate filesystem from root, the bindings file will be built in the wrong place, or not built at all, and /var will be mounted over it. The latest versions of device-mapper-multipath have a parameter in /etc/multipath.conf that allows you to specify the location of the bindings file. Earlier versions required it to be changed via command line parm, which, of course, required you do surgery on the init script. Finally, the version of mount that comes with RHEL5.2 uses a new scheme to prioritize mounts so that multipath devices and their components don't look like the same disk. This used to cause mount-by-label to fail. If you start getting mount failures, "device busy", or "duplicate device" messages, check file /etc/blkid/blkid.tab. If you've added and removed LUNs, this file can contain residual data that confuses mount. Just delete it, and reboot, it will be rebuilt properly. Good luck! -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Romanowski, John (OFT) Sent: Monday, October 27, 2008 11:31 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Zfcp.conf I don't actually have any Redhats myself but an IBM manual said after changing Redhat's zfcp.conf it's necessary to re-run mkinitrd and zipl to make the zfcp.conf changes survive (take effect) at reboot. Given that and you said " After the reboot, the original paths were still being used.", I suspect the initrd's got the prior contents of zipl.conf built into it and doesn't know yet about your changes to the zfcp.conf file. > 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. -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Spann, Elizebeth (Betsie) > Sent: Monday, October 27, 2008 11:21 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Zfcp.conf > > Duh, no. I'll try it. Is this a guess or have you been successful? > Thanks, > Betsie > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Romanowski, John (OFT) > Sent: Friday, October 24, 2008 7:38 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Zfcp.conf > > Betsie, > After changing zfcp.conf did you run mkinitrd and zipl before rebooting? > > > > > 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. > > > -Original Message- > > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > > Spann, Elizebeth (Betsie) > > Sent: Friday, October 24, 2
Re: Lin_tape build question
It's the "clean" that seems to be causing the trouble, and it shouldn't
be needed. Change the SPEC file in /usr/src/{whatever}/SPECS to remove
that in the "build" section, and try a manual rebuild ("rpmbuild -bb
lin_tape.spec").
My copy of 1.15 doesn't have that, and builds correctly. Haven't tried
1.16 yet.
And you're right, the documentation is terrible.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Lee, Gary D.
Sent: Monday, October 20, 2008 2:19 PM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] Lin_tape build question
Ok, went and downloaded lin_tape for SLES9 on s390x.
However cannot get it to build
Linux version from the boot messages is
Linux version 2.6.5-7.314-s390x ([EMAIL PROTECTED]) (gcc version 3.3.3
(SuSE Linux)) #1 SMP Mon Sep 15 16:43:00 UTC 2008
Below is a portion of the output from the rpmrebuild command listed in
the readme.install.
-
+ '[' s390x == i586 ']'
+ '[' s390x == i686 ']'
+ '[' s390x == ppc64 ']'
+ '[' s390x == powerpc ']'
+ '[' s390x == s390 ']'
+ '[' s390x == s390x ']'
+ proc=zSeries
+ '[' s390x == ia64 ']'
+ '[' s390x == x86_64 ']'
+ cp -af lin_tape_359X_zSeries.ReadMe lin_tape_359X.ReadMe
+ cp -af lin_tape_Ultrium_zSeries.ReadMe lin_tape_Ultrium.ReadMe
+ make KERNEL=2.6.5-7.314-s390x PROC=s390x driver
make -C /lib/modules/2.6.5-7.314-s390x/build
SUBDIRS=/usr/src/packages/BUILD/lin
_tape-1.16.0 PWD=/usr/src/packages/BUILD/lin_tape-1.16.0 clean
make[1]: Entering directory `/usr/src/linux-2.6.5-7.314-obj/s390/s390x'
make[1]: *** No rule to make target `clean'. Stop.
make[1]: Leaving directory `/usr/src/linux-2.6.5-7.314-obj/s390/s390x'
make: *** [clean] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.27660 (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.27660 (%build)
-
Where do I go from here? IBM Tape Device drivers installation and
user's guide seems to be of little help.
Thanks in Advance.
Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
This message w/attachments (message) may be privileged, confidential or
proprietary, and if you are not an intended recipient, please notify the
sender, do not use or share it and delete it. Unless specifically indicated,
this message is not an offer to sell or a solicitation of any investment
products or other financial product or service, an official confirmation of any
transaction, or an official statement of Merrill Lynch. Subject to applicable
law, Merrill Lynch may monitor, review and retain e-communications (EC)
traveling through its networks/systems. The laws of the country of each
sender/recipient may impact the handling of EC, and EC may be archived,
supervised and produced in countries other than the country in which you are
located. This message cannot be guaranteed to be secure or error-free. This
message is subject to terms available at the following link:
http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you
consent to the foregoing.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Searching for IBMtape driver for 64-bit sles9
I'm not sure which ones you got, but the IBMtape drivers are deprecated. The current ones are lin_tape, and there are two dependent packages, IBMtapeutil, and lin_taped. The lin_tape drivers have to be hand-built for a particular kernel level, and IBMtapeutil is provided as part source, and part OCO binary. Lin_taped is provided as a pre-packaged RPM. We did this for Red Hat, not sure how it's handled in SLES. One of the problems we ran into with TSM is that the device nodes created by the driver are arbitrary, and there's no good way to tie them to a particular changer, which is needed for the TSM definitions. Every time a drive is added or removed, the nodes change and you have to redo the TSM config. IBM helped us solve this with a combination of scripts and udev rules. There's information about the drive and changer mapping provided in /proc/IBMtape. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Lee, Gary D. Sent: Friday, October 17, 2008 10:49 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Searching for IBMtape driver for 64-bit sles9 Thanks to the list. Wouldn't have thought of the archives subdir. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Harder, Pieter Sent: Friday, October 17, 2008 10:06 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Searching for IBMtape driver for 64-bit sles9 ftp://ftp.software.ibm.com/storage/devdrvr/Linux/ Best regards, Pieter Harder [EMAIL PROTECTED] tel +31-73-6837133 / +31-6-47272537 -Oorspronkelijk bericht- Van: Linux on 390 Port [mailto:[EMAIL PROTECTED] Namens Lee, Gary D. Verzonden: vrijdag 17 oktober 2008 16:04 Aan: LINUX-390@VM.MARIST.EDU Onderwerp: Searching for IBMtape driver for 64-bit sles9 Trying to get a TSM server set up which will acccess both 3590 and ts1120 tape drives inside a 3494 library. Got the ibmatl package installed, but can't seem to find IBMtape. Any clues where to look? Thanks for the help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 Brabant Water N.V. Postbus 1068 5200 BC 's-Hertogenbosch http://www.brabantwater.nl Handelsregister: 16005077 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: ZFS or LVM2 on Debian?
For performance reasons, if you can afford to dedicate several devices to this, consider striping the LVM2 volume. Use the same number of stripes as you have paths to the DASD. Makes a HUGE difference in performance. Contrary to popular belief, you can still extend the LV later, you just need to do it by the same number of physical volumes as you have stripes. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Eric Chevalier Sent: Monday, October 06, 2008 1:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] ZFS or LVM2 on Debian? Hello Rich, On 10/6/2008 11:25 AM, Rich Smrcina wrote: > LVM is certainly a reasonable approach to this. How much data are you > talking about? Right now we have about a total of 9.5GiB of backup data. However, the amount that's transferred each night is typically much smaller. Based on the replies to my original message, it sounds like ext3 over lvm is the way to go. In fact, I've already installed the lvm components on our system. Many thanks to all who have offered suggestions! Eric -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Gigabit interface on Linux?
This is pretty much the same situation we had. The SA's are used to the tools they know, so when they don't behave as expected on z, they get nervous. I've had questions about grub, netdump, EMC Powerpath, and Veritas VxVM. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scott Rohling Sent: Monday, September 29, 2008 2:13 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Gigabit interface on Linux? They're just trying to confirm what they have.. and using the Linux tools they normally use to do so. I've since explained that a virtual NIC isn't going to show them the physical characteristics of the 'real' NIC and have explained that we've verified the OSA is set to gigabit speed. I guess you could equate it to the 'checkbox eval' -- someone from the app team got on and showed them what mii-tools what indicating and so they naturally started to ask questions or wonder if they needed to set something from the Linux side... Now that I've gotten all the good input, I'm better able to explain what they are seeing and why... Thanks again for all the great responses! Scott Rohling On Mon, Sep 29, 2008 at 11:11 AM, David Boyes <[EMAIL PROTECTED]> wrote: > > Thanks, Bruce -- we did that and confirmed it's set to gigabit.. but > > there > > seems to be concern from the Linux folks as mii-tools is reporting > 100mbs > > and ethtool is not reporting anything... > > I'd actually argue that ethtool is right -- there really isn't any valid > number TO report. Reporting the actual physical interface speed would be > wrong in that the memory speed interface isn't actually limited to that > speed, and reporting the actual memory interface speed is wrong in that > it's a theoretical number that you won't ever actually get. > > I guess my question is: why do they care? Does the application behave > differently with different interface speeds, or is this one of those > checkbox evals where "must have gigE support" is on there? > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Unusual amount of overhead on large volume group
We have some very large LVM2 filesystems, and have only seen one issue. As you add PV's to a VG, the time it takes for the utilities (pvscan, pvs, etc.) to run increases exponentially with the number of volumes. This is because LVM2 puts metadata on every volume by default, and the utilities seem to process the metadata recursively. It was recommended that the "--metadatacopies=0" parameter be used on pvcreate for all but the first couple of PV's in a VG to avoid this. We also found that when you have more than a handful of PV's to work with, striping makes a HUGE difference in performance, so consider that. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scott Rohling Sent: Monday, September 29, 2008 12:50 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Unusual amount of overhead on large volume group I'm confused about how much overhead seems to be involved in creating a volume group that approaches a terabyte with ECKD devices (A mix of some 3390-27 and mostly 3390-9): dxxxml01: ~ > df -h FilesystemSize Used Avail Use% Mounted on /dev/mapper/sysvg-root 2.0G 460M 1.5G 24% / /dev/dasda1 109M 34M 71M 33% /boot tmpfs1005M 0 1005M 0% /dev/shm /dev/mapper/sysvg-var 4.0G 210M 3.6G 6% /var /dev/mapper/sysvg-usr 2.0G 864M 1.1G 46% /usr /dev/mapper/sysvg-home 3.0G 319M 2.5G 12% /home /dev/mapper/sysvg-opt 6.9G 359M 6.2G 6% /opt /dev/mapper/sysvg-tmp 2.0G 68M 1.9G 4% /tmp /dev/mapper/appvg-lotus 9.9G 151M 9.2G 2% /opt/ibm/lotus /dev/mapper/appvg-logdir 20G 173M 19G 1% /opt/ibm/lotus/logdir */dev/mapper/appvg-notesdata 897G 200M 870G 1% /opt/notesdata * dxxxml01: ~ > sudo lvdisplay -v /dev/appvg/notesdata Using logical volume(s) on command line --- Logical volume --- LV Name/dev/appvg/notesdata VG Nameappvg LV UUIDub9Gqh-kAEc-wfxb-lXXi-i9ER-3F9Y-gjyHC2 LV Write Accessread/write LV Status available # open 1 * LV Size911.02 GB * Current LE 233222 Segments 71 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:8 We're going from 911G for the logical volume to 897G displayed in 'df' to only 870G being available in the filesystem.. That's 41G of 'overhead'. Am I just naive about how much space it takes to manage this? Any input welcome! Scott Rohling -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Gigabit interface on Linux?
We actually opened an issue with IBM over this. Here's what I got back: Action Taken...: The ethtool utility is not supported with all device drivers as noted in the man page. It's very typical that for an gigabit NIC (especially a fiber connection) will not have a valid speed reported or no speed reported at all. To some degree it makes a bit of sense as a gigabit card is exactly that, 1GB. That is you can't tell a 1GB FIBER card to run at 10MB. Granted what gets reported by ethtool (really what th device driver is returning is mis-leading). Here is another example .. a very simple Tigon3 GB NIC, note the speed it reported as Unknown! [EMAIL PROTECTED] ~]# ethtool eth0 Settings for eth0: Supported ports: [ FIBRE ] Supported link modes: 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: Unknown! (0) Duplex: Half Port: FIBRE mii-tool is only valid for mii compatable NIC cards. If the goal is to do some performance testing, then the best method is to use the netperf tools. ( see http://www.netperf.org) Another simple test is using dd and ftp, for example: # ftp ftp> bin ftp> put "| dd if=/dev/zero bs=32k count=1" /dev/null Using either of these tools should confirm that the NICS are transfering far faster the 10MB. So in other words, the gigabit OSA can only run at a gigabit, the tools are useless for this application, and the only way to be sure about the throughput is to measure it. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, September 29, 2008 12:14 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Gigabit interface on Linux? >>> On 9/29/2008 at 12:02 PM, in message <[EMAIL PROTECTED]>, Scott Rohling <[EMAIL PROTECTED]> wrote: > On RHEL5.2 -- we're using mii-tools and seeing that the ethernet interface > is set to 100mbs -- the OSA is set to gigabit - and we're wondering if > something special needs to be done to set it to gigabit speeds.. Using > 'ethtool=' doesn't seem to work on Linux (s390x linux).. I'm amazed that mii-tools returns anything at all. > This is on a VSWITCH -- everything works fine except the reported speed... > Any ideas? Since the interface that mii-tools is reporting on is a virtual one, having nothing to do with any real hardware, I would say ignore it. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www
