Boot partition mirror-raid possible?
I am following a HOWTO I found to move my DASD to use LVM on top of RAID1. The instructions assume Intel arch but all goes well until it says to use Grub to write the MBR onto the two partitions with the boot directory on them. Naturally I tried to use zipl but it fails with: # zipl Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu1' Adding #1: IPL section 'linux' (default) Preparing boot device: 09:00. Error: Could not read master boot record: Reached unexpected end of file where /boot is mounted thus: /dev/md1 ext3 97M 14M 79M 15% /mnt/tmp/boot Should I try to mount the actual partitions under boot sequentially? I am new to RAID and am not sure how to proceed. TIA -Robin -- -- Robin Atwood. Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst from Mandalay by Rudyard Kipling -- -- 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: Boot partition mirror-raid possible?
On Wed, Jul 16, 2008 at 11:53 AM, Robin Atwood [EMAIL PROTECTED] wrote: Should I try to mount the actual partitions under boot sequentially? I am new to RAID and am not sure how to proceed. If you want to make another disk bootable you must specify the right directory (and that must be on the target device). The reason is that zipl creates a bootmap in that directory. We used to put the zipl.conf in the /boot directory and point to that one in the command. Don't know whether the scheme with RAID and LVM maps well to Linux on z/VM. If you're just looking for an extra boot device, then you might want to share that with all the other Linux guests. -Rob -- 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: Boot partition mirror-raid possible?
On Wednesday 16 Jul 2008, Rob van der Heij wrote: On Wed, Jul 16, 2008 at 11:53 AM, Robin Atwood [EMAIL PROTECTED] wrote: Should I try to mount the actual partitions under boot sequentially? I am new to RAID and am not sure how to proceed. If you want to make another disk bootable you must specify the right directory (and that must be on the target device). The reason is that zipl creates a bootmap in that directory. We used to put the zipl.conf in the /boot directory and point to that one in the command. Don't know whether the scheme with RAID and LVM maps well to Linux on z/VM. If you're just looking for an extra boot device, then you might want to share that with all the other Linux guests. I think the problem is that my target device is /dev/md1 which is not a real disk, it's a pseudo-device manufactured by the mdadm command from two real partitions. -Robin -- -- Robin Atwood. Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst from Mandalay by Rudyard Kipling -- -- 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: Boot partition mirror-raid possible?
On Wed, Jul 16, 2008 at 12:32 PM, Robin Atwood [EMAIL PROTECTED] wrote: I think the problem is that my target device is /dev/md1 which is not a real disk, it's a pseudo-device manufactured by the mdadm command from two real partitions. That sure is a problem. But since you don't write to the boot partition a lot, could you not just maintain the two identical copies yourself? -- 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: Boot partition mirror-raid possible?
On Wednesday 16 Jul 2008, Rob van der Heij wrote: On Wed, Jul 16, 2008 at 12:32 PM, Robin Atwood [EMAIL PROTECTED] wrote: I think the problem is that my target device is /dev/md1 which is not a real disk, it's a pseudo-device manufactured by the mdadm command from two real partitions. That sure is a problem. But since you don't write to the boot partition a lot, could you not just maintain the two identical copies yourself? That's what I am beginning to think. :( I was hoping someone on the list has tried this and has a definitive answer. -Robin -- -- Robin Atwood. Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst from Mandalay by Rudyard Kipling -- -- 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
Using ESCON attached 3590 for TSM 5.5 / Linux
One of our customers who does not follow this list asked me to post a question here. They are running SLES 10 SP1 in an instance on a FLEX-ES system. (Think of this as running in an LPAR on a normal system. That is, no zVM.) They have an ESCON connected 3590 that they can use from the Linux system with no problem, but apparently there is a 'special' device driver supplied for TSM 5.5 and when they install it, the driver apparently does not 'see' the tape device. They found a statement that TSM only supports Fiber attached tape devices, but we're not sure if Fiber in this context includes ESCON or not and I can't see why TSM should care as long as Linux is happy with the device. Does anyone else have any experience with this combination (TSM 5.5 on SLES 10 with ESCON 3590) or possibly have any suggestions?? Thanks Mike C. M. (Mike) Hammock Sr. Technical Support zFrame IBM zSeries Solutions (404) 643-3258 [EMAIL PROTECTED] __ This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. To reply to our email administrator directly, send an email to [EMAIL PROTECTED] -- 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: Using ESCON attached 3590 for TSM 5.5 / Linux
Am Mittwoch, 16. Juli 2008 schrieb Mike Hammock: They are running SLES 10 SP1 in an instance on a FLEX-ES system. (Think of this as running in an LPAR on a normal system. That is, no zVM.) They have an ESCON connected 3590 that they can use from the Linux system with no problem, but apparently there is a 'special' device driver supplied for TSM 5.5 and when they install it, the driver apparently does not 'see' the tape device. They found a statement that TSM only supports Fiber attached tape devices, but we're not sure if Fiber in this context includes ESCON or not and I can't see why TSM should care as long as Linux is happy with the device. Does anyone else have any experience with this combination (TSM 5.5 on SLES 10 with ESCON 3590) or possibly have any suggestions?? As far as I know, TSM for Linux only supports FCP-attached (scsi) tapes. Channel attachement like FICON or ESCON are not supported. Christian -- 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: Boot partition mirror-raid possible?
On Wed, Jul 16, 2008 at 12:58 PM, Robin Atwood [EMAIL PROTECTED] wrote: That's what I am beginning to think. :( I was hoping someone on the list has tried this and has a definitive answer. Yes, zipl uses specific ioctl() calls of the eckd driver to write the IPL record etc. -Rob -- 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
Cobbler anyone?
Hello list, Anyone heard of cobbler? (no, not the shoe repairman nor the deep-dish fruit dessert with a thick top crust :)) This one: http://cobbler.et.redhat.com/ I wouldn't bother asking, but it seems they are looking at a port to s390x: https://fedorahosted.org/cobbler/wiki/SssThreeNinety Just FYI... Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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: DFDSS Backups
According to the z/os 1.9 DSS Reference manual p688: It (the Standalone RESTORE command) cannot restore from tapes created by a DFSMSdss logical dump, from a DFSMSdss tracks dump using the CPVOLUME keyword, or from dump tapes produced by other utilities. FYI. MA On Tue, Jul 15, 2008 at 11:11 PM, Doug Shupe [EMAIL PROTECTED] wrote: Better check to see if the DFDSS Standalone restore supports CPVOLUME before going to far into the abyss! - Original Message - From: Alan Altmark [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Sent: Tuesday, July 01, 2008 4:40 PM Subject: Re: DFDSS Backups On Wednesday, 06/25/2008 at 01:26 EDT, Mark Post [EMAIL PROTECTED] wrote: On Tue, Jun 24, 2008 at 8:41 PM, in message [EMAIL PROTECTED] , Walters, Gene P [EMAIL PROTECTED] wrote: -snip- I don't know that they use CPFORMAT to format the DASD before telling me it's available. Should they? Yes, since that is what will make the volume available to z/OS. Actually, you can format any CP volume from z/OS. A user volume (one that does NOT contain directory, T-disks, parm disks, paging, spooling, or other CP-managed extents) can be formatted by ICKDSF CPVOLUME or INIT on z/OS, as CP only looks at the volser on a standard VOL1 label. For CP-owned disks, you should format it using ICKDSF CPVOLUME FORMAT. I believe that CPVOLUME and INIT do not write the same style of VTOC. A CPVOLUME will appear to have no available space. An INITed volume, OTOH, appears empty except for the catalog. (I'm too lazy to test that theory.) So while you CAN init with INIT, you SHOULD init with CPVOLUME. Alan Altmark z/VM Development IBM Endicott -- 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 -- 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: Using ESCON attached 3590 for TSM 5.5 / Linux
Thanks Christian... That's what we were afraid of, but were not sure... They are trying to do a proof of concept with their existing equipment (ESCON 3590) and I don't believe there is any way to connect a true FCP or SCSI tape device to the Linux system on a FLEX-ES system, so I suspect they are out of luck for now... I assume that running zVM in the instance/LPAR and attaching the tape device to a Linux guest would not make any difference, correct? If anyone else has any ideas or suggestions, we'd be glad to listen.. Thanks C. M. (Mike) Hammock Sr. Technical Support zFrame IBM zSeries Solutions (404) 643-3258 [EMAIL PROTECTED] Christian Borntraeger [EMAIL PROTECTED] To bm.com LINUX-390@VM.MARIST.EDU Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: [LINUX-390] Using ESCON attached 3590 for TSM 5.5 / Linux 07/16/2008 07:54 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Am Mittwoch, 16. Juli 2008 schrieb Mike Hammock: They are running SLES 10 SP1 in an instance on a FLEX-ES system. (Think of this as running in an LPAR on a normal system. That is, no zVM.) They have an ESCON connected 3590 that they can use from the Linux system with no problem, but apparently there is a 'special' device driver supplied for TSM 5.5 and when they install it, the driver apparently does not 'see' the tape device. They found a statement that TSM only supports Fiber attached tape devices, but we're not sure if Fiber in this context includes ESCON or not and I can't see why TSM should care as long as Linux is happy with the device. Does anyone else have any experience with this combination (TSM 5.5 on SLES 10 with ESCON 3590) or possibly have any suggestions?? As far as I know, TSM for Linux only supports FCP-attached (scsi) tapes. Channel attachement like FICON or ESCON are not supported. Christian -- 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 email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. To reply to our email administrator directly, send an email to [EMAIL PROTECTED] -- 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: Cobbler anyone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael MacIsaac wrote: | Hello list, | | Anyone heard of cobbler? (no, not the shoe repairman nor the deep-dish | fruit dessert with a thick top crust :)) This one: | http://cobbler.et.redhat.com/ | | I wouldn't bother asking, but it seems they are looking at a port to | s390x: https://fedorahosted.org/cobbler/wiki/SssThreeNinety | No, I haven't. I'm curious how it compares to / interacts with Redhat Satellite, though. When I was testing with satellite on distributed platforms I found it difficult to create working client upgrade channel operations, so I'm interested in possible alternatives. - -- Pat -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIfgHoNObCqA8uBswRApYdAJ4gYLcgfG06NXlvhn91Mdf0TrvyVwCeP6vl qGijn4IGVL0PmVtf6EieO4E= =tOyv -END PGP SIGNATURE- -- 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: Cobbler anyone?
Michael MacIsaac wrote: Hello list, Anyone heard of cobbler? (no, not the shoe repairman nor the deep-dish fruit dessert with a thick top crust :)) This one: http://cobbler.et.redhat.com/ I wouldn't bother asking, but it seems they are looking at a port to s390x: https://fedorahosted.org/cobbler/wiki/SssThreeNinety Just FYI... I don't see any plugin for the z/VM SMAPI ;-) mark -- 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: Cobbler anyone?
Mainstar Provisioning Expert http://www.mainstar.com/products/provisioningexpert/ 'Where ever you go - There you are!! ' Richard (Gaz) Gasiorowski Global Solutions Technology Principal Lead Infrastructure Architect 845-773-9243 Work 845-392-7889 Cell [EMAIL PROTECTED] Computer Sciences Corporation Registered Office: 3170 Fairview Park Drive, Falls Church, Virginia 22042, USA Registered in Nevada, USA No: C-489-59 - This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. - -- 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: Using ESCON attached 3590 for TSM 5.5 / Linux
the tape device. They found a statement that TSM only supports Fiber attached tape devices, but we're not sure if Fiber in this context includes ESCON or not It does not. TSM doesn't understand channel-attached tape on Linux at all. FCP-only. Your 3590 is useless for this purpose. Does anyone else have any experience with this combination (TSM 5.5 on SLES 10 with ESCON 3590) or possibly have any suggestions?? If you want a Linux-only solution, buy a FCP tape drive. Or install z/OS.e and use the z/OS TSM to drive your channel-attached tape. Those are the choices on offer from IBM. Since most people don't like those options much, you can also use the remote volume option of the VM TSM server to drive the actual tapes (since it DOES understand channel-attached tape), and configure the Linux TSM server to use the CMS server as the destination for the virtual volumes. Look at the docs for virtual volume support -- there are some limitations but you don't end up with an entire z/OS system just to do backups. -- 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: Boot partition mirror-raid possible?
Robin Atwood wrote: On Wednesday 16 Jul 2008, Rob van der Heij wrote: On Wed, Jul 16, 2008 at 12:32 PM, Robin Atwood [EMAIL PROTECTED] wrote: I think the problem is that my target device is /dev/md1 which is not a real disk, it's a pseudo-device manufactured by the mdadm command from two real partitions. That sure is a problem. But since you don't write to the boot partition a lot, could you not just maintain the two identical copies yourself? That's what I am beginning to think. :( I was hoping someone on the list has tried this and has a definitive answer. -Robin -- -- Robin Atwood. Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst from Mandalay by Rudyard Kipling -- -- 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 fwiw, grub has been patched to work with RAID. A quick grep of the (Red Hat) RPM changelog shows: - add dmraid support ( [snip] - Always install in MBR for raid1 /boot/ [snip] - reworked much of how the RAID1 support in grub-install works. Not sure how hard it would be to implement this in zipl. -- Brad Hinson [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Cobbler anyone?
Anyone heard of cobbler? (no, not the shoe repairman nor the deep-dish fruit dessert with a thick top crust :)) This one: http://cobbler.et.redhat.com/ Several of our university clients use it for Intel lab machines. Depends very heavily on DHCP and PXE, but it's pretty slick when you've got it set up and working. Having PXE support for s390 would be pretty slick, esp if the boot PROM image could be loaded from a NSS. -- 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: Boot partition mirror-raid possible?
Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 16.07.2008 11:53:12: Should I try to mount the actual partitions under boot sequentially? I am new to RAID and am not sure how to proceed. zipl doesn't work with logical volumes, such as RAID1-like mirror setups. The reason behind this is that zipl lacks knowledge about this type of device which prevents it from putting the right type of IPL record into the right place. Because this can cause various types of malfunctions, current versions of zipl even check whether they're pointed at a DASD or ZFCP disk and bail out if neither is the case. This is being worked on and some future version of zipl should be able to cope with a defined set of logical volume setups (no dates given though). Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on System z Development IBM Deutschland Research Development GmbH -- 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: Cobbler anyone?
David Boyes wrote: Anyone heard of cobbler? (no, not the shoe repairman nor the deep-dish fruit dessert with a thick top crust :)) This one: http://cobbler.et.redhat.com/ Several of our university clients use it for Intel lab machines. Depends very heavily on DHCP and PXE, but it's pretty slick when you've got it set up and working. Having PXE support for s390 would be pretty slick, esp if the boot PROM image could be loaded from a NSS. I'm new to cobbler, but over the last few weeks I've been working with the cobbler community to get it working on s390. Eventually cobbler will be integrated into Satellite, as well as the recently announced Spacewalk, the open source Satellite: http://www.redhat.com/spacewalk/ Cobbler has a lot of promise on s390. The immediate goal is to get reprovisioning working, and the ultimate goal is to get bare metal provisioning via PXE working. The current thought is to write a *very* simplified PXE client as a REXX exec run at startup. It presents you with a menu, then based on your choice, uses the z/VM FTP client to download the correct kernel/initrd from the (cobbler) server. It's still in the development stages, so feel free to hit me with ideas and feedback (good or bad of course). Also, a couple of links: Mailing list: https://fedorahosted.org/mailman/listinfo/cobbler IRC: irc.freenode.net, #cobbler -Brad -- 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 -- Brad Hinson [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Boot partition mirror-raid possible?
On Wed, Jul 16, 2008 at 5:53 AM, in message [EMAIL PROTECTED], Robin Atwood [EMAIL PROTECTED] wrote: I am following a HOWTO I found to move my DASD to use LVM on top of RAID1. The instructions assume Intel arch but all goes well until it says to use Grub to write the MBR onto the two partitions with the boot directory on them. Naturally I tried to use zipl but it fails with: Peter has already indicated this won't work (today). But to follow up a little more, I would say to think about what you're doing and why. Using RAID 1 in a system is almost always done to prevent a system outage when a disk fails. If that happens on a mainframe Linux system, you've got bigger problems than worrying about whether your system will reboot if needed. Using software RAID can make a lot of sense on Linux for System z, but I wouldn't think that doing it for /boot (on ECKD) would be in that category. 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
Re: Cobbler anyone?
Having PXE support for s390 would be pretty slick, esp if the boot PROM image could be loaded from a NSS. This could be easily accomplished by using the CMS IPLer and a very stripped down Linux kernel and a port of the PXE loader code. It's basically TFTP plus some little stuff. If you went the Linux route, you could use the IPLer to put the NSS with the minikernel system into memory in one piece, do the normal PXE DHCP and tftp steps to put the kernel into a fixed location, and then crash the boot ROM image by jumping directly to the new kernel. -- 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
update-status and parse-metadata CPU load
Hello, I just returned from a disaster recovery test. After we restored our Linux for zSeries guests, we booted up several at one time. We noticed the system being very sluggish. I jumped on each of them and noticed that either a process called update-status or parse-metadata was running on all of them and consuming most if not all of the CPU. To get around the problem, I killed the offending process and went about finishing the test. Here at home I have not noticed this to be a problem. However at our DR site it appears to be. We contract with a IBM to perform DR tests at one of their BCRS sites. I am told that the hardware we are testing on is 3 generations or so behind what we have at home. It has a fraction of the number of CPUs that we have at home. It also has a lot less memory than we have at home. Performance problems show up in this environment. I have spent some quality time with google looking this up. All of the hits appear to be Intel based and have a list of some processes to stop running (using the runlevel editor) and/or packages to uninstall. So far I have not found any information on what is recommended for a zSeries system. At home, I do not have a problem. There are sufficient resources to let parse-metadata and update-status do their thing. At our DR location, we have a problem Any recommendations for a zSeries system? Is killing the offending process the right thing to do? Thanks, Ron Foster Baldor Electric -- 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: Cobbler anyone?
Hi, I've been looking at getting cobbler to run on s390x to serve as a provisioning manager for x86 (and friends). It installs without too much fuss on RHEL 5.2. Getting it to install on SLES10 SP2 looks far more challenging. Our immediate need is for rapid x86 provisioning (we have the s390x provisioning down to a science). Cheers, Arty -- 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: update-status and parse-metadata CPU load
On Wed, Jul 16, 2008 at 5:36 PM, in message [EMAIL PROTECTED], Ron Foster at Baldor-IS [EMAIL PROTECTED] wrote: Hello, I just returned from a disaster recovery test. After we restored our Linux for zSeries guests, we booted up several at one time. We noticed the system being very sluggish. I jumped on each of them and noticed that either a process called update-status or parse-metadata was running on all of them and consuming most if not all of the CPU. To get around the problem, I killed the offending process and went about finishing the test. chkconfig novell-zmd off You can either use YaST Online Update to do maintenance, or use the zypper command in place of rug. Fortunately, zmd is going away with SLE11, leaving only zypper and YOU. Starting with SLES10 SP2, any new installs for System z novell-zmd is disabled by default. 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
