Re: New redbook draft for Linux on zSeries
Hi! http://www.redbooks.ibm.com/redpieces/abstracts/sg246694.html I've read in this redbook: In kernel versions greater than 2.6.9, the I/O scheduler can be selected at runtime using the /sys/block/dev/queue/scheduler interface (where dev is the DASD device number). Is it possible to use different I/O scheduler for each dasd? István -- 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: New redbook draft for Linux on zSeries
-Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Istvan Nemeth Sent: Monday, October 03, 2005 08:21 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: New redbook draft for Linux on zSeries Hi! http://www.redbooks.ibm.com/redpieces/abstracts/sg246694.html I've read in this redbook: In kernel versions greater than 2.6.9, the I/O scheduler can be selected at runtime using the /sys/block/dev/queue/scheduler interface (where dev is the DASD device number). Is it possible to use different I/O scheduler for each dasd? István -- 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: SLES9, SP2 and zipl
Your initrd file is corrupted, possibly due to not having enough free space in /boot while applying maintenance. We ran into this, and received the same error message. Note that the install / maintenance process where the actual error occurs produces no error messages or codes, and will happily say that initrd was created successfully, even though the process failed miserably. If you can get a corrected initrd back on to /boot, you should be ok. At this point, being a pessimistic person, whenever I add maintenance that touches the kernel, I run mkinitrd and zipl afterward. -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844Rochester, MN 55905 - In theory, theory and practice are the same, but in practice, theory and practice are different. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Bates, Bob Sent: Friday, September 30, 2005 12:37 PM To: LINUX-390@VM.MARIST.EDU Subject: SLES9, SP2 and zipl Hello all, I have a SLES9 31-bit image I installed a short while back un zVM. I am now trying to put the SP2 pack on it using YaST. After I finished I rebooted and it would not come up correctly, it appeared to be looking for a file in the previous kernel level name. Remembering discussions regarding mksles9root and zipl I thought to look for those. I can't find mksles9root but did locate zipl and the zipl.conf. When I ran zipl the system would not boot. Got this error: RAMDISK: Compressed image found at block 0 RAMDISK: ran out of compressed data invalid compressed format (err=1) VFS: Cannot open root device dasda1 or unknown-block(0,0) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop I am trying to figure out what I did wrong, and where I can find more information about zipl.conf. I see the options but not an explanation of things on the parameter = card. Any help? Thanks Bob Bates Citigroup Technology Infrastructure 916-374-5017 -- 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: SLES9, SP2 and zipl
On Monday, 10/03/2005 at 08:06 EST, Nix, Robert P. [EMAIL PROTECTED] wrote: Your initrd file is corrupted, possibly due to not having enough free space in /boot while applying maintenance. We ran into this, and received the same error message. Note that the install / maintenance process where the actual error occurs produces no error messages or codes, and will happily say that initrd was created successfully, even though the process failed miserably. If you haven't done so, I encourage you to open a bugzilla or report it to your Linux support provider. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Getting an odd message when trying to NFS mount the sles9root tree
I have to make a new SLES9 installation server because I'm upgrading the current sles8 server I use for that to sles9. I get this message: vadnais:~ # mount -t nfs gsop23nnn09:/cd_images/SLES9/sles9root /sles9root nfs server reported tcp not available, falling back to udp Using NFS over UDP can cause data corruption. Does this mean something is scrozzled on the system I'm mounting it on, or something is scrozzled on the server where the sles9root exists. I am at a loss to explain why it is saying TCP is unavailable since I can access both of those images. -- 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: Getting an odd message when trying to NFS mount the sles9root tree
-Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of James Melin Sent: Monday, October 03, 2005 8:45 AM To: LINUX-390@VM.MARIST.EDU Subject: Getting an odd message when trying to NFS mount the sles9root tree I have to make a new SLES9 installation server because I'm upgrading the current sles8 server I use for that to sles9. I get this message: vadnais:~ # mount -t nfs gsop23nnn09:/cd_images/SLES9/sles9root /sles9root nfs server reported tcp not available, falling back to udp Using NFS over UDP can cause data corruption. Does this mean something is scrozzled on the system I'm mounting it on, or something is scrozzled on the server where the sles9root exists. I am at a loss to explain why it is saying TCP is unavailable since I can access both of those images. I get that message all the time, with no particular problems. Originally NFS only used UDP for communications. I guess there is now an option to allow NFS to use TCP transport as well. Your system is set up to use the new TCP communications method with fall back to UDP. So it is telling you about the fall back. I don't know how to tell the NFS server to use TCP as well as UDP. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- 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
MVMRUG Meeting Reminder
Just a reminder that it is time to get your reservations in to me if you plan to attend the MVMRUG meeting in Columbus, Ohio on October 28. I may be a bit biased, but I think we have another very good agenda. You can review it and register at http://www.mvmrug.org/nextmtg.html. Our host is very eager to get a catering count for breakfast and lunch. Terry - This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company / The Timken Corporation -- 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: Getting an odd message when trying to NFS mount the sles9root tree
On Oct 3, 2005, at 8:45 AM, James Melin wrote: I have to make a new SLES9 installation server because I'm upgrading the current sles8 server I use for that to sles9. I get this message: vadnais:~ # mount -t nfs gsop23nnn09:/cd_images/SLES9/sles9root / sles9root nfs server reported tcp not available, falling back to udp Using NFS over UDP can cause data corruption. Does this mean something is scrozzled on the system I'm mounting it on, or something is scrozzled on the server where the sles9root exists. I am at a loss to explain why it is saying TCP is unavailable since I can access both of those images. Probably the server is using a fairly old NFS server using only NFSv2, or very conservative compatibility settings, or some such. NFS-over-UDP was the only kind of NFS for a long long time. Check the settings for the NFS server on gsop23nnn09, and see what they are. The warning is probably harmless: lots of people used NFS over UDP just fine for many years, and only occasionally did th NFS server dogbreath not responding; still retrying... -- 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: Getting an odd message when trying to NFS mount the sles9root tree
I have to make a new SLES9 installation server because I'm upgrading the current sles8 server I use for that to sles9. I get this message: vadnais:~ # mount -t nfs gsop23nnn09:/cd_images/SLES9/sles9root /sles9root nfs server reported tcp not available, falling back to udp Using NFS over UDP can cause data corruption. Does this mean something is scrozzled on the system I'm mounting it on, or something is scrozzled on the server where the sles9root exists. I am at a loss to explain why it is saying TCP is unavailable since I can access both of those images. While TCP in general may be available, NFS over TCP may not be. It's a configuration option, and it sounds like whoever installed the NFS server allowed it to default to NFSv2 which spoke only UDP. Check your NFS server configuration and make sure NFSv3 is enabled. -- 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: Getting an odd message when trying to NFS mount the sles9root tree
This is a temporary situation and it's an old dusty/crusty linux installation that is getting replaced as soon as this temporary move of the SLES9 installation server is accomplished. David Boyes [EMAIL PROTECTED] e.net To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: Getting an odd message when trying to NFS mount the sles9root 10/03/2005 10:16 tree AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU I have to make a new SLES9 installation server because I'm upgrading the current sles8 server I use for that to sles9. I get this message: vadnais:~ # mount -t nfs gsop23nnn09:/cd_images/SLES9/sles9root /sles9root nfs server reported tcp not available, falling back to udp Using NFS over UDP can cause data corruption. Does this mean something is scrozzled on the system I'm mounting it on, or something is scrozzled on the server where the sles9root exists. I am at a loss to explain why it is saying TCP is unavailable since I can access both of those images. While TCP in general may be available, NFS over TCP may not be. It's a configuration option, and it sounds like whoever installed the NFS server allowed it to default to NFSv2 which spoke only UDP. Check your NFS server configuration and make sure NFSv3 is enabled. -- 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: Getting an odd message when trying to NFS mount ...
I see you've gotten several replies. But no one specifically addressed this part of the message you're getting: Using NFS over UDP can cause data corruption. I think it would be more accurate to say Using NFS over UDP with '-o soft' can cause data corruption. By default, the hard option is set for NFS mounts, so that even when using UDP, your risk of data corruption is greatly reduced. Hard NFS mounts have a problem on the other end of the spectrum: If the server from which you mounted that vol goes down, then your client is hung until it comes back. That is, rather than risk data corruption, you are more likely to get stuck depending on another host. THe soft option is a way around THIS problem, but leads to the potential for data corruption. Probably more info than you wanted. -- 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
NJE/IP Bridge Product Announcement
Product Announcement posting for NJE/IP Bridge Barnard Software, Inc. (BSI) is pleased to announce the general availability of NJE/IP Bridge. NJE/IP Bridge is developed by Sine Nomine Associates and marketed by BSI. NJE/IP Bridge allows you to interconnect NJE communication services on unmodified OS/390, VM, z/VM, z/OS, VSE, TPF and -- for the first time -- open systems (such as Windows, Linux, Solaris and AIX) over TCP/IP networks. NJE/IP Bridge incorporates a complete bi-directional NJE implementation for a large range of mainframe, midrange, and desktop computing environments, and supports integration of development environments, workstation applications, and system management tasks into a reliable, stable, completely IP-based environment that is transparent to end user awareness. 31-bit and 64-bit System/390 and zSeries systems (both standard engine and IFL) are supported along with most popular open systems platforms. Pricing for NJE/IP Bridge is machine-size neutral, and very affordable on any platform. NJE/IP Bridge provides an easy method for constructing system management automation for Linux guests within a z/VM environment as well as those with external hosts, routing system logging and messages to central Netview or VM Programmable Operator environments and dramatically simplifies and consolidates the number and type of monitoring systems needed to manage a diverse computing environment. For more information on NJE/IP Bridge, please go to: www.bsiopti.com and look over the NJE/IP Bridge technical fact sheet or go to the download page and download a trial version of NJE/IP Bridge. You can call BSI at 407-323-4773 or email us at [EMAIL PROTECTED] and we can discuss any questions you have in greater detail. About Barnard Software: Barnard Software, Inc. (BSI) is known in the VSE/ESA community for quality products and top-notch customer technical support. BSI has been in the mainframe software industry for 12 years. About Sine Nomine Associates: Sine Nomine Associates is a unique RD and engineering solutions provider with cross-platform strategic technology and business solution for customers worldwide. Additional information about Sine Nomine can be found at www.sinenomine.net. -- 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, SP2 and zipl
We have support through IBM. The ETR was closed and has fallen off my radar, but the gist of the response was make /boot bigger. They did say that they'd forward to Novell the fact that maintenance can fail without any error indication, but as the ETR was closed, we'll never know if this is addressed down the road... -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844Rochester, MN 55905 - In theory, theory and practice are the same, but in practice, theory and practice are different. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Monday, October 03, 2005 8:45 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES9, SP2 and zipl On Monday, 10/03/2005 at 08:06 EST, Nix, Robert P. [EMAIL PROTECTED] wrote: Your initrd file is corrupted, possibly due to not having enough free space in /boot while applying maintenance. We ran into this, and received the same error message. Note that the install / maintenance process where the actual error occurs produces no error messages or codes, and will happily say that initrd was created successfully, even though the process failed miserably. If you haven't done so, I encourage you to open a bugzilla or report it to your Linux support provider. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9, SP2 and zipl
Thanks again I ran mkinitrd and zipl and the system came up without a problem. I'll look into increasing /boot. Bob Bates -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Nix, Robert P. Sent: Monday, October 03, 2005 1:26 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES9, SP2 and zipl We have support through IBM. The ETR was closed and has fallen off my radar, but the gist of the response was make /boot bigger. They did say that they'd forward to Novell the fact that maintenance can fail without any error indication, but as the ETR was closed, we'll never know if this is addressed down the road... -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844Rochester, MN 55905 - In theory, theory and practice are the same, but in practice, theory and practice are different. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Monday, October 03, 2005 8:45 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES9, SP2 and zipl On Monday, 10/03/2005 at 08:06 EST, Nix, Robert P. [EMAIL PROTECTED] wrote: Your initrd file is corrupted, possibly due to not having enough free space in /boot while applying maintenance. We ran into this, and received the same error message. Note that the install / maintenance process where the actual error occurs produces no error messages or codes, and will happily say that initrd was created successfully, even though the process failed miserably. If you haven't done so, I encourage you to open a bugzilla or report it to your Linux support provider. Alan Altmark z/VM Development IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
