Re: Mapping Minidisks to File Systems
S390utils on RHEL contains the lsdasd command, which shows this. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Gentry, Stephen Sent: Tuesday, January 29, 2008 10:48 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Mapping Minidisks to File Systems Not a command per se but I look at the VM console log file for that linux instance. It usually tells what mdisk address is associated with linux name (dasda, dasdb, dasdc, etc). Steve G. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mrohs, Ray Sent: Tuesday, January 29, 2008 10:40 AM To: LINUX-390@VM.MARIST.EDU Subject: Mapping Minidisks to File Systems Hi, What's the best way for an admin to quickly see which minidisks map to which Linux file systems? Is there one command that parses the contents of fstab and /proc/dasd/devices? Ray Mrohs U.S. Department of Justice 202-307-6896 -- 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: Building kernel modules on Linux 390
Coming into this a bit late, so sorry if I missed the point... On Red Hat, there's a supplied kernel-devel package that has JUST ENOUGH of the kernel source to allow you to build third-party modules. You only really need the full source package if you're going to rebuild the kernel itself, or modules that are officially part of the source tree. They use symlinks from /usr/lib/modules/bla-bla into /usr/src/linux/kernels/bla-bla too. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, November 30, 2007 2:20 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Building kernel modules on Linux 390 >>> On Fri, Nov 30, 2007 at 3:40 AM, in message <[EMAIL PROTECTED]>, Rob van der Heij <[EMAIL PROTECTED]> wrote: -snip- > I have a vague recollection that you also need to install the > additional packages that ship the source of assorted kernel modules > (like vmcp for example). Admitted my most intimate experiences with > the process go back to SLES7 and SLES8, but building the SuSE Linux > kernel out of sources was extremely tricky (relied on other things > happening in the right order, but not validating that). These days (speaking of SLE10), the kernel packages have the symlinks into /usr/src/, and all you really need is the kernel-source RPM, and your own code, to build kernel modules. I haven't really tried to build a whole kernel recently, but I believe it just requires a "make somekindofconfig" followed by "make image" with an optional "make modules". 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.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: Linux community, was Re: Demo of OpenSolaris running on Systemz: oqo
I've been watching the OQO for a couple of years now. The only thing holding me back has been the price. There are a number of similar devices in the UMPC form factor. I DID buy a mini-pc a couple of years ago that runs Linux and Hercules very well. It's about the size of a CD player, but that has no keyboard or display of it's own. (Similar to a Mac-mini.) It WAS considerably cheaper than an OQO or UMPC though. http://www.boldata.com -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, November 30, 2007 1:49 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Linux community, was Re: Demo of OpenSolaris running on Systemz: oqo >>> On Fri, Nov 30, 2007 at 1:44 PM, in message <[EMAIL PROTECTED]>, Jay Maynard <[EMAIL PROTECTED]> wrote: -snip- > Has anyone gotten Linux running on it? I'm not interested in a Windows box, > but if it ran Linux, I'd buy one just to run Hercules on for the cool > factor. It would appear a number of people have, according to Google: http://linuxplanet.com/linuxplanet/reviews/6231/1/ http://www.handtops.com/forum/752/0//OQO_Linux_Installation__amp_Configu rati.html http://www.handtops.com/forum/752/0//OQO_Linux_Installation__amp_Configu rati.html --- lots more--- Mark Post 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: Linux community, was Re: Demo of OpenSolaris running on Systemz
One of my personal fantasies is to run zOS under Hercules on an OQO. Licensing issues aside, THAT would be cool! -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Cox Sent: Friday, November 30, 2007 8:18 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Linux community, was Re: Demo of OpenSolaris running on Systemz > accumulator patterns in the proper DEC colors. Includes REAL Emacs, and > most of the DEC languages (Bliss, C, COBOL, Fortran, etc) that survived. As they used to say "Bliss is ignorance" ;) > I have it running on my handheld -- full-on OPCOM and Galaxy batch in a > shirt pocket. Now that's personal automation. 8-) I used to have Hercules running on an IBM PC-110 (handheld PC). Not terribly useful but very good for "This is the new S/390 portable" mind games with sales people. Alan -- 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: Demo of OpenSolaris running on System z
Met him once, a few years back, when we were doing Linux-on-z the first time. Nice guy, very smart. Wore wrist braces because of carpal tunnel problems. Hope he's doing better with that. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Andrews Sent: Thursday, November 29, 2007 9:29 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Demo of OpenSolaris running on System z On Thu, 2007-11-29 at 06:36 -0500, Evans, Kevin R wrote: > Nice to see a face to David Boyes, having seen him post numerous times. Look here for more monitor abuse: http://linuxvm.org/community/index.html -- David Andrews A. Duda and Sons, Inc. [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 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: "Large" Number of DASD on zLinux on zVM
Udev should handle this on recent versions of Red Hat (RHEL). The nodes will automatically be built from dasda-dasdz, then dasdaa-dasdzz, and dasdaaa-dasdzzz. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Friday, October 26, 2007 1:21 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] "Large" Number of DASD on zLinux on zVM We run over 30 3390 mod 27 devices in a single Linux image w/o problems. Did you extend the /dev/dasd devices past /dev/dasdz? This could account for the problem... Although 800-81f is 31 devices, so I may be way off base. -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - "In theory, theory and practice are the same, but in practice, theory and practice are different." On 10/26/07 10:59 AM, "Hall, Ken (GTI)" <[EMAIL PROTECTED]> wrote: > Is your dasd driver a module, and are you using an initrd? > > If this is the case, the range is taken from /etc/modprobe.conf in the > initrd, not /etc. You need to rebuild the initrd and reboot. > > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Ron Henry > Sent: Friday, October 26, 2007 11:53 AM > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] "Large" Number of DASD on zLinux on zVM > > > I have a RedHat Linux machine on zVM 5.2 and I am trying to put about > 40 3390 mod 9s on it. Each device is a full-pack minidisk. > > The machine boots up fine and runs but doesn't have all its dasd. > > a "#CP Q V DASD" shows that the Linux machine has all the DASD mapped to > virtual addresses 800-82B. > > The /proc/dasd/devices only goes as far as 81F. Likewise the /dev/dasd. > > My /etc/zipl.conf allows for 800-83F. > > What have I messed-up here? I am still new to Linux on VM. -- 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: "Large" Number of DASD on zLinux on zVM
Is your dasd driver a module, and are you using an initrd? If this is the case, the range is taken from /etc/modprobe.conf in the initrd, not /etc. You need to rebuild the initrd and reboot. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ron Henry Sent: Friday, October 26, 2007 11:53 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] "Large" Number of DASD on zLinux on zVM I have a RedHat Linux machine on zVM 5.2 and I am trying to put about 40 3390 mod 9s on it. Each device is a full-pack minidisk. The machine boots up fine and runs but doesn't have all its dasd. a "#CP Q V DASD" shows that the Linux machine has all the DASD mapped to virtual addresses 800-82B. The /proc/dasd/devices only goes as far as 81F. Likewise the /dev/dasd. My /etc/zipl.conf allows for 800-83F. What have I messed-up here? I am still new to Linux on VM. Any help greatfully appreciated. Thanks, Ron Henry -- 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: Is anyone connecting to a Hitachi SAN-box with FCP NPiV?
We're getting ready to try it with EMC DMX. IBM has been very supportive, but we have a contract with them. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Collinson.Shannon Sent: Tuesday, October 23, 2007 10:22 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Is anyone connecting to a Hitachi SAN-box with FCP NPiV? We wanted to connect to our SAN-box using FCP NPiV for either open-systems server storage (using TSM) or to implement the new GDPS function of DR-mirroring the open-systems storage. However, the IBM representative we talked to said that they couldn't support us if we ran into any problems (either with connectivity or possibly data corruption) unless we were connecting to an IBM box. It kinda scared us off the idea. Is anyone successfully using non-IBM storage (especially Hitachi) with FCP NPiV? Shannon Collinson l Mainframe Operating Systems l ETI l SunTrust Banks l 404.827.6070 (office) l 404.642.1280 (mobile) Seeing beyond money (sm) LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. SunTrust and Seeing beyond money are federally registered service marks of SunTrust Banks, Inc. [ST:XCL] -- 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: Defining an LPAR on a z box to run LINUX
When we first tried Linux in an LPAR, about 3 months ago, we were concerned about this. The LPAR we were using was defined for another purpose, and had access to 12,000+ DASD devices. We went to IBM, and they recommended CIO_IGNORE. I tested that under VM, and it appeared to work, but when we tried it in the real LPAR, the kernel couldn't find ANY DASD devices. Rather than delay the test, we booted without the parm, and it came up fine, 12,000+ devices and all (they were scoped down in the module parm). It took about 5 minutes to scan them all on our z9 with Ficon. We haven't tried Linux in an LPAR again since, so I have no way to determine what went wrong. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, August 02, 2007 9:41 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Defining an LPAR on a z box to run LINUX > > > You should also use cio_ignore= to ignore all devices you might want > > to > > > use later but not now. The major issue (besides regulating access) is > > > not IPL time (though applications like HAL are extremely slow to start > > > with many devices) > > > > Can be order of 45-50 minutes with 16K devices. > > Ugh. Do you know what takes so long (HAL?) FWIW, in-kernel detection of > devices is now done in max. 30 seconds due to parallelism (unlike 2.4, > which literally may take hours if some devices behave badly). Seems to spend most of it's time figuring out what kind of device it is. As you say, newer versions are faster. I prefer to see it as another compelling reason to run z/VM and not mess with Linux in LPARs. 8-) > But nevertheless: Know how to use cio_ignore= :) Indeed. -- 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: LVM/Ext3 extend
It works in 2.6.9 in RHEL4 using ext2online. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kyle Smith Sent: Tuesday, July 31, 2007 10:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] LVM/Ext3 extend Now that I think about it, it was after 2.6.9 that it was rolled into the mainline kernel because I seem to recall it not working w/RHEL 4. The LWN article I pointed to states it was added to the -mm tree in 2.6.7 but I think it was closer to 2.6.11 when it was added to Linus' tree... ks On 7/31/07, Kyle Smith <[EMAIL PROTECTED]> wrote: > > Newer versions of the kernel support online resizing of ext3. To be > specific, 2.6.7 and newer allow you to do it [1], which sadly means you > won't be able to do it with SLES 9. SLES 10, RHEL 4 and newer should all > support it. > > [1] http://lwn.net/Articles/89560/ > > -- 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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
Udev should handle this automatically. Like I said in the previous note, however, it can take up to 10 seconds for the device node to appear. Race conditions of this type appear to be common during rc.sysinit, and also affect fcp devices, particularly when you use them in combination with LVM and/or multipath. Red Hat supposedly has a fix either available or coming soon. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, July 02, 2007 2:54 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] vmcp during boot results in Error: Could not open device /dev/vmcp: No such device >>> On Mon, Jul 2, 2007 at 2:32 PM, in message <[EMAIL PROTECTED] rg>, Susan Zimmerman <[EMAIL PROTECTED]> wrote: > Hi Mark. > > I noticed /sys/class/misc/vmcp was 10 63 > > OSA-LNX1:~ # cat /sys/class/misc/vmcp/dev > 10:63 > > So I deleted /dev/vmcp and manually created the node > > as 10 63 > > and now it works just fine. In addition to what Adam said about making sure to rebuild your initrd and re-run zipl, be careful of what you've done here. On one of my test systems, the device node is 10:61, so it can vary from system to system. If you rmmod the vmcp module, the device node _should_ go away. When you modprobe it again, it should appear dynamically. 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.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: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device
There's a delay between the time the module gets loaded and udev notices and creates the device node. This has bit us on other devices (tape, fcp) as well. We've had some discussions with Red Hat about it, and there's supposed to be some kind of fix in RHEL 4.5 or 5.0. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Susan Zimmerman Sent: Monday, July 02, 2007 1:43 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] vmcp during boot results in Error: Could not open device /dev/vmcp: No such device Hi Mark. I moved vmcp to the INITRD_MODULES but it still results in the same message. during boot: Starting udev Creating devices Loading kernel/drivers/s390/char/vmcp.ko z/VM CP interface loaded . . . Error: Could not open device /dev/vmcp: No such device +++ RC=3 +++ my settings now are: INITRD_MODULES="vmcp" ## Type:string ## ServiceRestart: boot.loadmodules # # This variable contains the list of modules to be loaded # once the main filesystem is active # MODULES_LOADED_ON_BOOT="" >From what I can tell, the device exists... OSA-LNX1:/ # ls -l /dev/vmc* crw--- 1 root root 10, 62 Jun 29 13:06 /dev/vmcp OSA-LNX1:/ # Thanks again for any and all help! Susan -- Date:Fri, 29 Jun 2007 14:34:23 -0600 From:Mark Post <[EMAIL PROTECTED]> Subject: Re: vmcp during boot results in Error: Could not open device /dev/vmcp: No such device >>> On Fri, Jun 29, 2007 at 4:31 PM, in message = , Susan Zimmerman <[EMAIL PROTECTED]> wrote:=20 > Hi Listers. >=20 > I am trying to issue a vmcp command within a boot script and receive the > following message during boot: >=20 > Error: Could not open device /dev/vmcp: No such device > +++ RC=3D3 +++ >=20 > Once the system is booted, I can see the device... >=20 > Any ideas on how to make this device permanent? Which distribution are you running? On SLES, you can add vmcp to the list = of modules that need to be in the initrd by editing /etc/sysconfig/kernel INITRD_MODULES=3D"vmcp" 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.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: Hercules 3.05 announcement
Runs very well under Fedora 7, as long as you build it there. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Thursday, June 28, 2007 9:20 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Hercules 3.05 announcement Jay Maynard wrote: > On Thu, Jun 28, 2007 at 02:20:34AM -0400, Rick Troth wrote: >> Seems to be fine after building on a slightly newer system. >> (Still have broad coverage so that the new Herc can "drop in" >> to most other systems around here.) Sorry for the false alert. > > How new? The distribution RPM was built on Red Hat 9, but I'm probably going > to put up a new system for building on due to some incompatibilities. I'd > like to use as old a system as possible, however, jsut to make it as broadly > useful as possible. Bear in mind that rpm changes over time, and some rpms that used to build might not now. If you can manage it (with xen?), I suggest building on a fully virtualised RHL and RHEL-clone. You don't need to distribute binaries for both, just verify the build and execution for both before releasing binaries. I s'pose one could use recent Fedora rather than RHEL-Clone. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Please do not reply off-list -- 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: PAV and RHEL 4 issue, not found on pathvec
I have device-mapper-multipath-0.4.5-16.1.RHEL4, but based on what I saw, I
don't see how this can be fixed without an update to the kernel driver. The
driver at the U4 level doesn't export vendor and model info into sysfs, so
there doesn't appear to be any way for device-mapper-multipath to identify a
rule set for dasd.
I know this was fixed in RHEL5.
>From /sys/bus/ccw/devices/0.0.0100] on RHEL4:
availability cmb_enable detach_state discipline readonly
block cutype devtype online use_diag
>From /sys/bus/ccw/devices/0.0.0100] on RHEL5:
alias bus devtype eer_enabled readonly uid
availability cmb_enable discipline modalias subsystem use_diag
block:dasda cutype driver online uevent vendor
Is there a kernel for RHEL4 that supports this?
Incidentally, the default configuration under RHEL5 still uses volume label to
match up pairs, but that's prone to problems if you have a mix of dedicated
devices and minidisks, and happen to end up with a duplicate label. There's a
"uid" field in sysfs now, wouldn't it make more sense to use that?
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Bader
Sent: Friday, June 15, 2007 9:26 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] PAV and RHEL 4 issue, not found on pathvec
Hm, update 4. Which device-mapper-multipath package is that? Found the
following on RHN:
device-mapper-multipath-0.4.5-21.RHEL4-s390x
-device-mapper-multipath is now able to handle DASD devices
Mit freundlichem Gruß / Regards,
Stefan Bader
SW Linux on zSeries Development
[EMAIL PROTECTED]
IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Herbert Kircher
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
--
When all other means of communication fail, try words.
Linux on 390 Port wrote on 15.06.2007 15:16:27:
> My multipath.conf (not including commented lines)
>
> defaults {
> user_friendly_names yes
> }
> devices {
> device {
> vendor "IBM"
> product "S/390 DASD ECKD"
> path_grouping_policymultibus
> getuid_callout "/sbin/dasdview -j -f /dev/%n"
> path_checkerdirectio
> }
> }
>
> My rhel version is:
>
> Red Hat Enterprise Linux AS release 4 (Nahant Update 4)
> 2.6.9-42.EL #1 SMP Wed Jul 12 23:21:43 EDT 2006 s390x s390x s390x
GNU/Linux
>
> Thanks!
> Eric
>
> Stefan Bader wrote:
> > Yes, with older kernels you have to stay with dasdview and the labels.
> > Unfortunately this isn't
> > quaranteed to be unique. But it is the only way for older kernels.
> > About the blacklist_execptions: I guess it will depend on the service
> > level of RHEL4 whether
> > the keyword actually is in or not. We would have to check the current
and
> > latest version numbers.
> > what did you put into blacklist_exceptions? The statement that should
> > enable all DASDs should
> > be:
> >
> > blacklist_execptions {
> > device {
> > vendor "IBM"
> > product "S/390 DASD.*"
> > }
> > }
> >
> > Eric's problem seems to be a bit stranger. The "not found in pathvec"
(yes
> > that is more of an informational
> > statement) indicates the scan found the DASD devices. But after that,
> > there is no probing to the devices
> > at all.
> > Just to make sure I don't miss anything: which level of RHEL4 are we
> > talking? And how does the multipath.conf
> > (only lines that are not commented out) look like?
> >
> > Mit freundlichem Gruß / Regards,
> > Stefan Bader
> >
> > SW Linux on zSeries Development
> > [EMAIL PROTECTED]
> >
> > IBM Deutschland Entwicklung GmbH
> > Vorsitzender des Aufsichtsrats: Martin Jetter
> > Geschäftsführung: Herbert Kircher
> > Sitz der Gesellschaft: Böblingen
> > Registergericht: Amtsgericht Stuttgart, HRB 243294
> >
>
--
> > When all other means of communication fail, try words.
> >
> > Linux on 390 Port wrote on 15.06.2007
14:28:41:
> >
> >
> >> I spent a lot of time going around with this. The problem seemed to
> >> come down to that with the kernel I'm using (2.6.9-42.0.8), the dasd
> >> driver doesn't provide vendor and model info in sysfs, so device-
> >> mapper-multipath can't match up the devices with a rule set. The
> >> newer driver in RHEL5 does provide this, and I was able to get it to
> >> work there. If someone else has found a workaround, I'd love to
> >> hear it, because we have situations where we'd love to use PAVs, and
> >> have been assuming they're not supported till RHEL5.
> >>
> >> Incidentally, the "pathvec" message seems to be semi-normal. It
> >> also show
Re: PAV and RHEL 4 issue, not found on pathvec
I spent a lot of time going around with this. The problem seemed to come down to that with the kernel I'm using (2.6.9-42.0.8), the dasd driver doesn't provide vendor and model info in sysfs, so device-mapper-multipath can't match up the devices with a rule set. The newer driver in RHEL5 does provide this, and I was able to get it to work there. If someone else has found a workaround, I'd love to hear it, because we have situations where we'd love to use PAVs, and have been assuming they're not supported till RHEL5. Incidentally, the "pathvec" message seems to be semi-normal. It also shows up on our multipath FCP devices, but they do work. There's also a syntax issue with the blacklist section of the multipath.conf file, at least on RHEL5. The default blacklist includes dasd*, but there's a "blacklist exceptions" section that's supposed to override this by vendor/model code. That section is invalid unless there's a "blacklist" section, so you can't remove the blacklist entirely. You need to put SOMETHING in the blacklist, even if it's bogus. The "exceptions" bit doesn't appear to work anyway, if "dasd*' is in the blacklist, the devices won't be examined. One more problem was that the mapper uses dasdview to pull the labels from the devices, and uses the labels to match up devices. If you're using minidisks for your non-PAV devices, and you happen to have a duplicate volume label, the mapper creates a multipath group for the pair (in our case, it was / and /var), and they're marked "busy". When the script tries to mount them by base device node, the mounts fail, and the boot process stops. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Bader Sent: Friday, June 15, 2007 7:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] PAV and RHEL 4 issue, not found on pathvec Hi Eric, short answer: if "multipath -ll" doesn't show anything, your setup still isn't correct. Now for some more information. Is the output of "multipath -v3" that you sent complete? It sound a bit strange. If DASDs aren't blacklisted there should be some action. The "not found in pathvec" is normal for an inittial run. It just says there hasn't been any information about the paths gathered, yet. You might increase the verbosity level to 6 and send it (proably to me directly, since it gets quite large). So we might see why the multipath volumes aren't created. Mit freundlichem Gruß / Regards, Stefan Bader SW Linux on zSeries Development [EMAIL PROTECTED] IBM Deutschland Entwicklung GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Herbert Kircher Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- When all other means of communication fail, try words. Linux on 390 Port wrote on 14.06.2007 17:49:17: > This is not the exact issue I am seeing... > > Here are my results and this is the case before and after the change to > multipath.conf per the bugz workaround. > > # multipath > # > # multipath -v3 > load path identifiers cache > # > # all paths in cache : > # > path dasda not found in pathvec > > = path info dasda (mask 0x1f) = > path dasdb not found in pathvec > > = path info dasdb (mask 0x1f) = > path dasdc not found in pathvec > > = path info dasdc (mask 0x1f) = > path dasdd not found in pathvec > > = path info dasdd (mask 0x1f) = > md0 blacklisted > ram0 blacklisted > ram10 blacklisted > ram11 blacklisted > ram12 blacklisted > ram13 blacklisted > ram14 blacklisted > ram15 blacklisted > ram1 blacklisted > ram2 blacklisted > ram3 blacklisted > ram4 blacklisted > ram5 blacklisted > ram6 blacklisted > ram7 blacklisted > ram8 blacklisted > ram9 blacklisted > > Interesting enough though iostat has the exact same stats for both > /dev/dasdb and /dev/dasdd and when running pvscan I receive the following: > dasdb0.00 0.00 0.00 0.000.000.00 0.00 > 0.0022.67 0.00 23.33 13.33 0.00 > dasdd0.00 0.00 0.00 0.000.000.00 0.00 > 0.0022.67 0.00 21.67 13.33 0.00 > > pvscan > Found duplicate PV sAHQBBquhyI5mbrj8QdvW3zM4YKXjEod: using /dev/dasdd1 > not /dev/dasdb1 > PV /dev/dasdd1 lvm2 [2.29 GB] > Total: 1 [2.29 GB] / in use: 0 [0 ] / in no VG: 1 [2.29 GB] > > So my question is, is PAV working or not? If it is how can I be certain > it is? multipath -ll returns no data that would lead me to believe > multipathing is working. > > Thoughts / assistance? > > Thanks! > > > Bradford Hinson wrote: > > This looks related to: > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238983 > > > > (see error msg at end of comment 0) > > > > On Thu, 2007-06-14 at 08:56 -0400, Eric Sammons wrote: > > > >> Hi, > >> > >> I am trying to configure PAV on RHEL 4 and am running into a problem. I > >> have
Re: FCP - shared disk [was: RHEL 4 - FCP - tape drives]
Here's what we were told: Without NPIV, the FCP CHPID acts like a shared HBA, and all LUNS are visible to all virtual machines in all LPARs. Only one OS instance can use a given LUN, however. If another tries, the LUN will appear busy. WITH NPIV, the system assigns an arbitrary virtual WWPN to each individual address (device number/subchannel). On the storage side, the SAN admins map/mask/whatever to the virtual HBA port names. The LUNs can be mapped to multiples, so sharing LUNs is possible. To share tape drives between zLinux instances for TSM server, NPIV is required. For us, this whole business of arbitrary virtual port names has serious DR implications. That, coupled with the whole business of having to code specific WWPNs in zfcp.conf, has caused us to proceed very slowly with FCP devices in general. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Richard Troth Sent: Tuesday, June 05, 2007 1:09 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] FCP - shared disk [was: RHEL 4 - FCP - tape drives] Sir Alan spake: > NPIV has nothing to do with sharing across LPARs. > Sharing is simply a matter of giving an multiple LPARs > access to different subchannels the same FCP chpid. I was thinking the same thing, however ... Your SAN team may need to zone or mask things differently if multiple LPARs have access to a device and you're not using NPIV. Case in point for me is one volume (one LUN, a disk) that I need to share across five VM systems, each in its own LPAR, one physical box, one CHPID (per path), one WWPN (per path). The host presents one entity to the fabric, without NPIV, so when I (try to) bring the volume on-line in another LPAR, it fails because it is busy. I don't know SAN fabric capabilities well enough to know if this is supposed to work without special tricks, or without them, or at all. I suspect that with NPIV it will work except that our SAN team would have to zone the LUN to multiple hosts. (But we want to do that eventually anyway.) It stretches the whole disk sharing thing beyond System z and z/VM and lets Sun, HP, AIX, and the rest enjoy the pain. This is disk, not tape, if that matters. -- R; -- 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: RHEL 4 - FCP - tape drives
Near as we can tell, tape_3590 drivers are for FICON attached drives, and aren't actually supported anymore. If you poke around the IBM web pages, they tell you to switch to the lin_tape drivers, and FCP attached tape. We've been trying to set up TSM server on zLinux, and that's the only supported configuration. If someone has different information, I'd love to hear it. We couldn't find ANY clear explanation of exactly what was supported by tape_3590, except in a German Powerpoint presentation, where they alluded to FICON. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ayer, Paul W Sent: Tuesday, June 05, 2007 11:57 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] RHEL 4 - FCP - tape drives I am RHEL 4.4 here is a modinfo for tape_34xx and also zfcp [EMAIL PROTECTED] ~]# modinfo tape_34xx filename: /lib/modules/2.6.9-42.EL/kernel/drivers/s390/char/tape_34xx.ko license:GPL description:Linux on zSeries channel attached 3480 tape device driver ($Revision: 1.21 $) author: (C) 2001-2002 IBM Deutschland Entwicklung GmbH alias: ccw:t3490m*dt3490dm00* alias: ccw:t3480m*dt3480dm00* depends:tape vermagic: 2.6.9-42.EL SMP gcc-3.4 [EMAIL PROTECTED] ~]# modinfo zfcp filename: /lib/modules/2.6.9-42.EL/kernel/drivers/s390/scsi/zfcp.ko parm: loglevel:log levels, 8 nibbles: FC ERP QDIO CIO Config FSF SCSI Other, levels: 0=none 1=normal 2=devel 3=trace parm: device:specify initial device license:GPL description:FCP (SCSI over Fibre Channel) HBA driver for IBM eServer zSeries author: Heiko Carstens <[EMAIL PROTECTED]>, Martin Peschke <[EMAIL PROTECTED]>, Raimund Schroeder <[EMAIL PROTECTED]>, Wolfgang Taphorn <[EMAIL PROTECTED]>, Aron Zeh <[EMAIL PROTECTED]>, IBM Deutschland Entwicklung GmbH alias: ccw:t1731m03dt1732dm04* alias: ccw:t1731m03dt1732dm03* depends:qdio,scsi_mod,scsi_transport_fc vermagic: 2.6.9-42.EL SMP gcc-3.4 [ -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Tuesday, June 05, 2007 11:45 AM To: LINUX-390@vm.marist.edu Subject: Re: RHEL 4 - FCP - tape drives On Tue, 2007-06-05 at 09:29 -0600, Mark Post wrote: > >>> On Tue, Jun 5, 2007 at 9:33 AM, in message > <[EMAIL PROTECTED]>, "Hall, Ken > (GTI)" <[EMAIL PROTECTED]> wrote: > > We just went through this. > > > > First, you need the lin_tape package from IBM. That has the > > device-specific drivers for the tape drives. You might have to find the > > source RPM and rebuild it to get a version that matches your kernel. > > This doesn't sound right to me. What distribution are you running? > > > Mark Post For RHEL 4, there are tape modules already built in: # ls /lib/modules/2.6.9-42.EL/kernel/drivers/s390/char/*tape* /lib/modules/2.6.9-42.EL/kernel/drivers/s390/char/tape_34xx.ko /lib/modules/2.6.9-42.EL/kernel/drivers/s390/char/tape_class.ko /lib/modules/2.6.9-42.EL/kernel/drivers/s390/char/tape.ko # modinfo tape_34xx filename: /lib/modules/2.6.9-42.EL/kernel/drivers/s390/char/tape_34xx.ko license:GPL description:Linux on zSeries channel attached 3480 tape device driver ($Revision: 1.21 $) author: (C) 2001-2002 IBM Deutschland Entwicklung GmbH alias: ccw:t3490m*dt3490dm00* alias: ccw:t3480m*dt3480dm00* depends:tape vermagic: 2.6.9-42.EL SMP gcc-3.4 > > -- > 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 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)
Re: RHEL 4 - FCP - tape drives
We just went through this. First, you need the lin_tape package from IBM. That has the device-specific drivers for the tape drives. You might have to find the source RPM and rebuild it to get a version that matches your kernel. The zcfp.conf file has five fields, but only three are meaningful. Here's a sample: 0.0.0a00 0x01 0x50060482d52e5d48 0x01 0x The first field is the device number, the second is meaningless, third is the WWPN of the tape drive (make sure you have your zoning right!), fourth field is also meaningless, and the last field is the LUN, which for real IBM tapes is supposedly always zero. Note that in the LUN, only the first two bytes are meaningful, so LUN 0001 would be coded as 0x0001. We were successful with real IBM drives, but when we tried an EMC VTAPE box that was supposed to emulate them, we got a kernel panic, so try defining the drives manually via SYSFS before setting up zfcp.conf, or you might end up with an unbootable system. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ayer, Paul W Sent: Tuesday, June 05, 2007 8:50 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] RHEL 4 - FCP - tape drives Hi Ray, Yes that's what I did cd /sys/bus/scsi/devices and did an ls ... empty also a cat /proc/scsi and cat /proc/scsi/scsi is empty too. lstape is blank. On the wwnn and wwpn side at first I was trying to use what filled in there when I echo'ed 1 to online but then on the vm console I would see an error. Later I was able to get the real wwnn and for the tape_controler and the wwpn for each of the two tape drives (putting them on 0.0.1a06 and 0.0.a107) Now when I try to start them there are no errors and also when I boot the System the boot messages say that SCSI is stating ok. I'm still a bit unsure as to how to setup the /etc/zfcp.conf format and am hopping that is my problem but again following the steps I the doc works fine for all the /sys/bus/scsi/drivers stuff but not the devices stuff. A vmcp q fcp does show 1a06 and 1a07 are attached. Thanks, -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Raymond Higgs Sent: Monday, June 04, 2007 6:00 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: RHEL 4 - FCP - tape drives Linux on 390 Port wrote on 06/04/2007 03:08:28 PM: > Hi Brad, > > Thanks for the info. > > I have been using the 1st document and all items work fine when doing > the commands to /sys/bus/drivers ... but when I move over to the > /sys/bus/scsi/devices .. is always empty. > > Paul > Paul, If you're having problems with commands like these: # cat /sys/bus/scsi/devices/0\:0\:1\:0/hba_id 0.0.010a # cat /sys/bus/scsi/devices/0\:0\:1\:0/wwpn 0x5005076300c18154 # cat /sys/bus/scsi/devices/0\:0\:1\:0/fcp_lun 0x5719 # cat /sys/bus/scsi/devices/0\:0\:1\:0/block/dev 8:0 # cat /sys/bus/scsi/devices/0\:0\:1\:0/block/sda1/dev 8:1 There are extra '\' characters in there. The SCSI device IDs should be written like 0:0:1:0. Go into the directory, and do an ls to see what your SCSI device IDs look like. Mine look like this: [EMAIL PROTECTED]:cd /sys/bus/scsi/devices [EMAIL PROTECTED]:ls 0:0:0:0 1:0:0:0 2:0:0:0 3:0:0:0 [EMAIL PROTECTED]:cat /sys/bus/scsi/devices/3:0:0:0/hba_id 0.0.c403 [EMAIL PROTECTED]:cat /sys/bus/scsi/devices/3:0:0:0/wwpn 0x500507630510477a [EMAIL PROTECTED]:cat /sys/bus/scsi/devices/3:0:0:0/fcp_lun 0x40114081 Thanks, Ray Higgs System z FCP Development Bld. 706, B24 2455 South Road Poughkeepsie, NY 12601 (845) 435-8666, T/L 295-8666 [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 -- 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
Re: Is there a better place to ask about Linux-390 under Hercules?
The disk issue is most likely the parameter passed to the DASD driver in modprobe.conf. I think all of the distros handle it the same way. Remember, if you change the address list, and you're using an initrd, you might have to rebuild the initrd. On the listserv title, send a note to [EMAIL PROTECTED] with: SET SUBJ In the body. You can get a list of commands by sending "LISTSERV REFCARD" in the body. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Thursday, February 15, 2007 3:25 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Is there a better place to ask about Linux-390 under Hercules? Carey Tyler Schug wrote: > Actually my first questions are more general: > > 1. How do I get Linux to recognize new devices? Specifically I have > installed the Debian version, but it won't recognize additional disks > (like for swapping) Possibly oneone here can answer that, but it may be Hercules-specific, and I'm sure te Herculeans can answee it. > > 2. Is there a searchable archive of this list? Going through titles > makes it difficult to see if my questions were already answered. Or > examples of using the list server to search? My one attempt to search > via the list server command failed. Google can search almost anything; go read up on how to google with intent. > > 3. Can I get the list server to put the name of the list in the title? > I couldn't find it in the refcard. Why would you want that? -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Please do not reply off-list -- 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 If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Time Zone problem
The tzdata RPM is a noarch, so a version from any distro that's even close should work. I had been asked to look into this, and I was watching for the change to RHEL4, but there has never been any mention in the changelog for the package. So I did a quick search, and found out about using the zdump command. It turns out that even the tzdata-2005m package from RHEL4 update 2 has the proper definitions for 2007. It looks like they anticipated the change to the dates, and prepositioned the update. If the current RPMs are incompatible, Lea might be able to extract the tables from the package and install them manually. Alternatively, pull the latest sources from the tzdata source package, adjust the tables manually, and use zic to compile them. Zdump will tell you if you got it right. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Tuesday, January 09, 2007 11:50 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Time Zone problem One of the downsides of running an OS that's been out of support for 3 years. Since there's no executable code in the timezone RPMs, you could just take one from RHEL, or Fedora. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stahr, Lea Sent: Monday, January 08, 2007 11:23 AM To: LINUX-390@VM.MARIST.EDU Subject: Time Zone problem I have what I think is a major Linux problem (not on s390 of course). I have a large Red Hat 8 cluster. I have searched the Red Hat database and found the Time Zone patch https://rhn.redhat.com/errata/RHEA-2006-0745.html but it does not list a RH8 version. Any ideas? I have the patch for SuSE already and am installing that already on my 15 systems. I found the RHEL3 patch listed also that I need. Lea Stahr Linux/Unix Team 630-753-5445 [EMAIL PROTECTED] If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Installed package differences (minor off-topic digression)
The sounds are burned into my brain. The difference between the '33 with local echo (Tzchunk), remote-echo (as used with PDP8) Tchunk, and no echo (as used with PDP8 logging into TSS8) Tzzz Tzzz Tzzz... Oh well, enough of that.. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, December 27, 2006 4:21 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Installed package differences (minor off-topic digression) > Wish I still had my ASR33, although I don't miss the LA30. > I was trying to describe the unique sounds of a Teletype to my > 15-year-old son the other day. A cross between chambering a round in a bolt-action rifle and a toy sewing machine whose batteries are a little bit run down. You get a bit more "crunchy" high-note if the tape punch is enabled. Then there's that unique whine that DECwriters had, especially if you wired the cable for hardware flow control so you could actually run 1200 baud. Now I *really* feel old. -- db -- 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 If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Installed package differences (minor off-topic digression)
Nope, sold it. Wish I hadn't. -Original Message- From: Tom Duerbusch [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 27, 2006 4:13 PM To: Hall, Ken (GTI); LINUX-390@VM.MARIST.EDU Subject: Re: Installed package differences (minor off-topic digression) "Discribe the sounds?" Why? Isn't yours working? Mine still works. Tom Duerbusch THD Consulting (KSR33 with 8 level paper tape unit) >>> [EMAIL PROTECTED] 12/27/2006 2:56 PM >>> Wish I still had my ASR33, although I don't miss the LA30. I was trying to describe the unique sounds of a Teletype to my 15-year-old son the other day. >>-- db (whose ASR33 and LA36 are working just fine, thank you.) If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Installed package differences (minor off-topic digression)
Wish I still had my ASR33, although I don't miss the LA30. I was trying to describe the unique sounds of a Teletype to my 15-year-old son the other day. >>-- db (whose ASR33 and LA36 are working just fine, thank you.) If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: sles 10 install - 32 bit packages
Same thing happens on RHEL4, and it confused me at first. Shared libraries & such are installed twice, so you can run both 32 and 64 bit binaries on the 64 bit versions. The 32 bit libraries go in /usr/lib, and the 64 bit ones in /usr/lib64. This can produce some interesting problems if package builders aren't aware that 's390x' is a 64-bit arch. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Levy, Alan Sent: Thursday, December 21, 2006 1:07 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] sles 10 install - 32 bit packages I noticed that while the software packages were being installed, there were a lot of packages that said 32 bit. Can someone tell me what they are used for ? Can I deselect them from the software ? Will I be able to run applications that I am currently running on sles9 31 bit ? -- 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 If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: ooRexx & Bastille for SLES10?
Suse distributed Bastille with SLES8 and SLES9 (IIRC), but it didn't work. When I called for support, I was told it was known to be broken, and not supported on 390/z. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Stephanie A Maginn Sent: Thursday, December 21, 2006 12:01 PM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] ooRexx & Bastille for SLES10? I have installed SUSE SLES10 under z/VM. This is my first time installing Linux. Is there a version of ooRexx that runs on SLES10 (64 bit)? I found an x86 version, but I think it is only 32 bit. I also can't seem to find Bastille for SLES10. Yast can't find it on the installation CD's (an NFS with copies of the .iso files). Is there something I am doing wrong? Or is it really not there? Thanks, Steph 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 If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Central vs Expanded Storage
Actually, in it's original form (on 3090 or 9021, IIRC), Expanded storage was physically different memory. It was slower, and therefore cheaper. As real storage got cheaper, it was positioned as a paging-avoidance mechanism until the OS could be enhanced to address more real storage. HDS used the fact that their memory was all the same, and you could move the line between types at will, as a selling point. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry Sent: Friday, November 03, 2006 1:42 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Central vs Expanded Storage * PGP Signed by an unknown key: 11/03/2006 at 01:42:26 PM Hi Steve, the faster option is "not to page", which is an option if you have more real memory i.e. Central storage. Paging *OUT* from Expanded Memory, if I understand correctly, requires first bringing the data into Central storage so that it can then be written to DASD. If Expanded storage offered a better paging solution then don't you think z/OS would have retained support for it? Expanded storage, I believe, originated as physically separate storage in the days before 64bit addressing. The z9 no longer has such limitations. Sorry I didn't want a rehash, and yes I will search the archives (a pointer would have been nice.) Mark Steve Gentry wrote: > Mark, respectfully, this has been hashed over many times, even recently. > Check the archives. > Think about it, which would it be faster to page from extended storage, > which is memory or a disk drive, which is going to be > slower?If you allocated all to real and you still had to page, then > you'd by pass the extended storage and go straight to dasd. > There are others here who can go into far more technical details about the > "internals" of VM and why it likes extended storage. > I think the consensus from the group and even IBM is to define some > extended storage. > Hope this helps a little. > Regards, > Steve G * Unknown Key * 0x14419D74 (L) -- 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 If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: SMART Card Problem mapping to our Linux Drives
Assuming these are Samba shares under Linux, there's a mechanism in Samba to map users between the Windows client and Samba. Check the Samba doc for details. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brown, Larry J. Sent: Thursday, November 02, 2006 11:17 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] SMART Card Problem mapping to our Linux Drives Hello, hopefully someone is doing this and can give us some pointers on what we need to do or at least where to start. Currently, we have a few Linux (SUSe SLES 8) instances running under z/VM 5.2.0 (IFL) that we use basically as file servers. We manually keep the Linux ID/PW file in sync with Windows active directory. When a Linux user is assigned an ID, it is the same as Windows, and then they are instructed to go in and change their PW to match their windows PW before attempting to map the drive/s. So, when a user logs on to the network, it is actually their active directory (I'm not sure how this all works, but believe this is the basic premise) ID and PW that is passed on to Linux-390 to map several network drives to their windows environment. Works fine - our user community is not very big, so it is easy enough to manage the Linux IDs/PWs. Problem is however, we are soon going to implement a 'Smart Card' logon process for our windows environment and it doesn't look like our current process will continue to work. Our 'smart card' IDs appear to be a 10 digit numeric + @domain name. When we test, it appears Windows passes this on to Linux to try and map the drive, and fails since it doesn't match the Linux ID/PW. We were going to try and set up an ID in Linux to match the Smart Card ID and PIN, but Linux won't allow the numeric ID. Any ideas out there, anybody else using smart card windows logon and accessing Linux-390 drives? I'm fairly new here, and not the actual Linux Admin, so if you need any more info, I'll need to go to him for more specifics. Thanks, Larry Brown Enterprise Server Support USMEPCOM 847-688-3680 x7275 DSN 792-3680 x7275 [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 If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Linux under VM:Operator
The autologin patch wasn't part of SLES8 when I was using that, but it's in RHEL4. I don't know about SLES9 or 10. Check the man page for mingetty to make sure. To enable, just change the line in /etc/inittab from: 1:2345:respawn:/sbin/mingetty console --noclear to: 1:2345:respawn:/sbin/mingetty console --noclear --autologin root This will drop the console to a root (#) prompt after the system finishes coming up. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Bates, Bob > Sent: Wednesday, September 13, 2006 11:06 AM > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] Linux under VM:Operator > > > I've was reviewing the archives, reading over notes from > Share and I still can't figure it out. > > I am running Linux under z/VM and want to be able to monitor > and interact with them through VM:Operator. I've already got > the talking part done but when the system comes up I have to > enter the userid and password. I see mentions of changing > inittab to do things that might alleviate the need but its > just passing me by. > > What to I need to get a user active through ttyS0 without > needing to pass a password in the open or place one in a file > that is readily viewable? > > Thanks in advance > > Bob Bates > Citigroup Technology Infrastructure > 817-317-8033 > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Methods to move DVD software to zLinux?
DVD's should be able to convert to ISO files. I've gotten DVD ISO images of Fedora that mount just like CD ISOs, and burn onto DVD-Rs. You still might need a Linux-x86 box somewhere in there though, to avoid case-mangling issues with Windows. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Romanowski, John (OFT) > Sent: Tuesday, September 12, 2006 3:13 PM > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] Methods to move DVD software to zLinux? > > > Have Oracle on a DVD and want to install it on z/VM SLES 9 guest; of > course the mainframe doesn't have a DVD drive. > > How do you folks install DVD software on the mainframe? > > I don't have a unix/linux server with a DVD drive to NFS share to the > guest. Have only windoz PC's with DVD drives and sftp and scp client > software. > > For a CD I'd convert it to an iso file, sftp it to the guest and > loopback mount it, but DVD's don't convert to iso files, > right? (Maybe > Oracle has the software on CD's instead of DVD?) > > Perhaps zip the DVD, sftp it to guest and gunzip it? > > tia > > This e-mail, including any attachments, may be confidential, > privileged or otherwise legally protected. It is intended > only for the addressee. If you received this e-mail in error > or from someone who was not authorized to send it to you, do > not disseminate, copy or otherwise use this e-mail or its > attachments. Please notify the sender immediately by reply > e-mail and delete the e-mail from your system. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO > LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: SLES vs RHEL
Considering we're using both, I'd assume so. There's a minor bug in the FCP implementation though. Red Hat is working on it. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Smith, Ann (ISD, IT) > Sent: Thursday, August 31, 2006 12:13 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] SLES vs RHEL > > > RH is priced by virtual machines now Maybe that's where the > Netbackup vendor got the idea. > Last time I had checked RH was only twice as much as SuSE for the > license. > But as to the real reason we run SuSE- RedHat at least used to lag > behind a year or 2 is providing new features that we needed > such as SAN > and hipersockets. Has RedHat finally caught up in functionality? > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Rich Smrcina > Sent: Wednesday, August 30, 2006 11:36 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: SLES vs RHEL > > SLES was first to the market and appears to have a better > grip on the z > marketplace. From what I've heard the RH pricing model is by how many > virtual machines you run, where the Novell pricing model is > strictly by > how many CPUs you have. RH lost some traction with their > more stringent > non-OCO requirement (which may have helped more than not, > since now the > OSA Express and 3590 drivers are OSS). > > Others will certainly chime in with their reasons. > > Evans, Kevin R wrote: > > Without wishing to stir up a firestorm here, we are working > on a proof > > > of concept project here with RHEL on z series hardware. I > have noticed > > > that most of the questions here seem to be about SLES...so I was > > wondering why? > > > > > > > > Is this because: > > > > > > > > RHEL is more stable (therefore less questions)? > > > > SLES is used by more people (therefore more questions)? > > > > Something else? > > > > > > > > We are not set on a distribution yet although will be a > choice between > > > SLES and RHEL. > > > > > > > > Inquiring minds want to know . > > > > > > > > TIA > > > > > > > > Kevin > > > > > > > > Kevin R Evans > > > > > > > > Software Engineer Staff IV > > > > Lockheed Martin Information Technology > > > > Federal Bureau of Investigation > > > > 1000 Custer Hollow Road > > > > Clarksburg > > > > WV, 26306 > > > > > > > > 304-625-5870 > > > > > > > > > > > -- > > 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 > > > > -- > Rich Smrcina > VM Assist, Inc. > Phone: 414-491-6001 > Ans Service: 360-715-2467 > rich.smrcina at vmassist.com > > Catch the WAVV! http://www.wavv.org > WAVV 2007 - Green Bay, WI - May 18-22, 2007 > > -- > 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 communication, including attachments, is > for the exclusive use of addressee and may contain proprietary, > confidential and/or privileged information. If you are not > the intended > recipient, any use, copying, disclosure, dissemination or > distribution is > strictly prohibited. If you are not the intended recipient, > please notify > the sender immediately by return e-mail, delete this communication and > destroy all copies. > ** > *** > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: SLES vs RHEL
Red Hat has also been very cooperative with us on our extended POC study.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Ceruti, Gerard G
> Sent: Thursday, August 31, 2006 2:43 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] SLES vs RHEL
>
>
> Kevin
>
> In our case SUSE was prepared to let us have a look at the
> software for
> 6 months for the POC and RH only 30 days before they wanted money.
>
> Regards
> Gerard Ceruti
>
> __
>
>
> Standard Bank Disclaimer and Confidentiality Note
>
> This e-mail, its attachments and any rights attaching hereto
> are, unless the context clearly indicates otherwise, the
> property of Standard Bank Group Limited
> and/or its subsidiaries ("the Group"). It is confidential,
> private and intended for the addressee only. Should you not
> be the addressee and receive this e-mail by
> mistake, kindly notify the sender, and delete this e-mail,
> immediately and do not disclose or use same in any manner
> whatsoever. Views and opinions
> expressed in this e-mail are those of the sender unless
> clearly stated as those of the Group. The Group accepts no
> liability whatsoever for any loss or
> damages whatsoever and howsoever incurred, or suffered,
> resulting, or arising, from the use of this email or its
> attachments. The Group does not warrant the integrity
> of this e-mail nor that it is free of errors, viruses,
> interception or interference. Licensed divisions of the
> Standard Bank Group are authorised financial services providers
> in terms of the Financial Advisory and Intermediary Services
> Act, No 37 of 2002 (FAIS).
> For information about the Standard Bank Group Limited visit
> our website http://www.standardbank.co.za
> __
> _
>
> --
> 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
>
If you are not an intended recipient of this e-mail, please notify the sender,
delete it and do not read, act upon, print, disclose, copy, retain or
redistribute it. Click here for important additional terms relating to this
e-mail. http://www.ml.com/email_terms/
--
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: SLES vs RHEL
Okay, RHEL4 is 2.6.9-42.0.2 (can they get any more digits?) as of today's update. Looks like they're leapfrogging. My FC5 x86 machine is 2.6.17. I forget whether Red Hat said they would be going that high in RHEL5 (probably not), but if they are doing it for Intel, they'll be doing it on z. Is SLES10 for x86 out already? Is Suse still releasing x86 and z out-of-sync with each other? Red Hat releases new versions and updates for all archs at the same time. Makes it easier to keep our x86 and zSeries systems consistent. > > What's the kernel level for SLES10? I thought I recalled > RHEL4 was slightly higher than SLES9. > > On IA32 it's 2.6.16.21. > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: SLES vs RHEL
> > If you're paying for SLES and yast doesn't work, whinge and complain > about it:-) I do think it has some bugs, and some components may be a > little frail (I got openldap set up, and then broke it, but OTOH I got > openldap set up much more easily than on RHEL or Debian or FC). > Don't get me started on either Suse support OR openldap... If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: SLES vs RHEL
My experience with Yast has not been good. Maybe it's better now, but when I used it, it tended to break things and hide shadow copies of configuration files where we couldn't find them, then write over our customized REAL files when we least expected. After having to fix a couple of broken systems by hand, we gave up using it. But please, no religious wars! What's the kernel level for SLES10? I thought I recalled RHEL4 was slightly higher than SLES9. Suse does seem to like ReiserFS a lot. RHEL4 doesn't even include it in the base. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > John Summerfield > Sent: Wednesday, August 30, 2006 11:46 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] SLES vs RHEL > > > Evans, Kevin R wrote: > > Without wishing to stir up a firestorm here, we are working > on a proof > > of concept project here with RHEL on z series hardware. I > have noticed > > that most of the questions here seem to be about SLES...so I was > > wondering why? > > > > > > > > Is this because: > > > > > > > > RHEL is more stable (therefore less questions)? > > > > SLES is used by more people (therefore more questions)? > > > > Something else? > > > > > > > > We are not set on a distribution yet although will be a > choice between > > SLES and RHEL. > > > > I recommend you do your POC on both. > > > > > > Inquiring minds want to know . > > > > I suspect RH is a little more conservative; SUSE defaults to reiserfs > (which is newer than ext2/3), whereas you have to try fairly > hard to get > RHEL installed on it, I'd rather ext3, I still see the occasional > complaint about reiserfs. > > OTOH I think SLES has better configuration tools (in Yast, > everything's > anchored at a single point) than RHEL (they're a bit harder to find, > some seem to be there just so as to tick a box on a list, some work > unsatisfactorily with a text interface (I'm thinking network > configuration), many don't have a text interface AFAIK, > > You can, at present, get an evaluation copy of SLES and SLED for the > trouble of registering and downloading. RH is supposedly > going into beta > for RHEL5 in Sep (was Aug), & releasing at year's end. This will be > about equivalent to SLES 10, which has just been released. > > > I'd be surprised if there's much difference in performance > _iff_ you use > the same filesystems, the differences will be in the tools such as > installation & configuration, and in the support channel. > > The one you use should be the one you prefer, you may well decide the > best configuration tool is /usr/bin/vim and that the > configuration tools > don't matter. > > > -- > > Cheers > John > > -- spambait > [EMAIL PROTECTED] [EMAIL PROTECTED] > Tourist pics > http://portgeographe.environmentaldisasters.cds.merseine.nu/ > > do not reply off-list > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Swap partition "filling up" on RHEL4 - NOT
This is the road I've been down before re disk-based swapping, and in principle, I agree, BUT... I can't justify that at the moment, even if it's just because 1) We have no experience with it, and 2) We're at a point in the process where we can't make major configuration changes. I also believe virtual disk requires zVM memory backing, and we're not sure we can afford that without a lot of analysis. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Rich Smrcina > Sent: Wednesday, August 30, 2006 11:37 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Swap partition "filling up" on RHEL4 - NOT > > > If you're running under VM, make the swap devices a virtual > disk. They > can handle a significantly higher load than the real disk. > > Hall, Ken (GTI) wrote: > > I tracked down a copy of the actual report from the > performance guy, and it turns out we've been (partially) > barking up the wrong tree. Sorry for the confusion. > > > > The real story is that the large swap partition DEVICE was > 100% BUSY during part of the test. The original summary > report said 100% FULL, so we've all been going around trying > to explain that. What I now suspect was actually happening > was that the memory load increased to the point that the > instance started paging heavily and saturated the path to one > of the swap devices. > > > > This makes a lot more sense, but the problem is still > there, just a little different. > > > > We definitely have a memory constraint, so we're going to > increase the memory allocation for the instance, but would it > also help to use multiple small-ish swap partitions as a > safety net for peak periods? (Please don't start up the > debate on whether to use disk-based swap devices at all. > I've been through that, and the alternatives won't fly here > right now.) > > > > Right now, the busy (larger) swap device has a priority of > -2, and the other (smaller) one has a priority of -1 > (defaults). The load problem appeared on the larger one, > implying that it was getting hit harder (far harder than the > smaller partition during peak periods). I found a howto that > indicates that if you set multiple partitions to the same > priority, they get used "round robin", instead in in > "spillover" mode, but this might not help either. > > > > If we set several partitions to equal priority, does the > kernel do any kind of load balancing between partitions? It > wouldn't do much good if it keeps trying to use a heavily > loaded swap device. > > > > Thanks for all of the suggestions, and apologies for > starting down the wrong road earlier. > > > > > > If you are not an intended recipient of this e-mail, please > notify the sender, delete it and do not read, act upon, > print, disclose, copy, retain or redistribute it. Click here > for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ > > > -- > 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 > -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007 -- 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 If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: SLES vs RHEL
All I can tell you is from our experience. When we first looked at Linux a few years back (2002 or so), Red Hat didn't have a usable s390/zSeries distribution. We started with SLES7, and moved to SLES8. It wasn't till (relatively) recently, with RHEL3 for zSeries, that Red Hat had anything worth looking at. This delay might have allowed Suse to get feet in a number of doors, and once in, they stayed. We took a "break" from Linux-on-mainframe for a while, and coming back into it, we went with Red Hat (RHEL4), mainly because our x86 Linux base uses it, and we're trying to maintain compatibility. Red Hat keeps their x86 and z distributions in sync. There are some level differences between the two, some packaging anomalies, and a few things missing on one or the other. Stability wise, I can't really say much. RHEL4 is MUCH more stable than SLES8 ever was, but it's a much newer code base, so you can't really compare. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Evans, Kevin R > Sent: Wednesday, August 30, 2006 11:23 AM > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] SLES vs RHEL > > > Without wishing to stir up a firestorm here, we are working on a proof > of concept project here with RHEL on z series hardware. I have noticed > that most of the questions here seem to be about SLES...so I was > wondering why? > > > > Is this because: > > > > RHEL is more stable (therefore less questions)? > > SLES is used by more people (therefore more questions)? > > Something else? > > > > We are not set on a distribution yet although will be a choice between > SLES and RHEL. > > > > Inquiring minds want to know . > > > > TIA > > > > Kevin > > > > Kevin R Evans > > > > Software Engineer Staff IV > > Lockheed Martin Information Technology > > Federal Bureau of Investigation > > 1000 Custer Hollow Road > > Clarksburg > > WV, 26306 > > > > 304-625-5870 > > > > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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
Swap partition "filling up" on RHEL4 - NOT
I tracked down a copy of the actual report from the performance guy, and it turns out we've been (partially) barking up the wrong tree. Sorry for the confusion. The real story is that the large swap partition DEVICE was 100% BUSY during part of the test. The original summary report said 100% FULL, so we've all been going around trying to explain that. What I now suspect was actually happening was that the memory load increased to the point that the instance started paging heavily and saturated the path to one of the swap devices. This makes a lot more sense, but the problem is still there, just a little different. We definitely have a memory constraint, so we're going to increase the memory allocation for the instance, but would it also help to use multiple small-ish swap partitions as a safety net for peak periods? (Please don't start up the debate on whether to use disk-based swap devices at all. I've been through that, and the alternatives won't fly here right now.) Right now, the busy (larger) swap device has a priority of -2, and the other (smaller) one has a priority of -1 (defaults). The load problem appeared on the larger one, implying that it was getting hit harder (far harder than the smaller partition during peak periods). I found a howto that indicates that if you set multiple partitions to the same priority, they get used "round robin", instead in in "spillover" mode, but this might not help either. If we set several partitions to equal priority, does the kernel do any kind of load balancing between partitions? It wouldn't do much good if it keeps trying to use a heavily loaded swap device. Thanks for all of the suggestions, and apologies for starting down the wrong road earlier. If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Swap partition "filling up" on RHEL4
Yes, it does, and we haven't, although the performance folks use it extensively on x86 Linux, and have great confidence in it. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Rich Smrcina > Sent: Wednesday, August 30, 2006 9:43 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Swap partition "filling up" on RHEL4 > > > Does 'Teamquest' run on the websphere machine? If so, don't discount > the possibility that it caused the problem. > > Hall, Ken (GTI) wrote: > > You've put your finger on the crux of the matter there. > We're not sure. > > > > We believe it was Teamquest that reported the error, but > the first mention of this issue came from someone who's on > vacation right now. > > > > I would have been inclined to discount the message except > for the hanging threads and IBM's report that this was caused > by a memory shortage. > > > >> -Original Message- > >> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > Behalf Of > >> Carsten Otte > >> Sent: Wednesday, August 30, 2006 10:55 AM > >> To: LINUX-390@VM.MARIST.EDU > >> Subject: Re: [LINUX-390] Swap partition "filling up" on RHEL4 > >> > >> > >> Hall, Ken (GTI) wrote: > >>> Here's how it looks NOW. Can't speak for the time of the failure. > >> You stated, one swap device is full and another is not (at > the time of > >> failure). Where do you get that data from? > >> > >> cheers, > >> Carsten > >> -- > >> Carsten Otte has stopped smoking: Ich habe in 3 Monate, 5 > Tage und 22 > >> Stunden schon 470,07 Euro gespart anstatt 1.958,63 Zigaretten > >> zu kaufen. > >> > > -- > Rich Smrcina > VM Assist, Inc. > Phone: 414-491-6001 > Ans Service: 360-715-2467 > rich.smrcina at vmassist.com > > Catch the WAVV! http://www.wavv.org > WAVV 2007 - Green Bay, WI - May 18-22, 2007 > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Swap partition "filling up" on RHEL4
You've put your finger on the crux of the matter there. We're not sure. We believe it was Teamquest that reported the error, but the first mention of this issue came from someone who's on vacation right now. I would have been inclined to discount the message except for the hanging threads and IBM's report that this was caused by a memory shortage. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Carsten Otte > Sent: Wednesday, August 30, 2006 10:55 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Swap partition "filling up" on RHEL4 > > > Hall, Ken (GTI) wrote: > > Here's how it looks NOW. Can't speak for the time of the failure. > You stated, one swap device is full and another is not (at the time of > failure). Where do you get that data from? > > cheers, > Carsten > -- > Carsten Otte has stopped smoking: Ich habe in 3 Monate, 5 Tage und 22 > Stunden schon 470,07 Euro gespart anstatt 1.958,63 Zigaretten > zu kaufen. > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Swap partition "filling up" on RHEL4
This is consistent with what I've observed, but it's nice to have confirmation. Here's the current swap configuration: FilenameTypeSizeUsedPriority /dev/dasdd1 partition 516136 40360 -1 /dev/dasdf1 partition 1032460 11732 -2 At the request of another, I supplied /proc/meminfo in a separate post. Note that the above reflects the current (idle) state of the instance. We have another load test scheduled this week, so we hope to get some more info then. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Alan Cox > Sent: Wednesday, August 30, 2006 9:06 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Swap partition "filling up" on RHEL4 > > > Ar Mer, 2006-08-30 am 08:21 -0400, ysgrifennodd Hall, Ken (GTI): > > We've been going around trying to figure out: 1) why we suddenly > > should have run out of virtual memory (if we did, because we never > > even got close to that before), and 2) why it was reported in this > > way. Does anyone know if there's anything in the swap space > > management mechanism that would cause Linux to fail malloc > if a single > > swap partition fills up? Is there some kind of process affinity for > > paging to swap spaces? > > #1 no idea - maybe you hit a worst case or a memory leak in it ? Java > and other garbage collectors are also a common source of large brief > spikes in memory usage. > > #2 Linux uses the swap according to the priority of the swap files and > swap partitions. When one fills it will move onto the next. Memory > allocations are failed according to the overcommit settings. > > The default behaviour is "fail allocations that will obviously fail". > This allows overcommit of resources (so you can get process > kills due to > out of memory) but tries to avoid obvious cases. > > A seperate mode is available which assumes all allocation requests > should be allowed until the box goes totally out of memory. > This is only > for specialist scientific applications > > The third mode prevents overcommit and will fail allocations > when it is > theoretically possible for an overcommit situation to occur, this is > used for high reliability environments where having to deploy > extra swap > "just in case" is preferable to, say, having your air traffic control > system self destruct. > > Alan > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Swap partition "filling up" on RHEL4
Here's how it looks NOW. Can't speak for the time of the failure. MemTotal: 1345376 kB MemFree: 6968 kB Buffers: 73984 kB Cached: 134016 kB SwapCached: 10784 kB Active:1110932 kB Inactive: 105864 kB HighTotal: 0 kB HighFree:0 kB LowTotal: 1345376 kB LowFree: 6968 kB SwapTotal: 1548596 kB SwapFree: 1496504 kB Dirty: 364 kB Writeback: 0 kB Mapped:1024648 kB Slab:91356 kB Committed_AS: 4402024 kB PageTables: 5536 kB VmallocTotal: 4293582848 kB VmallocUsed: 3540 kB VmallocChunk: 4293577724 kB There are two WAS JVM instances running (for two separate apps). To meet service targets, they've been increasing the memory allocation for each of these. I believe they're currently set to 512m, and the "real" storage allocation was increased to 1.3 gb. to allow for this. Various people have suggested increasing "real" memory still further, but we're approaching the point where it might affect other instances under VM, so we need justification and we haven't seen anything concrete. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Carsten Otte > Sent: Wednesday, August 30, 2006 10:38 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Swap partition "filling up" on RHEL4 > > > Carsten Otte wrote: > > Malloc fails when there is no more free memory except the > emergency pool > > and no swap slots are free. Note that anonymous pages in > memory may well > > occupy both a swap slot and a pysical page in swap cache at > the same time. > May we see /proc/meminfo content of the system? > > Carsten > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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
Swap partition "filling up" on RHEL4
We've been doing some load testing with WAS on RHEL4 under VM, and the other day something weird came up. The machine is defined with 1.3 gb. storage under zVM 5.2, and about 1.5 gb. swap space in two partitions: One about 1 gb. (dasdf), and the other about .5 gb. (dasdd) We use a product called "Teamquest" to monitor the system during the test, and as we were running, it suddently reported "dasdf" was 100% full. WAS started to choke, and analysis of a crashdump appeared to show threads hung consistent with malloc failures. We've been going around trying to figure out: 1) why we suddenly should have run out of virtual memory (if we did, because we never even got close to that before), and 2) why it was reported in this way. Does anyone know if there's anything in the swap space management mechanism that would cause Linux to fail malloc if a single swap partition fills up? Is there some kind of process affinity for paging to swap spaces? If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Filesystem type and re-sizing filesystems
You can resize ext2 and ext3 filesystems while mounted with ext2online. It's a standard part of RHEL4. I don't know about other distributions. We've used it, and it works fine. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Carsten Otte Sent: Monday, August 28, 2006 12:44 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Filesystem type and re-sizing filesystems Carsten Otte wrote: > I don't know what you mean by "dynamic", but you can resize ext3 > filesystems with resize2fs. There is also a patch that allows online > resizing of ext3 filesystems (that is, resizing while the filesystem > is mounted). I don't know about the state of it, therefore I would > avoid to use it in production environments for the time being. > Resize2fs should be part of the e2fsprogs package in sles as far as I > know (I don't have a Sles at hand to verify that). To avoid misinterpretion: I would feel safe to use resize2fs after backup of a production system, then do an e2fsck -f before going production again. Online resize of ext3 feels too hot for me to use in production systems, but that does also apply to reiserfs in general. with kind regards, Carsten -- Carsten Otte has stopped smoking: Ich habe in 3 Monate, 4 Tage und 10 Minuten schon 460,83 Euro gespart anstatt 1.920,15 Zigaretten zu kaufen. -- 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 If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: [OT] I WANT A PONY
You might want to keep in mind a scene from the movie "Dogma": Jay: Guys like us just don't fall out of the **cking sky, you know. [Rufus falls out of the sky] Jay: Beautiful, naked, big-titted women just don't fall out of the sky, you know. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Adam Thornton > Sent: Friday, July 07, 2006 12:03 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] [OT] I WANT A PONY > > > On Jul 7, 2006, at 6:20 AM, James Melin wrote: > > > Adam, just be glad you don't say stuff like "I want a sperm whale" > > or "I want a rabid pack of hyenas" > > Well, that would be pretty *cool* > > Adam > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Unexpectedly closing VM console breaks Linux server under z/VM
I went back and rechecked, and while the console showed CP read, the guest actually did continue to run. I made a minor, but stupid, mistake when I first tested it. CP SET RUN ON seems to be behaving exactly as the manual says it should. Still doesn't explain why the other guy is having trouble and we're not, except I don't think he mentioned how his terminal was attached. Mine is in through TN3270 direct, with no VTAM. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Post, Mark K > Sent: Thursday, June 29, 2006 2:28 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Unexpectedly closing VM console breaks Linux > server under z/VM > > > If the guest entered CP READ when you reconnected, you are > _not_ setting > RUN ON as you should. If for any reason your guest gets put into CP > READ, after (the default) 15 minutes, CP will force it off. > Try killing > your 3270 emulator after reconnecting, seeing CP READ, and waiting 15 > minutes. I think you'll find out the guest "goes away." > > > Mark Post > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Hall, Ken (GTI) > Sent: Thursday, June 29, 2006 1:34 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Unexpectedly closing VM console breaks Linux server under > z/VM > > I wonder what we're doing differently. I just tried this with my test > server several times, and it disconnected properly each time, leaving > the guest running. > > When I logged back ON though, the session went to CP READ and > the server > was partly locked up until I satisfied the read. > > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Unexpectedly closing VM console breaks Linux server under z/VM
I wonder what we're doing differently. I just tried this with my test server several times, and it disconnected properly each time, leaving the guest running. When I logged back ON though, the session went to CP READ and the server was partly locked up until I satisfied the read. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > James Melin > Sent: Thursday, June 29, 2006 1:26 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Unexpectedly closing VM console breaks Linux > server under z/VM > > > We ran into that here. SET RUN ON is specified in the profile > exec for all of the Linux guests, but if the 3270 session for > that guest (we would use > 3270 to manually IPL - otherwise xautolog is the choice) is > terminated (computer crashes, or someone closes the 3270 > program) without a #CP DISC the > session would go into a state other than disconnected and VM > would treat it as a 'dangling' session and kill it after a > period of time. This is > primarily aimed at situations where several hundred VM users > could be logged on and any number of them would leave a > session dangling and lock up the > resources for that user. It has dramatic and usually bad > consequences for ID's that are running guest operating > systems in the VM environment. > > The bottom line: DO NOT leave a 3270 session representing the > console of a Linux Guest just sitting someplace. Any variety > of scenarios can lead to a > 3270 session going into an abnormal state and VM will > diligently clean those up. Use #CP DISC when you're done if > you MUST access things by 3270. > Otherwise telnet/SSH is your better option for guest interaction. > > > > > "Post, Mark K" <[EMAIL PROTECTED]> > Sent by: Linux on 390 Port > > >To > >LINUX-390@VM.MARIST.EDU > > >cc > 06/29/2006 12:01 PM > > > Subject > >Re: Unexpectedly closing VM console breaks Linux > server under z/VM > Please respond to >Linux on 390 Port > > > > > > > > > Since you say you have "set run on" I admit to being puzzled. I would > have expected that to work for you. Perhaps someone from the VM > development team can say whether dropped connections are handled > differently from CP disconnects or not. > > > Mark Post > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Jack Hoarau > Sent: Thursday, June 29, 2006 11:24 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Unexpectedly closing VM console breaks Linux server > under z/VM > > -snip- > CP Q SET shows RUN set to ON but it > seems this is not to sufficient, am I missing some other important > function > settings of the guest ? > > Jack HOARAU > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Unexpectedly closing VM console breaks Linux server under z/VM
Maybe if there's no network, like you forgot to change the IP address before moving the machine to a different subnet. I've recovered quite a few unreachable machines using the 3270 console. It just requires some familiarity with line-mode commands. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Mark D Pace > Sent: Thursday, June 29, 2006 11:38 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Unexpectedly closing VM console breaks Linux > server under z/VM > > > Not to make light of your point, but doing anything from the > VM console of > a Linux guest is next to impossible anyway. Why would you do > this instead > of using a telnet/ssh client? > > > > Mark D Pace > Senior Systems Engineer > Mainline Information Systems > 1700 Summit Lake Drive > Tallahassee, FL. 32317 > Office: 850.219.5184 > Fax: 888.221.9862 > http://www.mainline.com > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Unexpectedly closing VM console breaks Linux server under z/VM
Make sure you have "CP SET RUN ON" in the PROFILE EXEC for the machine. Sounds to me like it's going into CP READ when it disconnects. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Rich Smrcina > Sent: Thursday, June 29, 2006 11:30 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Unexpectedly closing VM console breaks Linux > server under z/VM > > > What administration tasks required that he log on using the 3270 > interface? I rarely use it and only in the case that there is some > problem bring up Linux. > > Jack Hoarau wrote: > > Below is what I experienced considering that the described > behavior can > > have harmful consequences: > > Let's figure a Linux server is running under z/VM to serve network > > connectivity (gateway firewalling, etc...) to a colony of > Linux's. The > > system administrator log-on in the running server from the > VM console, to > > do some administration tasks, completes the tasks but the > VM console (pcom > > or x3270) drops unexpectedly (network connection lost, 3270 emulator > > closed) before he enters log-off or disconnect. From a VM > point of view One > > would consider the Linux guest still up but just > disconnected and walk > > away: Wrong ! in reality It is suspended...not > running...not serving... > > frozen. After a while z/VM just force the guest > definitively off breaking > > the linux network server. > > I suppose this is a normal behavior of z/VM to suspend > dispatching the > > guest due to the console I/O error. Do you think this is > compatible with > > running Linux under z/VM? Does anyone has this kind of > concern when using > > the console with Linux under z/VM ? CP Q SET shows RUN set > to ON but it > > seems this is not to sufficient, am I missing some other > important function > > settings of the guest ? > > > > Jack HOARAU > > > ** > * > > IBM System z New Technology Center > > IBM France Dpt. 1445 > > Products and Solutions Support Center > > Parc Industriel de la Pompignane, rue de la vieille Poste > >34055 Montpellier cedex 1 > > Tel: 04 67 34 4507 (+33 4 67 34 4507)Ext: : 38-4507 > > Fax: 04 67 34 6475 (+33 4 67 34 6475) > > > > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Changeing system name and IP address
Red Hat (RHEL4) is simple, compared to SLES. I think there are only two or three files involved, compared to like 6 or 7 on SLES. We did this quite a bit because of the way we cloned systems, and Yast wasn't an option because all we had after the clone was the 3270 console. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Robinson, Jim (robinsjo) > Sent: Wednesday, May 17, 2006 10:49 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Changeing system name and IP address > > > Not very elegant, but "grep -r /etc" and > "grep -r system name> /etc" should give you all the files that would need to be > modified. Brute force, but it works well on the Red Hat > distros I run. > > Jim Robinson > University of Cincinnati > 513-556-0013 > [EMAIL PROTECTED] > > > > -Original Message- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > > Behalf Of Mike Lovins > > Sent: Wednesday, May 17, 2006 10:22 AM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Changeing system name and IP address > > > > Can some give me the directions on the proper steps to change > > the system name and the IP address of my test Linux system > > that is going to replace a current system I am shutting down. > > I need to use the same system name and IP address because of > > the TSM application that I have. > > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Changeing system name and IP address
For SLES9, don't forget /etc/hosts, and if your subnet changed, /etc/sysconfig/network/routes. There may also be a host name in /etc/inews_mail_gateway. If you're using Postfix for mail, /etc/postfix/main.cf. You might also have to delete ssh keys in /etc/ssh. Basically, delete any file with the string "key" in the name. New versions of the keys don't seem to have the host name though, so this might not be an issue. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Gianfranco Ciotti > Sent: Wednesday, May 17, 2006 10:31 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Changeing system name and IP address > > > Mike Lovins wrote: > > Can some give me the directions on the proper steps to > change the system > > name and the IP address of my test Linux system that is > going to replace > > a current system I am shutting down. I need to use the same > system name > > and IP address because of the TSM application that I have. > > Your Linux distro (SuSE, RH, Debian, Slack...)? > > Anyway, in general, edit files: > > /etc/HOSTNAME > or > /etc/hostname > > /etc/sysconfig/network/ifcfg- > or > /etc/network/ifcfg- > > by, > > -- > > Gian > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Changeing system name and IP address
Depends on which distro and version you're using. SLES7 is different from SLES8 and SLES9, and they're different from RHEL. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Mike Lovins > Sent: Wednesday, May 17, 2006 10:22 AM > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] Changeing system name and IP address > > > Can some give me the directions on the proper steps to change > the system > name and the IP address of my test Linux system that is going > to replace > a current system I am shutting down. I need to use the same > system name > and IP address because of the TSM application that I have. > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Is it possible to move an LVM from guest to guest?
Oh, yeah... It is there. Doesn't seem to be a man page for it, but it does have internal help: Usage: chccwdev [] -e|--online Tries to set the given device online. -f|--forceonline Tries to force a device online if the device driver supports this. -d|--offline Tries to set the given device offline. [-][,[-]] ... The bus ID is the "0.0.0100" that I mentioned below. This does seem to be a simpler solution. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Richard Hitt > Sent: Thursday, May 11, 2006 3:13 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Is it possible to move an LVM from guest to > guest? > > > It's chccwdev, not cchccwdev. Change CCW-based Device, named I guess > along the model of other commands chmod, chroot, .... > > Richard Hitt[EMAIL PROTECTED] > > Hall, Ken (GTI) wrote: > > >Assuming cchccwdev is a program, Red Hat doesn't have it, so > here's the "manual" procedure, which should work on any > distro with a 2.6 kernel. > > > >If the device is 0100, for example, then you should have a directory: > > > >/sys/bus/ccw/devices/0.0.0100/ > > > >that contains: > > > >availability cmb_enable detach_state discipline readonly > >block cutype devtype online use_diag > > > >if you cat the file "online", and the device is actually > online, it will return a "1". > > > >To put the device offline: > > > >echo 0 > online > > > >Then you can safely detach it via VM. > > > >On the target system, the subdirectory "0.0.0100" won't > appear until you attach or link device 0100 via VM. Once > that's done, you echo a "1" to the "online" file to bring it on. > > > >Note that this is INDEPENDENT of the device string you pass > the module in modprobe.conf. Those are devices brought > online AUTOMATICALLY. Using this manual method, you can > bring ANY DASD device online that is linked or attached to > the guest. We use this scheme to temporarily bring the CMS > 191 disk online during boot to copy off configuration files. > > > >Piece of cake! > > > > > > > >>-Original Message- > >>From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > >>Ranga Nathan > >>Sent: Wednesday, May 10, 2006 4:58 PM > >>To: LINUX-390@VM.MARIST.EDU > >>Subject: Re: [LINUX-390] Is it possible to move an LVM from guest to > >>guest? > >> > >> > >> > >> > >>Hall, Ken (GTI) wrote: > >> > >> > >>>Unmount the filesystem, and run "vgexport" for the volume group. > >>> > >>> > >>Great. > >> > >> > >>>Then take the volume offline via sysfs > >>> > >>> > >>You mean cchccwdev -d /dev/ ? > >>sysfs manpage refers to /proc/filesystems which lists used > >>file systems. > >> > >> > >> > >>>, and detach it from the guest (This assumes you're on the > >>> > >>> > >>2.6 kernel. With 2.4 it's a little more complicated). > >> > >> > >>on 2.6. Good to go! > >> > >> > >>>Repeat the process in reverse on the other system, doing a > >>> > >>> > >>vgimport on the other side. > >>Cool. > >> > >> > >>> I'm reasonably sure I've done this successfully. > >>> > >>>It's much easier to set up an NFS share though, and leave > >>> > >>> > >>the volume attached to one guest. > >> > >> > >>Agreed, NFS would be helpful, but when you have to do repairs > >>in single > >>user mode, it is good to mount the LVM in the sick guest > >>sometimes and > >>do the repair, although most likely I will mount the sick > volume on a > >>good guest. You got me thinking. > >>Thanks a bunch. > >> > >> > >>>>-Original Message- > >>>>From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > >>>> > >>>> > >>Behalf Of > >> > >> > >>>>Ranga Nathan > >>>>Sent: Wednesday, May 10, 2006 2:52 PM > >>>>To: LINUX-390@VM.MARIST.EDU > >>>>Subject: [LINUX
Re: Is it possible to move an LVM from guest to guest?
Assuming cchccwdev is a program, Red Hat doesn't have it, so here's the "manual" procedure, which should work on any distro with a 2.6 kernel. If the device is 0100, for example, then you should have a directory: /sys/bus/ccw/devices/0.0.0100/ that contains: availability cmb_enable detach_state discipline readonly block cutype devtype online use_diag if you cat the file "online", and the device is actually online, it will return a "1". To put the device offline: echo 0 > online Then you can safely detach it via VM. On the target system, the subdirectory "0.0.0100" won't appear until you attach or link device 0100 via VM. Once that's done, you echo a "1" to the "online" file to bring it on. Note that this is INDEPENDENT of the device string you pass the module in modprobe.conf. Those are devices brought online AUTOMATICALLY. Using this manual method, you can bring ANY DASD device online that is linked or attached to the guest. We use this scheme to temporarily bring the CMS 191 disk online during boot to copy off configuration files. Piece of cake! > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Ranga Nathan > Sent: Wednesday, May 10, 2006 4:58 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Is it possible to move an LVM from guest to > guest? > > > > > Hall, Ken (GTI) wrote: > > Unmount the filesystem, and run "vgexport" for the volume group. > Great. > > Then take the volume offline via sysfs > > You mean cchccwdev -d /dev/ ? > sysfs manpage refers to /proc/filesystems which lists used > file systems. > > > , and detach it from the guest (This assumes you're on the > 2.6 kernel. With 2.4 it's a little more complicated). > > > on 2.6. Good to go! > > Repeat the process in reverse on the other system, doing a > vgimport on the other side. > Cool. > > I'm reasonably sure I've done this successfully. > > > > It's much easier to set up an NFS share though, and leave > the volume attached to one guest. > > > Agreed, NFS would be helpful, but when you have to do repairs > in single > user mode, it is good to mount the LVM in the sick guest > sometimes and > do the repair, although most likely I will mount the sick volume on a > good guest. You got me thinking. > Thanks a bunch. > > > >> -Original Message- > >> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > Behalf Of > >> Ranga Nathan > >> Sent: Wednesday, May 10, 2006 2:52 PM > >> To: LINUX-390@VM.MARIST.EDU > >> Subject: [LINUX-390] Is it possible to move an LVM from guest > >> to guest? > >> > >> > >> I want to set up an LVM that I can move from guest to > guest. I have a > >> 3390-09 volume that I want to use for this. > >> Why? It makes it easy to re-do file systems, at least for now. > >> I have LVM running on a couple of guests but I dont know if it is > >> possible to move this 'utility' LVM from guest to guest > >> easily *without* > >> any outage to the guests. > >> Thanks > >> > >> -- > >> __ > >> Ranga Nathan > >> Work: 714-442-7591 > >> If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Is it possible to move an LVM from guest to guest?
Unmount the filesystem, and run "vgexport" for the volume group. Then take the volume offline via sysfs, and detach it from the guest (This assumes you're on the 2.6 kernel. With 2.4 it's a little more complicated). Repeat the process in reverse on the other system, doing a vgimport on the other side. I'm reasonably sure I've done this successfully. It's much easier to set up an NFS share though, and leave the volume attached to one guest. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Ranga Nathan > Sent: Wednesday, May 10, 2006 2:52 PM > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] Is it possible to move an LVM from guest > to guest? > > > I want to set up an LVM that I can move from guest to guest. I have a > 3390-09 volume that I want to use for this. > Why? It makes it easy to re-do file systems, at least for now. > I have LVM running on a couple of guests but I dont know if it is > possible to move this 'utility' LVM from guest to guest > easily *without* > any outage to the guests. > Thanks > > -- > __ > Ranga Nathan > Work: 714-442-7591 > > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: What file system type to use for LVM ?
Mount options NOATIME and NODIRATIME But I don't see those on the current Reiser doc pages. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Phil Tully > Sent: Thursday, April 27, 2006 1:28 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] What file system type to use for LVM ? > > > David Boyes wrote > > In a earlier life I had implemented Reiserfs for a series > large (200Gb > ) samba filesystems. We experienced significant problems at the peak > access times (9am and 4pm) after many months of hair pulling we found > the culprit. The last referenced field was being updated and locked, > with the lock being held much longer than expected. > > There is an option to turn off updating the last referenced > field but I > can't find my notes from 3 years ago.. When this was resolved we > acheived up to very reasonable response time with hundreds of > concurrent > users. > > Now to find that setting > > Phil > > >>Just trying to gauge which is the more popular filesystem > type to use > >> > >> > >for > > > > > >>logical volumes, reiserfs or ext3 and why. > >> > >> > > > >Reiserfs is more popular, because it is the default in SuSE. We've > >observed a fair number of cases where reiserfs fails at very high I/O > >rates, so we tend to use ext3 in places where we know it's > going to get > >beaten hard. reiserfs performs slightly better than ext3 on > filesystems > >that will have a lot of small files (that's its design point > anyway) so > >you may need to mix and match. > > > > > > > >>Seems like reiserfs will allow resizing through the YaST GUI, whilst > >> > >> > >ext3 > > > > > >>filesystems forces CLI interaction. > >> > >> > > > >Install EVMS and use evmsn in place of the YaST storage gui. Then you > >get a nice front end for both, and a whole lot more. > > > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: SuSE 2.2.16 kernel to test
Pre-SLES8 systems used /etc/rc.config to configure everything except routing information. The three files you need to update are: /etc/rc.config /etc/route.conf /etc/hosts There are a couple of others that have to change if the host name changes, but if only the IP address and gateway are changing, these are the ones. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Loren Charnley, Jr. > Sent: Wednesday, April 19, 2006 1:00 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] SuSE 2.2.16 kernel to test > > > To the best of my knowledge it is SLES 7. It was installed > so long ago that > I can't remember. Any help will be gratefully received! > > Loren Charnley, Jr. > IT Systems Engineer > Family Dollar Stores, Inc. > [EMAIL PROTECTED] > (704) 847-6961 x 2000 > > -Original Message- > From: Hall, Ken (GTI) [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 19, 2006 12:42 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: SuSE 2.2.16 kernel to test > > Is this SLES7? I wrote a script way-back-when that handles > this, but it's > customized for our configuration. At least I can identify the files > involved though. > > > -Original Message- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > > Loren Charnley, Jr. > > Sent: Wednesday, April 19, 2006 12:34 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: [LINUX-390] SuSE 2.2.16 kernel to test > > > > > > All, > > > > > > > > My LINUX guru is in training all week and I need to get some > > things done > > before Thursday at noon. I need to move an OLD version of > > SuSE LINUX to a > > new CPU to use for a couple of months. The version of LINUX > > is 2.2.16 and I > > need to be able to boot this instance in single user mode and > > be able to > > edit all the files that need to be changed in order to bring > > this instance > > up with a new IP address. > > > > > > > > So far I have DDR'd the 3390 volumes to tape and restored to > > the new system. > > I have done some research and I think that I can boot in > > single user mode by > > using the LIPL EXEC on the 'A' disk. I have also found 2 > > files that I think > > will need to be changed, "/etc/rc.config and /etc/hosts", I > > think that there > > are probably more files involved and need a little direction > > on this. I will > > be in single user mode from a 3270 session and therefore will > > not be able to > > use "vi" as the editor. I think that I could use "sed" but I > > don't know the > > commands. If I could get the directions to a book or manuals > > that would > > really help. > > > > > > > > I have gotten myself into a bit of a jam and I am hoping > that there is > > someone out there that will be willing to help me out of this mess! > > > > > > > > TIA, > > > > Loren Charnley, Jr. > > IT Systems Engineer > > Family Dollar Stores, Inc. > > [EMAIL PROTECTED] > > (704) 847-6961 x 2000 > > > > > > > > > > > -- > > 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 > > > > > If you are not an intended recipient of this e-mail, please notify the > sender, delete it and do not read, act upon, print, disclose, > copy, retain > or redistribute it. Click here for important additional terms > relating to > this e-mail. http://www.ml.com/email_terms/ > > > -- > 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 > > - > NOTE: > This e-mail message contains PRIVILEGED and CONFIDENTIAL > information and is intended only for the use of the specific > individual or individuals to which it is addressed. If you are not > an intended recipient of this e-mail, you are hereby notified that > any unauthorized use, dissemination or copying of this e-mail or > t
Re: SuSE 2.2.16 kernel to test
Is this SLES7? I wrote a script way-back-when that handles this, but it's customized for our configuration. At least I can identify the files involved though. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Loren Charnley, Jr. > Sent: Wednesday, April 19, 2006 12:34 PM > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] SuSE 2.2.16 kernel to test > > > All, > > > > My LINUX guru is in training all week and I need to get some > things done > before Thursday at noon. I need to move an OLD version of > SuSE LINUX to a > new CPU to use for a couple of months. The version of LINUX > is 2.2.16 and I > need to be able to boot this instance in single user mode and > be able to > edit all the files that need to be changed in order to bring > this instance > up with a new IP address. > > > > So far I have DDR'd the 3390 volumes to tape and restored to > the new system. > I have done some research and I think that I can boot in > single user mode by > using the LIPL EXEC on the 'A' disk. I have also found 2 > files that I think > will need to be changed, "/etc/rc.config and /etc/hosts", I > think that there > are probably more files involved and need a little direction > on this. I will > be in single user mode from a 3270 session and therefore will > not be able to > use "vi" as the editor. I think that I could use "sed" but I > don't know the > commands. If I could get the directions to a book or manuals > that would > really help. > > > > I have gotten myself into a bit of a jam and I am hoping that there is > someone out there that will be willing to help me out of this mess! > > > > TIA, > > Loren Charnley, Jr. > IT Systems Engineer > Family Dollar Stores, Inc. > [EMAIL PROTECTED] > (704) 847-6961 x 2000 > > > > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Fw: [LINUX-390] GPFS
Could be. When we first looked at Levanta, back in the 03-04 time frame, I was very curious about how they did what they claimed. I'd never heard of UnionFS, and they told me that's what their product was based on: UnionFS mounts over NFS. I don't know what they're doing now, but last we spoke with them, they had pretty thoroughly overhauled their product as part of moving it into the Lin-Tel world. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > Behalf Of Rob > van der Heij > Sent: Wednesday, April 12, 2006 2:18 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Fw: [LINUX-390] GPFS > > > On 4/12/06, Hall, Ken (GTI) <[EMAIL PROTECTED]> wrote: > > > IIRC, UnionFS was part of the core of the Levanta "virtual > server" product, when we looked at it in 2003-2004. The idea > was that you installed each product group in a separate > filesystem, and then layered them onto each other to produce > custom-tailored images. Obviously, they had it working on > s390 back then, as a bundled product at least. > > From what I know, Levanta have their 'mapfs' that was made GPL half a > year ago or so. I don't think I ever looked in detail at it. > > -- > Rob van der Heij > Velocity Software, Inc > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Fw: [LINUX-390] GPFS
IIRC, UnionFS was part of the core of the Levanta "virtual server" product, when we looked at it in 2003-2004. The idea was that you installed each product group in a separate filesystem, and then layered them onto each other to produce custom-tailored images. Obviously, they had it working on s390 back then, as a bundled product at least. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > Behalf Of Rob > van der Heij > Sent: Wednesday, April 12, 2006 12:10 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Fw: [LINUX-390] GPFS > > > On 4/12/06, John Campbell <[EMAIL PROTECTED]> wrote: > > > I'm curious over how available the UnionFS (made famous or > infamous by > > Knoppix) would be? > > I started working with unionfs some time ago and it is pretty cool. > There was an error in one of the macros in the s390 kernel source, but > I believe that has been repaired properly by our friends in > Boeblingen. > > In fact, I used it for my latest project to run 100 Linux servers on > the P/390. I used unionfs to provide me with a private r/w layer as > well as a system-specific configuration layer in R/O, very neat. But > it turned out that on this slow CPU the extra overhead was making a > huge difference for me, so much that I had to give up using it. > > Will send Mark the PDF for the presentation... > > -- > Rob van der Heij > Velocity Software, Inc > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Checking with the experts...
FTP clients and servers are supposed to handle this transparently. If you send in ASCII or "text" mode, the proper end-of-line protocol should be automatically used on the receiving system. In binary mode, of course, you're on your own. RPM packages should obviously always be sent in binary mode. I don't think the install transfers any files that need to be sent in ASCII mode (although I could be wrong). More likely, the problem with the install is the same as it is for Windows-based ftp servers: Inconsistent file name case mangling. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > Behalf Of Tim > Hare > Sent: Monday, April 03, 2006 2:52 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Checking with the experts... > > > Well, that may have just shot down my last guess about why > z/OS USS wasn't > working as the FTP server for SuSe install. On to plan B or C... > > Tim Hare > Senior Systems Programmer > Florida Department of Transportation > (850) 414-4209 > > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Setting Hostname in SuSE Linux image on VM
Just a suspicion, but I think Bernard may be thinking of /proc/sys/kernel/hostname, which does show zero length, but when displayed, contains the host name. I think Ryan (and I) were looking at the program /bin/hostname, which on my machine is 15464 bytes. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Ryan Stewart > Sent: Thursday, March 30, 2006 4:08 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Setting Hostname in SuSE Linux image on VM > > > It was empty, but when I updated the package in YaST it became full. > Also, in my other image it has something in it. > > Ryan > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Bernard Wu > Sent: Thursday, March 30, 2006 3:59 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Setting Hostname in SuSE Linux image on VM > > Hi Ryan, > Are you sure it's empty. Mine shows 0 bytes, but when I do a "cat > hostname" , the correct hostname shows up. > > Bernie Wu > [EMAIL PROTECTED] > > > > > Ryan Stewart > <[EMAIL PROTECTED] > u> > To > Sent by: Linux on > 390 Port > cc > <[EMAIL PROTECTED] > IST.EDU> > Subject >Setting Hostname in SuSE Linux >image on VM > 03/30/2006 12:24 > PM > > > Please respond to > Linux on 390 Port > <[EMAIL PROTECTED] > IST.EDU> > > > > > > > Hi all, > > Does anyone know the proper way to set the hostname in SuSE. I had a > problem recently with the modprobe utility. I was conversing with > Novell about the issue via email and after spending some time on the > problem (since this was just a test image), I was going to > reinstall. I > played with it a little longer and figured out when I > compared the file > /sbin/modprobe to the same file on another image, they were different. > So I copied the file from the good image to the bad one. Everything > works (or so it seems to so far), but at my prompt I have a > hostname of > (none). > > For some reason I cannot set the hostname using the hostname command > either. I have added it to the /etc/hosts file. The hostname is > correct in the /etc/HOSTNAME file. One thing I noticed is in the > /proc/sys/kernel/hostname file it says (none) for the hostname. > > I am not sure what else to check or change. Anyone have any > thoughts on > the issue? > > Thanks, > > Ryan Stewart > Indian River Community College > [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 > > > > > The information contained in this e-mail message is intended only for > the personal and confidential use of the recipient(s) named > above. This > message may be an attorney-client communication and/or work > product and > as such is privileged and confidential. If the reader of this > message is > not the intended recipient or an agent responsible for > delivering it to > the intended recipient, you are hereby notified that you have received > this document in error and that any review, dissemination, > distribution, > or copying of this message is strictly prohibited. If you > have received > this communication in error, please notify us immediately by > e-mail, and > delete the original message. > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Setting Hostname in SuSE Linux image on VM
Either copy the file from the other image and run rpm --verify to check it, or re-install the rpm (rpm --install --force). You might want to list the contents of the RPM (rpm -ql) and make sure nothing else has been changed before you do that (although rpm --verify will tell you that too). > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Ryan Stewart > Sent: Thursday, March 30, 2006 2:16 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Setting Hostname in SuSE Linux image on VM > > > Ken, > > I think you hit on it. For some reason my /bin/hostname file is > completely empty. In another image it looks like a binary file. > > Any idea how to rebuild it? > > Thanks, > Ryan > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Hall, Ken (GTI) > Sent: Thursday, March 30, 2006 1:12 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Setting Hostname in SuSE Linux image on VM > > Try running "which hostname" to make sure you're picking up the right > program. On my Red Hat system, it's in /bin. (We used to > run Suse, so > I'm familiar with that too, I just don't have a sample Suse system > anymore.) > > Then run rpm -qf `which hostname` to find out which package it belongs > to. On Red Hat, it's net-tools. > > Then you can run "rpm --verify net-tools" (or whatever package you got > from the step above) to confirm that the files haven't been modified. > > Looks to me like you've got another program called "hostname" > out there > somewhere, since it's that program that sets the host name in the > kernel. > > I wrote my own scripts to configure instance-identity after cloning to > avoid using Yast, which was somewhat broken in early releases, and > couldn't be run from the VM console. There are only a few > places where > the host name is stored, and it looks like you've covered the two most > important. > > Just for reference, the files affected are: > > /etc/hosts > /etc/HOSTNAME > /etc/ssh/*key* (multiple files. Your best bet is to delete > these when > the host name changes.) /etc/postfix/main.cf > > > > -Original Message- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > Behalf Of > > Ryan Stewart > > Sent: Thursday, March 30, 2006 12:59 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: [LINUX-390] Setting Hostname in SuSE Linux image on VM > > > > > > Thanks Mike, that did work. I am still curious as to why I > had to do > > that when in my other images (that didn't have a problem) > there is no > > need to. > > > > Also, I get the hostname at the command prompt but when I use the > > hostname command, it returns nothing. > > > > Marcy, > > I did not run /sbin/SuSEconfig. I will now, but what exactly does > > that do? > > > > Thanks, > > > > Ryan > > > > -Original Message- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of > > Michael Krysiak > > Sent: Thursday, March 30, 2006 12:34 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: Setting Hostname in SuSE Linux image on VM > > > > Try using sysctl. It will set the hostname value found in > > /proc/sys/kernel/hostname. > > > > # sysctl -w kernel.hostname=myhostname > > > > You can place the above command in /etc/init.d/boot.local > and it will > > be set on boot. > > > > Regards, > > Mike > > > > > > -- > > > > > > > > > Ryan Stewart <[EMAIL PROTECTED]> > > Sent by: Linux on 390 Port > > 03/30/2006 12:24 PM > > Please respond to > > Linux on 390 Port > > > > > > To > > LINUX-390@VM.MARIST.EDU > > cc > > > > Subject > > Setting Hostname in SuSE Linux image on VM > > > > > > > > > > > > > > Hi all, > > > > Does anyone know the proper way to set the hostname in > SuSE. I had a > > problem recently with the modprobe utility. I was conversing with > > Novell about the issue via email and after spending some > time on the > > problem (since this was just a test image), I was going to > reinstall. > > > I played with it a little longer and figured out when I > compared the > > file /sbin/modprobe to the same file on another image, they were > > diff
Re: Setting Hostname in SuSE Linux image on VM
Try running "which hostname" to make sure you're picking up the right program. On my Red Hat system, it's in /bin. (We used to run Suse, so I'm familiar with that too, I just don't have a sample Suse system anymore.) Then run rpm -qf `which hostname` to find out which package it belongs to. On Red Hat, it's net-tools. Then you can run "rpm --verify net-tools" (or whatever package you got from the step above) to confirm that the files haven't been modified. Looks to me like you've got another program called "hostname" out there somewhere, since it's that program that sets the host name in the kernel. I wrote my own scripts to configure instance-identity after cloning to avoid using Yast, which was somewhat broken in early releases, and couldn't be run from the VM console. There are only a few places where the host name is stored, and it looks like you've covered the two most important. Just for reference, the files affected are: /etc/hosts /etc/HOSTNAME /etc/ssh/*key* (multiple files. Your best bet is to delete these when the host name changes.) /etc/postfix/main.cf > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Ryan Stewart > Sent: Thursday, March 30, 2006 12:59 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Setting Hostname in SuSE Linux image on VM > > > Thanks Mike, that did work. I am still curious as to why I had to do > that when in my other images (that didn't have a problem) there is no > need to. > > Also, I get the hostname at the command prompt but when I use the > hostname command, it returns nothing. > > Marcy, > I did not run /sbin/SuSEconfig. I will now, but what exactly > does that > do? > > Thanks, > > Ryan > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Michael Krysiak > Sent: Thursday, March 30, 2006 12:34 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Setting Hostname in SuSE Linux image on VM > > Try using sysctl. It will set the hostname value found in > /proc/sys/kernel/hostname. > > # sysctl -w kernel.hostname=myhostname > > You can place the above command in /etc/init.d/boot.local and > it will be > set on boot. > > Regards, > Mike > > > -- > > > > Ryan Stewart <[EMAIL PROTECTED]> > Sent by: Linux on 390 Port > 03/30/2006 12:24 PM > Please respond to > Linux on 390 Port > > > To > LINUX-390@VM.MARIST.EDU > cc > > Subject > Setting Hostname in SuSE Linux image on VM > > > > > > > Hi all, > > Does anyone know the proper way to set the hostname in SuSE. I had a > problem recently with the modprobe utility. I was conversing with > Novell about the issue via email and after spending some time on the > problem (since this was just a test image), I was going to > reinstall. I > played with it a little longer and figured out when I > compared the file > /sbin/modprobe to the same file on another image, they were different. > So I copied the file from the good image to the bad one. Everything > works (or so it seems to so far), but at my prompt I have a > hostname of > (none). > > For some reason I cannot set the hostname using the hostname command > either. I have added it to the /etc/hosts file. The hostname is > correct in the /etc/HOSTNAME file. One thing I noticed is in the > /proc/sys/kernel/hostname file it says (none) for the hostname. > > I am not sure what else to check or change. Anyone have any > thoughts on > the issue? > > Thanks, > > Ryan Stewart > Indian River Community College > [EMAIL PROTECTED] > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Cannot read package from the installation media. Media error?
My guess would be you're using a Windows FTP server on your laptop, and this doesn't work. You either need to use an FTP server or NFS on Linux. The problem has to do with Windows being rather casual about case-sensitivity in file names. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > Behalf Of Tom > Shilson > Sent: Tuesday, February 21, 2006 6:24 PM > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] Cannot read package from the installation media. > Media error? > > > I am trying to install SLES 9 on zVM. I go through the boot > of the card > decks, get VNC running, format the disks, then I get the > panel with all the > options. Under "Software" is the subject message. > > I have tried to load from the CD in my laptop's CD Drive and > from a share > on my laptop. (I have copied all the CDs to the share.) Both > get the same > error. > > zVM is 64 bit and this is 64-bit Linux. Do I need to specify > a certain > folder? Any ideas? > > Thanks, > > tom > - - - - - - - - - - - - > Toto, I have a feeling we're not in the mainframe world any more. >_/) Tom Shilson > ~Unix Team / IT Server Services > Aloha Tel: 651-733-7591 tshilson at mmm dot com >Fax: 651-736-7689 > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Linux on Intel;
They even had one that was selling for $50, with a $50 rebate a couple of years ago. Made a dandy Christmas present. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Alan Altmark > Sent: Friday, February 10, 2006 2:23 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Linux on Intel; > > > On Friday, 02/10/2006 at 12:36 EST, David Andrews > <[EMAIL PROTECTED]> > wrote: > > Oh yes... Belkin. These are the people who sold a router that > > periodically hijacked your port 80 traffic and redirected > it to their > > own adservers. See: > > http://www.theregister.co.uk/2003/11/07/help_my_belkin_router/ > > > > "The router would grab a random HTTP connection every > > eight hours and redirect it to Belkin?s (push) advertised > > web page." > > > > Perhaps they make fine equipment. But I won't buy any. > > In the interest of full disclosure and fairness, that was more than 2 > years ago and Belkin responded a mere 4 days later, removing the > redirection. > http://www.theregister.co.uk/2003/11/11/belkin_disables_router _spamming_feature/ And you're right, Belkin makes fine routers. Alan If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Linux on Intel;
Just as an FYI on this topic, I bought some combo USB/Firewire cards at a local PC show a while back. They had no identifiable brand name that I can recall, but they came in blue boxes, and were fairly cheap ($15-$25). They DID NOT work. Using USB 2.0 with my iPod gave all sorts of errors. Firewire worked a little better, but not much. About half the time, Windows would tell me my iPod was corrupted and I should restore it to "factory settings". Yeah, right. When they did work, they were much slower than they should have been. I finally got a new motherboard with built-in USB 2.0 and Firewire and once I got the drivers settled, all of the problems went away. So stick with known brands for this. The cheap cards still seem to have problems. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Gregg C Levine > Sent: Friday, February 10, 2006 12:18 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Linux on Intel; > > > Hello from Gregg C Levine > Let's see The only brand I can think of, that is its available > practically everywhere is Belkin. They make excellent USB cards. > They've had a USB 2.0 one out for a while now in fact I had bought a > USB 1.1 card from them at the same time they brought out their USB 2.0 > one. Depending on how quickly you would need the thing, you can either > buy it directly. That is from their website, www.belkin.com or from > any Staples or other such distributor. Their site will give > suggestions. > --- > Gregg C Levine [EMAIL PROTECTED] > --- > "Remember the Force will be with you. Always." Obi-Wan Kenobi > > > -Original Message- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf > Of > > Clark, Douglas > > Sent: Friday, February 10, 2006 11:56 AM > > To: LINUX-390@VM.MARIST.EDU > > Subject: [LINUX-390] Linux on Intel; > > > > I have a dual boot Intel box running Windows 2000 sp 4 and SuSE > Linux > > Enterprise version 9.0. See the output of "uname -a" below. > > > > uname -a > > Linux tsglnux1 2.6.5-7.244-default #1 Mon Dec 12 18:32:25 UTC 2005 > i686 > > i686 i386 GNU/Linux > > > > This Linux box does not have USB 2.0 and I would like to add a PCI > card > > into the system which is supported by both Windows and Linux. I use > > this Intel box as my You server that I update my mainframe Linux > > environments. What I want to do is backup the internal hard drive > on > > the Intel box to an external USB hard drive but with the amount of > data > > the time it takes over USB 1.1 is over 28 hours! > > > > Does anyone have a USB 2.0 PCI card they would recommend running in > an > > Intel box that supported Linux? > > > > TIA > > > > Doug > > > > > -- > > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Redhat Linux 2.4.9 Hanging
I think we did report it at the time, but we were in the process of converting to SLES8 and the LVM bug was fixed in that release. Activation now fails (properly) for a given VG if all volumes in the VG aren't present. The first time I saw our /var LV double-mounted on /usr AND /var was a bit of a shock though. :) > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Carsten Otte > Sent: Thursday, November 03, 2005 11:32 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Redhat Linux 2.4.9 Hanging > > > Hall, Ken (GTI) wrote: > > the connect of the DASD would frequently just fail. This > combined with an LVM bug that caused the wrong disks to be > attached to a volume group if volumes were missing, and made > for some really "interesting" situations. > *ouch*. Is that still with latest Sles8? Did you consider > reporting it as PMR? > -- > > Carsten Otte > IBM Linux technology center > ARCH=s390 > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Redhat Linux 2.4.9 Hanging
This makes sense in both our and Peter's situation, since the hangs did appear to be during this phase. We actually saw two different symptoms: At later service levels (SLES8+), the hangs seemed to be more common, but on our earlier SLES7 machines, the connect of the DASD would frequently just fail. This combined with an LVM bug that caused the wrong disks to be attached to a volume group if volumes were missing, and made for some really "interesting" situations. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Carsten Otte > Sent: Thursday, November 03, 2005 11:10 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Redhat Linux 2.4.9 Hanging > > > Hall, Ken (GTI) wrote: > > We used to see behavior like this on our SLES8 systems, > when too many images were brought up at once. It seemed to > be related to contention for the disks because we'd reboot > the images independently and they'd come up fine, and never > seemed to hang on individual reboots. > > > > Try staggering the autologs (insert delays, etc.) at IPL time. > > > > Did anyone ever figure out what caused this? > My personal favorite candidate is our device discovery. > We issue a sense-id command on each subchannel, and we > wait for a response from the device for a given amount > of time. After the timeout, we continue startup with the > assumption that there is no such device. If we get a > response after the timeout has expired, we set the device > online, but that may be too late for devices that need > to be present for startup (rootfs and such). > -- > > Carsten Otte > IBM Linux technology center > ARCH=s390 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Redhat Linux 2.4.9 Hanging
We used to see behavior like this on our SLES8 systems, when too many images were brought up at once. It seemed to be related to contention for the disks because we'd reboot the images independently and they'd come up fine, and never seemed to hang on individual reboots. Try staggering the autologs (insert delays, etc.) at IPL time. Did anyone ever figure out what caused this? > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Peter Webb, Toronto Transit Commission > Sent: Thursday, November 03, 2005 10:43 AM > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] Redhat Linux 2.4.9 Hanging > > > I discovered this week that my three test Linux systems had > been hanging > during boot, apparently since October 3, since this is the last date I > can find on their disks, and we did our monthly IPL that day. I cannot > find anything to suggest why they are not working. I can boot > my install > system, mount the disks and look around, but all the boots > from October > 3 on do not appear to be writing any log files. > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: iSCSI
I tried a little, but the iSCSI driver package and the Linux kernel never quite seem to be at compatible levels. I believe I got it to compile, but couldn't get any farther. I haven't tried recently though. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Steve Gentry > Sent: Tuesday, October 04, 2005 11:59 AM > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] iSCSI > > > Has anyone messed with iSCSI on Linux on the mainframe? Any > comments or > suggestions? > The information I've found on the web seems to indicate that a) the > kernel needs to be changed/updated and b) iSCSI and Linux > are close but > not quite > ready for prime time. > Thanks, > Steve G. > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: LVM for system fs in production?
We used LVM for all filesystems except the root FS. Since the volume group "virtualization" is activated by the SYSVINIT scripts, /boot, /lib, /bin and /etc have to be on "native" disk. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] > Behalf Of Eli > Criffield > Sent: Tuesday, September 20, 2005 12:29 PM > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] LVM for system fs in production? > > > Is anyone using lvm for all there file systems safely. We currently > only use lvm for non-system file systems only, but have a test box > that uses lvm for every file system except /boot. > > The test box is working fine but i just wanted to check to see if > there is any reason to not use lvm for system file systems (/usr, > /var, /ect...) before i made a production box all lvm. > > > Also the same question about reiserfs? Does anyone use reiserfs? Is > there any reason not to use reiserfs? > > Eli > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Dasdfmt and other potential block sizes
In the "more than you wanted to know" department, I have sitting on my semi-junk pile an old Sony Optical disk drive that came off a Sun Sparcstation clone. It uses 600 mb. optical cartridges that only support a 1024 byte sector. It was originally supported by SunOS (the precursor to Solaris), but the drivers are long lost. Only one OS has been able to properly support it: SCO OpenServer. Needless to say, I don't use it anymore. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Fargusson.Alan > Sent: Monday, August 15, 2005 12:25 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Dasdfmt and other potential block sizes > > > Technically there are Inter-Record-Gaps. As far as I know > all SCSI and IDE disk are physically formatted in 512 byte > sectors (oddly enough so they will work with Windows, which > seems to have problems with anything other than 512 bytes). > In reality there is a header followed by a gap followed by > 512 bytes of data followed by another gap then next header. > In gory detail: each header and data block actually starts > with a sync mark to get the timing started, then the data or > header, then a block of ECC. All of this is hidden by the > SCSI or IDE controller (the one on the disk, not the one on the bus). > > I know this is probably more then you wanted to know, but I > use to work for a company that made disk controllers. > > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: Supporting zLinux
I had Nagios up for quite a while. It's not too bad once you understand it. I'd be happy to look at the drafts. > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > David Boyes > Sent: Friday, August 12, 2005 11:49 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Supporting zLinux > > > > Nagios, > > mon, and other such products are capable of producing e-mails > > to lists of support personnel. (In our case, we can use an > > e-mail to trigger a pager if we want.) > > Nagios works well for this, but it's a bear to configure. The > documentation > is really, really awful. The combination of Nagios and NRPE > agents is pretty > slick though. > > I'm still working on a Nagios book -- anyone interested in > being a early > guinea pig and reading drafts? > > -- > 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 > If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -- 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: SLES9 install stuff - more weirdness
In this case though, it's going to depend on how the installer is doing the
mounts. If it's issuing a separate mount for each CD image, unless the server
allows subdirectories to be mounted under a parent export, it's not going to
work. That's how I remember Linux working.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Uriel Carrasquilla
> Sent: Tuesday, August 09, 2005 1:30 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] SLES9 install stuff - more weirdness
>
>
> There are two type of NFS (don't remember the details). One
> of them allows
> for subdirectories to be mounted while a parent directory is
> also mounted.
> The other way around this problem is to create an LVM with all the
> directories you need. Then export the entire LVM.
>
> Regards,
>
> [EMAIL PROTECTED]
> NCCI
> Boca Raton, Florida
> 561.893.2415
> greetings / avec mes meilleures salutations / Cordialmente
> mit freundlichen Grüßen / Med vänlig hälsning
>
>
>
>
> James Melin
>
> <[EMAIL PROTECTED]To:
> LINUX-390@VM.MARIST.EDU
>
> epin.mn.us> cc:
>
> Sent by: Linux on Subject:
> SLES9 install stuff - more weirdness
>
> 390 Port
>
> <[EMAIL PROTECTED]
>
> ST.EDU>
>
>
>
>
>
> 08/09/2005 01:17
>
> PM
>
> Please respond to
>
> Linux on 390 Port
>
>
>
>
>
>
>
>
>
> I had gotten things to work NFS wise, the GUI installer was
> fine until It
> asked for CD2. Well there was no CD 2 in the
> /data/SLES9/sles9root/sles9/
> path, just CD1. That's also where I found the initrd,
> parmfile etc. So
> I dug around some and found /data/SLES9/sles9root/core9/CD1
> (CD1, etc etc)
>
> When I attempted to supply /data/SLES9/sles9root/core9/CD1 as
> the path for
> NFS, it complained that it was not the correct path.
>
> My NFS server on the installation server allowed me to NFS
> mount that path
> on another Linux, so that is OK. I know the NFS part is set
> up correctly.
>
> The path being exposed on NFS is:
> exportfs
> /data/SLES9/sles9root/core9
>
>
>
> So I tried FTP. When it appeared to accept the path and ask
> me if I wanted
> X-Window, VNC or SSH, I picked 2 as usual, and entered the
> password I use
> for an installation VNC server. What happened next is
> strange. Rather, what
> DIDN'T happen. I didn't get the message that VNC server
> started and to go
> to {ip address}:1 with a VNC client or go to {ipaddress}:5801 with a
> browser.
> Instead this is what the screen showed.
>
> 1) X-Window
> 2) VNC (VNC-Client or Java enabled Browser)
> 3) ssh
> Choice:2
> Please enter the Password for VNC-Access (6 to 8 characters):foobar
> ramdisk /dev/ram0 freed
> >>> SUSE LINUX Enterprise Server 9 installation program v1.6.36 (c)
> 1996-2004 SU
> SE LINUX AG <<<
> SCSI subsystem initialized
> st: Version 20040318, fixed bufsize 32768, s/g segs 256
> Starting hardware detection...
>
> Searching
> for
> info file...
> Main Menu
> 1) Settings
> 2) System Information
> 3) Kernel Modules (Hardware Drivers)
>
Re: SLES9 install stuff - more weirdness
Try exporting the individual subdirectories. I've run across this sort of NFS
weirdness before. You can only directly mount the exported directory, not the
ones under it.
I know someone is going to tell us it isn't supposed to work this way, but I've
been down this road before.
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> James Melin
> Sent: Tuesday, August 09, 2005 1:17 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: [LINUX-390] SLES9 install stuff - more weirdness
>
>
> I had gotten things to work NFS wise, the GUI installer was
> fine until It
> asked for CD2. Well there was no CD 2 in the
> /data/SLES9/sles9root/sles9/
> path, just CD1. That's also where I found the initrd,
> parmfile etc. So
> I dug around some and found /data/SLES9/sles9root/core9/CD1
> (CD1, etc etc)
>
> When I attempted to supply /data/SLES9/sles9root/core9/CD1 as
> the path for
> NFS, it complained that it was not the correct path.
>
> My NFS server on the installation server allowed me to NFS
> mount that path
> on another Linux, so that is OK. I know the NFS part is set
> up correctly.
>
> The path being exposed on NFS is:
> exportfs
> /data/SLES9/sles9root/core9
>
>
>
> So I tried FTP. When it appeared to accept the path and ask
> me if I wanted
> X-Window, VNC or SSH, I picked 2 as usual, and entered the
> password I use
> for an installation VNC server. What happened next is
> strange. Rather, what
> DIDN'T happen. I didn't get the message that VNC server
> started and to go
> to {ip address}:1 with a VNC client or go to {ipaddress}:5801 with a
> browser.
> Instead this is what the screen showed.
>
> 1) X-Window
> 2) VNC (VNC-Client or Java enabled Browser)
> 3) ssh
> Choice:2
> Please enter the Password for VNC-Access (6 to 8 characters):foobar
> ramdisk /dev/ram0 freed
> >>> SUSE LINUX Enterprise Server 9 installation program v1.6.36 (c)
> 1996-2004 SU
> SE LINUX AG <<<
> SCSI subsystem initialized
> st: Version 20040318, fixed bufsize 32768, s/g segs 256
> Starting hardware detection...
>
> Searching
> for
> info file...
> Main Menu
> 1) Settings
> 2) System Information
> 3) Kernel Modules (Hardware Drivers)
>
> MORE... ZVM3
>
>
> This has me flummoxed. NFS won't fly, and FTP won't
> 'continue' properly
> for VNC. Any ideas would be most highly appreciated.
>
> --
> 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
>
If you are not an intended recipient of this e-mail, please notify the sender,
delete it and do not read, act upon, print, disclose, copy, retain or
redistribute it. Click here for important additional terms relating to this
e-mail. http://www.ml.com/email_terms/
--
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
