Linux not recognizing file systems
I've got a strange problem with a Linux guest. The only indicator we've come up with so far is that /dev/null had it's file permissions changed on Friday afternoon to -rw-r--r-- 1 root root 81 2008-01-11 15:03 /dev/null (we don't know how this was changed). One of our admins changed it back to 666, but it was still missing the character file attributes. Everything still worked fine, until it was rebooted on Sunday evening. Now, it comes up under VM, but the connections that allow us to putty to it aren't working. It's only mounting / and when I sign on as root and try to change null to a character file, it tells me the file system is read-only although the permissions for /dev are drwxr-xr-x. It's also not mounting /opt which is what is on /dev/system/lvm1. doing the mount command, we see this output. proc on /proc type proc (rw) (none):/ # mount -a mount -a mount: devpts already mounted or /dev/pts busy mount: /dev/system/lvm1 is not a valid block device We're in the process of trying to restore back to the last good full volume backup, but I'm really curious if changing /dev/null could have this strong of a impact and if there's any ideas of what we might be able to do to fix the problem without restoring. CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of 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
Re: Linux not recognizing file systems
Can you see the virtual machine register on your VSwitch (Q LAN DETAILS)? Can you ping it? Joell Chockley wrote: I've got a strange problem with a Linux guest. The only indicator we've come up with so far is that /dev/null had it's file permissions changed on Friday afternoon to -rw-r--r-- 1 root root 81 2008-01-11 15:03 /dev/null (we don't know how this was changed). One of our admins changed it back to 666, but it was still missing the character file attributes. Everything still worked fine, until it was rebooted on Sunday evening. Now, it comes up under VM, but the connections that allow us to putty to it aren't working. It's only mounting / and when I sign on as root and try to change null to a character file, it tells me the file system is read-only although the permissions for /dev are drwxr-xr-x. It's also not mounting /opt which is what is on /dev/system/lvm1. doing the mount command, we see this output. proc on /proc type proc (rw) (none):/ # mount -a mount -a mount: devpts already mounted or /dev/pts busy mount: /dev/system/lvm1 is not a valid block device We're in the process of trying to restore back to the last good full volume backup, but I'm really curious if changing /dev/null could have this strong of a impact and if there's any ideas of what we might be able to do to fix the problem without restoring. -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008 -- 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 not recognizing file systems
It does show up on the VSwitch, but you can't ping it. Rich Smrcina <[EMAIL PROTECTED] om>To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc <[EMAIL PROTECTED] IST.EDU>Topic Subject 01/14/2008 09:02 Re: Linux not recognizing file AMsystems Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> Can you see the virtual machine register on your VSwitch (Q LAN DETAILS)? Can you ping it? Joell Chockley wrote: > I've got a strange problem with a Linux guest. The only indicator we've > come up with so far is that /dev/null had it's file permissions changed on > Friday afternoon to -rw-r--r-- 1 root root 81 2008-01-11 15:03 /dev/null > (we don't know how this was changed). One of our admins changed it back to > 666, but it was still missing the character file attributes. Everything > still worked fine, until it was rebooted on Sunday evening. Now, it comes > up under VM, but the connections that allow us to putty to it aren't > working. It's only mounting / and when I sign on as root and try to change > null to a character file, it tells me the file system is read-only although > the permissions for /dev are drwxr-xr-x. It's also not mounting /opt which > is what is on /dev/system/lvm1. > > doing the mount command, we see this output. > > proc on /proc type proc (rw) > (none):/ # mount -a > mount -a > mount: devpts already mounted or /dev/pts busy > mount: /dev/system/lvm1 is not a valid block device > > We're in the process of trying to restore back to the last good full volume > backup, but I'm really curious if changing /dev/null could have this strong > of a impact and if there's any ideas of what we might be able to do to fix > the problem without restoring. -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008 -- 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 CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of 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
Re: Linux not recognizing file systems
Joell Chockley wrote: >I've got a strange problem with a Linux guest. The only indicator we've >come up with so far is that /dev/null had it's file permissions changed on >Friday afternoon to -rw-r--r-- 1 root root 81 2008-01-11 15:03 /dev/null >(we don't know how this was changed). One of our admins changed it back to >666, but it was still missing the character file attributes. Everything >still worked fine, until it was rebooted on Sunday evening. Now, it comes >up under VM, but the connections that allow us to putty to it aren't >working. It's only mounting / and when I sign on as root and try to change >null to a character file, it tells me the file system is read-only although >the permissions for /dev are drwxr-xr-x. It's also not mounting /opt which >is what is on /dev/system/lvm1. > >doing the mount command, we see this output. > >proc on /proc type proc (rw) >(none):/ # mount -a >mount -a >mount: devpts already mounted or /dev/pts busy >mount: /dev/system/lvm1 is not a valid block device > >We're in the process of trying to restore back to the last good full volume >backup, but I'm really curious if changing /dev/null could have this strong >of a impact and if there's any ideas of what we might be able to do to fix >the problem without restoring. Joell, Just taking a guess here. Is your system coming up in recovery mode? The fact that your file system is read only and you are having problems with mounts kind of points me in that direction. What distribution are you running? SUSE sles9? I am almost suspecting that someone made some changes to your dasd configuration then did not do a mkinitrd and zipl. Things would work just fine until you did a reboot. What are the messages you get when you do the reboot? Regards, John -- 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 not recognizing file systems
I concur with John. Check the messages log and dmesg. Something bigger is happening. I changed /dev/null on a virtual machine to the state that you had it in and yes, weird things happened, but as soon as I rebooted it, it changed back to exactly what it was before (as I would expect). This may also explain your connectivity problem. Joell Chockley wrote: It does show up on the VSwitch, but you can't ping it. Rich Smrcina <[EMAIL PROTECTED] om>To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc <[EMAIL PROTECTED] IST.EDU>Topic Subject 01/14/2008 09:02 Re: Linux not recognizing file AMsystems Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> Can you see the virtual machine register on your VSwitch (Q LAN DETAILS)? Can you ping it? Joell Chockley wrote: I've got a strange problem with a Linux guest. The only indicator we've come up with so far is that /dev/null had it's file permissions changed on Friday afternoon to -rw-r--r-- 1 root root 81 2008-01-11 15:03 /dev/null (we don't know how this was changed). One of our admins changed it back to 666, but it was still missing the character file attributes. Everything still worked fine, until it was rebooted on Sunday evening. Now, it comes up under VM, but the connections that allow us to putty to it aren't working. It's only mounting / and when I sign on as root and try to change null to a character file, it tells me the file system is read-only although the permissions for /dev are drwxr-xr-x. It's also not mounting /opt which is what is on /dev/system/lvm1. doing the mount command, we see this output. proc on /proc type proc (rw) (none):/ # mount -a mount -a mount: devpts already mounted or /dev/pts busy mount: /dev/system/lvm1 is not a valid block device We're in the process of trying to restore back to the last good full volume backup, but I'm really curious if changing /dev/null could have this strong of a impact and if there's any ideas of what we might be able to do to fix the problem without restoring. -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008 -- 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 CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of 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 -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008 -- 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 not recognizing file systems
This sounds like your /dev directory went bad. I don't know what version of Linux you are running. Does it use udev? Did udev fail to start? -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Joell Chockley Sent: Monday, January 14, 2008 6:54 AM To: LINUX-390@VM.MARIST.EDU Subject: Linux not recognizing file systems I've got a strange problem with a Linux guest. The only indicator we've come up with so far is that /dev/null had it's file permissions changed on Friday afternoon to -rw-r--r-- 1 root root 81 2008-01-11 15:03 /dev/null (we don't know how this was changed). One of our admins changed it back to 666, but it was still missing the character file attributes. Everything still worked fine, until it was rebooted on Sunday evening. Now, it comes up under VM, but the connections that allow us to putty to it aren't working. It's only mounting / and when I sign on as root and try to change null to a character file, it tells me the file system is read-only although the permissions for /dev are drwxr-xr-x. It's also not mounting /opt which is what is on /dev/system/lvm1. doing the mount command, we see this output. proc on /proc type proc (rw) (none):/ # mount -a mount -a mount: devpts already mounted or /dev/pts busy mount: /dev/system/lvm1 is not a valid block device We're in the process of trying to restore back to the last good full volume backup, but I'm really curious if changing /dev/null could have this strong of a impact and if there's any ideas of what we might be able to do to fix the problem without restoring. CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of 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
Re: Linux not recognizing file systems
Thanks for all the reply's... Not real sure how this could impact so much and why rebooting did not bring /dev/null back to its initial state, but once we got the file permissions set back to the character set for /dev/null, our other file system was able to mount and we had our /opt file structure back. I even rebooted a couple times to make sure it came back correctly and everything appears to be working fine now. Thanks! Rich Smrcina <[EMAIL PROTECTED] om>To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc <[EMAIL PROTECTED] IST.EDU>Topic Subject 01/14/2008 09:46 Re: Linux not recognizing file AMsystems Please respond to Linux on 390 Port <[EMAIL PROTECTED] IST.EDU> I concur with John. Check the messages log and dmesg. Something bigger is happening. I changed /dev/null on a virtual machine to the state that you had it in and yes, weird things happened, but as soon as I rebooted it, it changed back to exactly what it was before (as I would expect). This may also explain your connectivity problem. Joell Chockley wrote: > It does show up on the VSwitch, but you can't ping it. > > > > > Rich Smrcina > <[EMAIL PROTECTED] > om> To > Sent by: Linux on LINUX-390@VM.MARIST.EDU > 390 Port cc > <[EMAIL PROTECTED] > IST.EDU> Topic > > Subject > 01/14/2008 09:02 Re: Linux not recognizing file > AMsystems > > > Please respond to > Linux on 390 Port > <[EMAIL PROTECTED] > IST.EDU> > > > > > > > Can you see the virtual machine register on your VSwitch (Q LAN > DETAILS)? Can you ping it? > > Joell Chockley wrote: >> I've got a strange problem with a Linux guest. The only indicator we've >> come up with so far is that /dev/null had it's file permissions changed > on >> Friday afternoon to -rw-r--r-- 1 root root 81 2008-01-11 15:03 /dev/null >> (we don't know how this was changed). One of our admins changed it back > to >> 666, but it was still missing the character file attributes. Everything >> still worked fine, until it was rebooted on Sunday evening. Now, it > comes >> up under VM, but the connections that allow us to putty to it aren't >> working. It's only mounting / and when I sign on as root and try to > change >> null to a character file, it tells me the file system is read-only > although >> the permissions for /dev are drwxr-xr-x. It's also not mounting /opt > which >> is what is on /dev/system/lvm1. >> >> doing the mount command, we see this output. >> >> proc on /proc type proc (rw) >> (none):/ # mount -a >> mount -a >> mount: devpts already mounted or /dev/pts busy >> mount: /dev/system/lvm1 is not a valid block device >> >> We're in the process of trying to restore back to the last good full > volume >> backup, but I'm really curious if changing /dev/null could have this > strong >> of a impact and if there's any ideas of what we might be able to do to > fix >> the problem without restoring. > > -- > Rich Smrcina > VM Assist, Inc. > Phone: 414-491-6001 > Ans Service: 360-715-2467 > rich.smrcina at vmassist.com > http://www.linkedin.com/in/richsmrcina > > Catch the WAVV! http://www.wavv.org > WAVV 2008 - Chattanooga - April 18-22, 2008 > > -- > 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 > > > > > CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of 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 > -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http:
Re: Console Server equivalent for z/VM
On Friday, 01/11/2008 at 03:37 EST, Mark Post <[EMAIL PROTECTED]> wrote: > >>> On Fri, Jan 11, 2008 at 12:15 PM, in message > <[EMAIL PROTECTED]>, David > Boyes <[EMAIL PROTECTED]> wrote: > -snip- > > From a usability standpoint, it'd be my expectation to AT MINIMUM be > > able to do SSL-protected telnet to a concentrator of some time and > > select a connected system to interact with. > > Sounds like an opportunity for profit via a commercial product. Unfortunately there's nothing in CP to connect to a virtual machine's ASCII console. In the environments where the support is being asked for, the only allowed interaction with Linux while its security system is inactive is via the console. But perhaps there are other remote console configurations (e.g. wasn't there a CTC console driver at one time?) that would be permitted, given that the preferred option isn't possible right now. It's a balance of risk vs. cost. 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
Re: Console Server equivalent for z/VM
> Unfortunately there's nothing in CP to connect to a virtual machine's > ASCII console. A clarification question: can a virtual ASCII console be attached to another virtual machine? Maybe I'm being dense, but I can't make out from the docs whether the support in 5.3 is just for the HMC "device" being attached to a Linux virtual machine, or whether a virtual ASCII console can be attached to another user. > But perhaps there are other remote console configurations (e.g. wasn't > there a CTC console driver at one time?) that would be permitted, given > that the preferred option isn't possible right now. I have a PVM-compatible console driver mostly working. I also have a working LAT-based console, although it would still be problematical if the kernel can't boot. AFAIK, the CTC console driver was never updated for 2.4 kernels (it was a 2.2 vintage thing), so it would probably take some surgery to get it working on a modern kernel. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Console Server equivalent for z/VM
On Monday, 01/14/2008 at 01:29 EST, David Boyes <[EMAIL PROTECTED]> wrote: > > Unfortunately there's nothing in CP to connect to a virtual machine's > > ASCII console. > > A clarification question: can a virtual ASCII console be attached to another > virtual machine? Maybe I'm being dense, but I can't make out from the docs > whether the support in 5.3 is just for the HMC "device" being attached to a > Linux virtual machine, or whether a virtual ASCII console can be attached to > another user. No. All that is available is the ability to ATTACH the VM LPAR's real HMC ASCII console to a guest. 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
Re: IODF-HCD Defining FCP on a z9 for z/Linux
Both Linux and VM can talk directly to the channels so you don't have to define anything for Linux or VM in HCD OS config. As long as the channels, CU & devices are attached to the lpar Linux & VM can use them. -- Jay Brenneman -- 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
VSWITCH routing question
Hi, On z/VM 5.2, I'm defining a VSWITCH as a primary router because I have a Linux guest performing the routing. When I do not define an OSA triplet (no RDEV specified), the PRI option has no effect. Even I perform 'cp set vswitch vsw1 pri', a VSWITCH query returns NONROUTER. However, once I define an RDEV, query then returns PRIROUTER. I assume the routing options don't take effect unless there's an external OSA interface defined. Is this true? If so, does the VSWITCH act in NONROUTER or PRIROUTER mode before the OSA is defined? The goal is to send packets to another network through the Linux router attached to this VSWITCH, but the VSWITCH seems to discard these packets as if NONROUTER were set. Is this a case where a GuestLAN is a better fit than a VSWITCH with no external interface? Thanks, -- Brad Hinson <[EMAIL PROTECTED]> Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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: IODF-HCD Defining FCP on a z9 for z/Linux
>>> On Mon, Jan 14, 2008 at 4:11 PM, in message <[EMAIL PROTECTED]>, Robert J Brenneman <[EMAIL PROTECTED]> wrote: > Both Linux and VM can talk directly to the channels so you don't have to > define anything for Linux or VM in HCD OS config. As long as the channels, > CU & devices are attached to the lpar Linux & VM can use them. Define "attached" in this context. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IODF-HCD Defining FCP on a z9 for z/Linux
On Monday, 01/14/2008 at 04:46 EST, Mark Post <[EMAIL PROTECTED]> wrote: > >>> On Mon, Jan 14, 2008 at 4:11 PM, in message > <[EMAIL PROTECTED]>, Robert J > Brenneman <[EMAIL PROTECTED]> wrote: > > Both Linux and VM can talk directly to the channels so you don't have to > > define anything for Linux or VM in HCD OS config. As long as the channels, > > CU & devices are attached to the lpar Linux & VM can use them. > > Define "attached" in this context. "Configured" is the term of art. As long as the chpids, CUs, and devices are configured to the VM LPAR (via IOCDS, HCD, or dynamic DEFINE), then CP (EDEVICE) and Linux (ATTACH or DEDICATE) can talk to the FCP adapters. The above is necessary, but typically not sufficient. Additional configuration of your SAN fabric is usually required to give Linux and/or CP access to the target WWPNs & LUNs. 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
Re: VSWITCH routing question
On Monday, 01/14/2008 at 04:19 EST, Brad Hinson <[EMAIL PROTECTED]> wrote: > I assume the routing options don't take effect unless there's an > external OSA interface defined. Is this true? Yes. > If so, does the VSWITCH > act in NONROUTER or PRIROUTER mode before the OSA is defined? Not applicable since there are no inbound packets from an OSA. > The goal is to send packets to another network through the Linux router > attached to this VSWITCH, but the VSWITCH seems to discard these packets > as if NONROUTER were set. Is this a case where a GuestLAN is a better > fit than a VSWITCH with no external interface? Make sure the Linux guest has configured PRIROUTER in it's network config. The other guests are delivering packets to the Linux guest's virtual NIC that do not have Linux's own IP address in them. As with a real OSA, PRIROUTER is required to get the NIC to accept all IP addresses. Alternatively, change to a layer 2 VSWITCH. Then all the PRIROUTER stuff goes away. 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
Re: IODF-HCD Defining FCP on a z9 for z/Linux
HI guys, I figured it out. There are two sections in the IODF, an LPARNAME and a CONFIG-ID For sanity I had the LPARNAMES and the CONFIG-ID the same. The CONFIG-ID is for z/OS and I think VM. It has no meaning in Linux. The CONFIG-ID is defined in option 1. In OPTION 5 you can associate Devices to a CONFIG-ID so you can select which Devices go to what z/OS (via the IPLPARM(LOAD**) All you need for Linux in the IODF is options 3,4,5 and no need to connect the devices to a CONFIG-ID. Sam Bass 254-771-7212 Sr z/OS Systems Specialist -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, January 14, 2008 3:38 PM To: LINUX-390@VM.MARIST.EDU Subject:Re: IODF-HCD Defining FCP on a z9 for z/Linux >>> On Mon, Jan 14, 2008 at 4:11 PM, in message <[EMAIL PROTECTED]>, Robert J Brenneman <[EMAIL PROTECTED]> wrote: > Both Linux and VM can talk directly to the channels so you don't have to > define anything for Linux or VM in HCD OS config. As long as the channels, > CU & devices are attached to the lpar Linux & VM can use them. Define "attached" in this context. 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 -- 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: IODF-HCD Defining FCP on a z9 for z/Linux
> (BTW, why should PR/SM care what OS is to be run in the LPAR?) So it can know which one the IFLs can be given to? It was probably not using IFLs either since it was defined as MVS. I've been told also that you get a little penguin picture there somewhere too. Course I haven't actually seen it since no one lets me near an HMC. Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, January 14, 2008 2:41 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] IODF-HCD Defining FCP on a z9 for z/Linux >>> On Mon, Jan 14, 2008 at 5:11 PM, in message <[EMAIL PROTECTED]>, Alan Altmark <[EMAIL PROTECTED]> wrote: -snip- >> Define "attached" in this context. > > "Configured" is the term of art. As long as the chpids, CUs, and > devices are configured to the VM LPAR (via IOCDS, HCD, or dynamic > DEFINE), then CP > (EDEVICE) and Linux (ATTACH or DEDICATE) can talk to the FCP adapters. This was the problem the OP was having. Since the LPAR was defined as being an "MVS LPAR" (BTW, why should PR/SM care what OS is to be run in the LPAR?), HCD would not allow him to configure the FCP I/O devices onto the LPAR. He had to either create a new LPAR definition, saying it was a "VM LPAR" or delete and redefine the existing one. > The above is necessary, but typically not sufficient. Additional > configuration of your SAN fabric is usually required to give Linux > and/or CP access to the target WWPNs & LUNs. Sure, but you have to get past the first hurdle before you can even try to deal with these items. 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 -- 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: IODF-HCD Defining FCP on a z9 for z/Linux
>>> On Mon, Jan 14, 2008 at 5:11 PM, in message <[EMAIL PROTECTED]>, Alan Altmark <[EMAIL PROTECTED]> wrote: -snip- >> Define "attached" in this context. > > "Configured" is the term of art. As long as the chpids, CUs, and devices > are configured to the VM LPAR (via IOCDS, HCD, or dynamic DEFINE), then CP > (EDEVICE) and Linux (ATTACH or DEDICATE) can talk to the FCP adapters. This was the problem the OP was having. Since the LPAR was defined as being an "MVS LPAR" (BTW, why should PR/SM care what OS is to be run in the LPAR?), HCD would not allow him to configure the FCP I/O devices onto the LPAR. He had to either create a new LPAR definition, saying it was a "VM LPAR" or delete and redefine the existing one. > The above is necessary, but typically not sufficient. Additional > configuration of your SAN fabric is usually required to give Linux and/or > CP access to the target WWPNs & LUNs. Sure, but you have to get past the first hurdle before you can even try to deal with these items. 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
Cracklib library empty SLES 10
Hi, It seems that the three dictionary files for cracklib (pw_dict.hwm, pw_dic.pwd and pw_dict.pwi) are empty on SLES 10-SP1 system but on a SLES 9 system they were populated when the system was installed. This causes YAST to fail adding users or changing passwords for users without any error message. Command line password change via passwd command receives the following error message: /usr/share/cracklib/pw_dict: error reading header and does not change the password. This happens only when the local security settings in YAST are set to check for complicated passwords, etc.. Turning these settings off will fix the problem. Does anyone know how to build the dictionary files for cracklib on SLES 10 and why they are missing to begin with? Thanks. -- 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: Cracklib library empty SLES 10
>>> On Mon, Jan 14, 2008 at 6:23 PM, in message <[EMAIL PROTECTED]>, Aria Bamdad <[EMAIL PROTECTED]> wrote: -snip- > Does anyone know how to build the dictionary files for cracklib on SLES 10 > and why they are missing to begin with? They are non-empty on my SLES10 SP1 system. What does "rpm -V cracklib" show you? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux not recognizing file systems
Joell Chockley wrote: I've got a strange problem with a Linux guest. The only indicator we've come up with so far is that /dev/null had it's file permissions changed on Friday afternoon to -rw-r--r-- 1 root root 81 2008-01-11 15:03 /dev/null (we don't know how this was changed). One of our admins changed it back to This is what I would expect to see if someone deleted /dev/null and then root did something like echo >/dev/null as you would expect root to do sometimes - just look at /etc/init.d/* grep /dev/null /etc/init.d/* _I_ would like to know who|what deleted /dev/null and what else was done, it sounds to me like a breakdown in procedures, or some malware was installed. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Linux not recognizing file systems
/sbin/SuSEconfig can change permissions on things based on the settings in /etc/permissions* and /etc/sysconfig/security Could you have changed those things and run it? (or yast2 ran it after changing something else). Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John Summerfield Sent: Monday, January 14, 2008 4:11 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Linux not recognizing file systems Joell Chockley wrote: > I've got a strange problem with a Linux guest. The only indicator > we've come up with so far is that /dev/null had it's file permissions > changed on Friday afternoon to -rw-r--r-- 1 root root 81 2008-01-11 > 15:03 /dev/null (we don't know how this was changed). One of our > admins changed it back to > This is what I would expect to see if someone deleted /dev/null and then root did something like echo >/dev/null as you would expect root to do sometimes - just look at /etc/init.d/* grep /dev/null /etc/init.d/* _I_ would like to know who|what deleted /dev/null and what else was done, it sounds to me like a breakdown in procedures, or some malware was installed. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [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: Cracklib library empty SLES 10
On Mon, 14 Jan 2008 16:39:19 -0700 Mark Post said: On Mon, Jan 14, 2008 at 6:23 PM, in message ><[EMAIL PROTECTED]>, Aria Bamdad ><[EMAIL PROTECTED]> wrote:=20 >-snip- >> Does anyone know how to build the dictionary files for cracklib on SLES = >10 >> and why they are missing to begin with? > >They are non-empty on my SLES10 SP1 system. What does "rpm -V cracklib" = >show you? > > >Mark Post RPM shows the following: S.5T/usr/share/cracklib/pw_dict.hwm S.5T/usr/share/cracklib/pw_dict.pwd S.5T/usr/share/cracklib/pw_dict.pwi The files are there but they are zero byte files. There is also a cracklib.magic file that has data in it. -- 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: Cracklib library empty SLES 10
>>> On Mon, Jan 14, 2008 at 8:42 PM, in message <[EMAIL PROTECTED]>, Aria Bamdad <[EMAIL PROTECTED]> wrote: -snip- > RPM shows the following: > > S.5T/usr/share/cracklib/pw_dict.hwm > S.5T/usr/share/cracklib/pw_dict.pwd > S.5T/usr/share/cracklib/pw_dict.pwi > The files are there but they are zero byte files. There is also > a cracklib.magic file that has data in it. So, basically, someone running as the root user emptied them. Most likely the time stamp on the files will tell you when. You can either re-install the RPM, or copy the files from another SLES10 SP1 system that has the same version of cracklib installed. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IODF-HCD Defining FCP on a z9 for z/Linux
On Monday, 01/14/2008 at 05:43 EST, Mark Post <[EMAIL PROTECTED]> wrote: > This was the problem the OP was having. Since the LPAR was defined as being an > "MVS LPAR" (BTW, why should PR/SM care what OS is to be run in the LPAR?), HCD > would not allow him to configure the FCP I/O devices onto the LPAR. He had to > either create a new LPAR definition, saying it was a "VM LPAR" or delete and > redefine the existing one. PR/SM doesn't care. IOCP doesn't care. HCD cares, wanting to ensure that you create a valid IODF for z/OS. 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
Celio C Carvalho/Brazil/IBM is on Vacation
I will be out of the office starting 14/01/2008 and will not return until 19/01/2008. Estarei de férias no periodo de 14/Jan/2008 e retornarei em 19/Jan/2008. I will respond to your message when I return. Estarei de férias até o dia 01/07/2005. Seu email não está sendo redirecionado para outro pessoa. -- 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
