Re: zLinux OS disk read-only
Steve, I am afraid so! I think it will affect the z/OS DASD on the same CU. In our case, it worked out well because all our DASD for z/VM is the on same CU. Waheb Waheb Boukhemis McJunkin Red Man Corporation Email: waheb.boukhe...@mrcpvf.com Phone: +1-304-348-1588 Fax: +1-304-348-4902 Cell: +1-304-993-6070 www.MRCPVF.com -- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Perez, Steve S Sent: Tuesday, March 08, 2011 1:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only Hi Waheb, I do not have this PTF installed. Yes we are using HYPERPAV. We have shared DASD between our z/OS and z/VM LPARs. If I turn off HYPERPAV on my z/VM LPAR via the SET command, will that also turn off HYPERPAV effectively on the z/OS side for those volumes on that CU ? I don't want it to affect the z/OS side. If it does affect z/OS then my only option would be to apply the PTF. Thanks. Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Boukhemis, Waheb Sent: Wednesday, March 02, 2011 8:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only Check if you have PTF UM32790 for z/VM540. It is on the 1002 RSU. Are you using HYPERPAV? If so, removing HYPERPAV volume use from your VM LPAR should resolve the problem. We had similar problem and the applying 1002 RSU service fixed it. Example: 1. Q CU 0039 PAVMODE If it is in any kind of PAV mode then: 2. SET CU NOPAV 0039 3. RUN your test. Hope this helps! Waheb Boukhemis McJunkin Red Man Corporation Email: waheb.boukhe...@mrcpvf.com Phone: +1-304-348-1588 Fax: +1-304-348-4902 Cell: +1-304-993-6070 www.MRCPVF.com -- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Steve Perez Sent: Tuesday, March 01, 2011 3:23 PM To: IBMVM@LISTSERV.UARK.EDU Subject: zLinux OS disk read-only Hello All, Has anyone run into a situation where the zLinux OS disk has become READ- ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. My zLinux Admin were doing compares between the production environment versus the Test D/R environment and noticed it. He issued the following on the prod zLinux guest environment: # mount -o remount,rw /dev/VolGroup01/LogVol00 mount: block device /dev/VolGroup01/LogVol00 is write-protected, mounting read-only Since we are testing our D/R process at the moment for the z/VM LPAR we are unsure at this point whether that is a contributing factor. It should not be but we can't rule it out. We paused our PPRC/Global mirroring from the z/OS side before starting the D/R activities to perform recovery of the z/VM & z/Linux. The problem was found while in the middle of verifying/comparing environments on the zLinux side. I can link to the minidisk that is used to IPL that zLinux guest and it shows R/W when I issue Q LINKS. All other minidisks owned by that zLinux guest are R/W as well. From my perspective (z/VM) all looks good. Any input would be appreciated, if anything to rule out that PPRC/GM would have contributed to this. Thanks. Steve. ** This message may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is legally privileged. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message and any copies immediately thereafter. Thank you. ** CLLD
Re: zLinux OS disk read-only
Hi Waheb, I do not have this PTF installed. Yes we are using HYPERPAV. We have shared DASD between our z/OS and z/VM LPARs. If I turn off HYPERPAV on my z/VM LPAR via the SET command, will that also turn off HYPERPAV effectively on the z/OS side for those volumes on that CU ? I don't want it to affect the z/OS side. If it does affect z/OS then my only option would be to apply the PTF. Thanks. Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Boukhemis, Waheb Sent: Wednesday, March 02, 2011 8:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only Check if you have PTF UM32790 for z/VM540. It is on the 1002 RSU. Are you using HYPERPAV? If so, removing HYPERPAV volume use from your VM LPAR should resolve the problem. We had similar problem and the applying 1002 RSU service fixed it. Example: 1. Q CU 0039 PAVMODE If it is in any kind of PAV mode then: 2. SET CU NOPAV 0039 3. RUN your test. Hope this helps! Waheb Boukhemis McJunkin Red Man Corporation Email: waheb.boukhe...@mrcpvf.com Phone: +1-304-348-1588 Fax: +1-304-348-4902 Cell: +1-304-993-6070 www.MRCPVF.com -- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Steve Perez Sent: Tuesday, March 01, 2011 3:23 PM To: IBMVM@LISTSERV.UARK.EDU Subject: zLinux OS disk read-only Hello All, Has anyone run into a situation where the zLinux OS disk has become READ- ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. My zLinux Admin were doing compares between the production environment versus the Test D/R environment and noticed it. He issued the following on the prod zLinux guest environment: # mount -o remount,rw /dev/VolGroup01/LogVol00 mount: block device /dev/VolGroup01/LogVol00 is write-protected, mounting read-only Since we are testing our D/R process at the moment for the z/VM LPAR we are unsure at this point whether that is a contributing factor. It should not be but we can't rule it out. We paused our PPRC/Global mirroring from the z/OS side before starting the D/R activities to perform recovery of the z/VM & z/Linux. The problem was found while in the middle of verifying/comparing environments on the zLinux side. I can link to the minidisk that is used to IPL that zLinux guest and it shows R/W when I issue Q LINKS. All other minidisks owned by that zLinux guest are R/W as well. From my perspective (z/VM) all looks good. Any input would be appreciated, if anything to rule out that PPRC/GM would have contributed to this. Thanks. Steve. ** This message may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is legally privileged. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message and any copies immediately thereafter. Thank you. ** CLLD
Re: zLinux OS disk read-only
So you are saying you suspended your PPRC and then did a "failover test" . What does that mean? You IPL'd off the PPRC secondaries (that were now broken mirror? ) or you flashed the whole thing so something else? Or is it the primary copy that is corrupted? If you corrupted or lost data in the process, you probably should be opening a ticket with IBM to see if they can figure out why. Marcy From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Perez, Steve S Sent: Sunday, March 06, 2011 5:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] zLinux OS disk read-only Output from q v dasd below. The OS disk is address 200. We still had the problem. Nothing was in the Operator log to indicate any write inhibit messages. To correct it, we decided to IPL the z/VM LPAR this weekend. When the z/Linux guest machine came up, the Filesystem was corrupted. That same z/Linux guest machine we recovered during our test D/R had the same issue with a corrupt Filesystem. With that in mind, we suspect that after suspending PPRC/Global Mirror, the Failover to test our D/R process may have had some hand in corrupting the Filesystem. -q v dasd DASD 0199 3390 540RES R/O 5 CYL ON DASD 50B4 SUBCHANNEL = 0009 DASD 0200 3390 LX53B5 R/W 10016 CYL ON DASD 53B5 SUBCHANNEL = 000A DASD 0201 3390 LX54B4 R/W 10016 CYL ON DASD 54B4 SUBCHANNEL = 000B DASD 0202 3390 LX54B5 R/W CYL ON DASD 54B5 SUBCHANNEL = 000C DASD 0203 3390 LX59B5 R/W CYL ON DASD 59B5 SUBCHANNEL = 000D DASD 0204 3390 LX5AB4 R/W 10016 CYL ON DASD 5AB4 SUBCHANNEL = 000E DASD 0205 3390 LX5AB5 R/W 10016 CYL ON DASD 5AB5 SUBCHANNEL = 000F ---snippet from z/Linux guest Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... Found volume group "vgIBM" using metadata type lvm2 Found volume group "VolGroup01" using metadata type lvm2 Activating logical volumes 2 logical volume(s) in volume group "VolGroup01" now active Creating root device. Mounting root filesystem. EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs warning (device dm-0): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure EXT3-fs warning (device dm-0): ext3_clear_journal_err: Marking fs in need of fil esystem check. EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys SELinux: Disabled at runtime. type=1404 audit(1299410056.218:2): selinux=0 auid=4294967295 ses=4294967295 "INIT: version 2.86 booting"" Welcome to Red Hat Enterprise Linux Server" Setting clock (localtime): Sun Mar 6 05:14:16 CST 2011 Ý OK ¨"" Starting udev: Ý OK ¨"" Thanks, Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Marcy Cortes Sent: Tuesday, March 01, 2011 3:50 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only Do a vmcp q v dasd If it shows r/w and is still not working, log the guest off and back on. If it works then, that would indicate it is some kind of RH problem and Linux was confused. If it still does not work, check the VM Operator log for any write inhibit HCP* error messages. That would indicate some problem
Re: zLinux OS disk read-only
Output from q v dasd below. The OS disk is address 200. We still had the problem. Nothing was in the Operator log to indicate any write inhibit messages. To correct it, we decided to IPL the z/VM LPAR this weekend. When the z/Linux guest machine came up, the Filesystem was corrupted. That same z/Linux guest machine we recovered during our test D/R had the same issue with a corrupt Filesystem. With that in mind, we suspect that after suspending PPRC/Global Mirror, the Failover to test our D/R process may have had some hand in corrupting the Filesystem. -q v dasd DASD 0199 3390 540RES R/O 5 CYL ON DASD 50B4 SUBCHANNEL = 0009 DASD 0200 3390 LX53B5 R/W 10016 CYL ON DASD 53B5 SUBCHANNEL = 000A DASD 0201 3390 LX54B4 R/W 10016 CYL ON DASD 54B4 SUBCHANNEL = 000B DASD 0202 3390 LX54B5 R/W CYL ON DASD 54B5 SUBCHANNEL = 000C DASD 0203 3390 LX59B5 R/W CYL ON DASD 59B5 SUBCHANNEL = 000D DASD 0204 3390 LX5AB4 R/W 10016 CYL ON DASD 5AB4 SUBCHANNEL = 000E DASD 0205 3390 LX5AB5 R/W 10016 CYL ON DASD 5AB5 SUBCHANNEL = 000F ---snippet from z/Linux guest Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... Found volume group "vgIBM" using metadata type lvm2 Found volume group "VolGroup01" using metadata type lvm2 Activating logical volumes 2 logical volume(s) in volume group "VolGroup01" now active Creating root device. Mounting root filesystem. EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs warning (device dm-0): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure EXT3-fs warning (device dm-0): ext3_clear_journal_err: Marking fs in need of fil esystem check. EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys SELinux: Disabled at runtime. type=1404 audit(1299410056.218:2): selinux=0 auid=4294967295 ses=4294967295 "INIT: version 2.86 booting"" Welcome to Red Hat Enterprise Linux Server" Setting clock (localtime): Sun Mar 6 05:14:16 CST 2011 Ý OK ¨"" Starting udev: Ý OK ¨"" Thanks, Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Marcy Cortes Sent: Tuesday, March 01, 2011 3:50 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only Do a vmcp q v dasd If it shows r/w and is still not working, log the guest off and back on. If it works then, that would indicate it is some kind of RH problem and Linux was confused. If it still does not work, check the VM Operator log for any write inhibit HCP* error messages. That would indicate some problem with the HW stop you did. Marcy From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Perez, Steve S Sent: Tuesday, March 01, 2011 1:41 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] zLinux OS disk read-only I issued a LINK RR against it and did a Q LINKS and it shows no other link access to that disk. Would it be possible that when we paused PPRC and suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) that it may have accessed the dasd the minidisk is on in write mode and caused the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mark Pace Sent: Tuesday, March 01, 2011 2:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S mailto:sspe...@corelogic.com>> wrote: The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU>] O
Re: zLinux OS disk read-only
Steve, Just a suggestion, check the storage itself to make sure that the volumes are not set to r/o. I've been plagued with read-only situations due to a myriad of reasons but the 'write protected' reminds me of the one situation where the storage itself were set to read-only as they were DR volumes. Thanx, Joe Comitini TD Ameritrade - Senior SystemZ Engineer Office: (201) 369 - 8436 Cell: (551) 200 - 7781 From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Perez, Steve S Sent: Tuesday, March 01, 2011 6:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only When my zLinux Admin issued this command in the zLinux guest machine, he got the "write-protected" message indicating to him that the OS disk is read-only... # mount -o remount,rw /dev/VolGroup01/LogVol00 mount: block device /dev/VolGroup01/LogVol00 is write-protected, mounting read-only He said it wasn't like that yesterday. The likelihood of a finger check is very minimal since the way we have these guest machines start up, which is directly IPL it's OS disk (addr 200). My zLinux Admin tells me that it was fine Monday before the D/R test started this morning. He himself I guess could have finger checked, but he knows very little about how VM works let alone issue the command to link the OS disk device R/O. Thank you for the suggestion on IPLing the guest into CMS first. I will look into it again at some point when more time allows. But in the meantime, this bizarre occurrence has puzzled us. I have since set the console to start at IPL/startup of the guest machine to get some console activity log to see what he's doing at startup. Thanks for you assistance. Kind Regards, Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 4:29 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only You said you ended up with the disk in read-only mode, but M would imply that if you couldn't get it in read-write mode, you wouldn't get it at all. This would lead me to believe that there might have been fingers at work on the console after the log-in and before the boot that might have subsequently linked the disk, possibly with a "LINK * 200 200 MR", maybe? Again, the console log would lead to the footprint of the perp that would tell all. Another fine way to handle the situation and allow some control would be to IPL the guest into CMS before starting the Linux guest. Set up the machine using the CMS profile and do your sanity checks there, then IPL the Linux boot disk when you know things will go well. Given our two CEC environment, and our history before going into CSE, we use this method to check that the image was last run on the current LPAR before IPLing the Linux image, to be sure that it can't be running in the other CEC. We had the same image booted on both systems at the same time once too often, destroying the image (i.e... Once) We use a read-only CMS 191 with a profile to perform this vital sanity check (for us) before allowing the Linux image to start. (In fact, all our linux images share the same 191 minidisk.) Checking the Linux disks to be sure they are RW certainly wouldn't hurt as well. It would be a simple task, especially if you stuck to a standard addressing scheme for all your images. Just an idea to think about. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 3:40 PM, "Perez, Steve S" wrote: I issued a LINK RR against it and did a Q LINKS and it shows no other link access to that disk. Would it be possible that when we paused PPRC and suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) that it may have accessed the dasd the minidisk is on in write mode and caused the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mark Pace Sent: Tuesday, March 01, 2011 2:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S wrote:
Re: zLinux OS disk read-only
Check if you have PTF UM32790 for z/VM540. It is on the 1002 RSU. Are you using HYPERPAV? If so, removing HYPERPAV volume use from your VM LPAR should resolve the problem. We had similar problem and the applying 1002 RSU service fixed it. Example: 1. Q CU 0039 PAVMODE If it is in any kind of PAV mode then: 2. SET CU NOPAV 0039 3. RUN your test. Hope this helps! Waheb Boukhemis McJunkin Red Man Corporation Email: waheb.boukhe...@mrcpvf.com Phone: +1-304-348-1588 Fax: +1-304-348-4902 Cell: +1-304-993-6070 www.MRCPVF.com -- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Steve Perez Sent: Tuesday, March 01, 2011 3:23 PM To: IBMVM@LISTSERV.UARK.EDU Subject: zLinux OS disk read-only Hello All, Has anyone run into a situation where the zLinux OS disk has become READ- ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. My zLinux Admin were doing compares between the production environment versus the Test D/R environment and noticed it. He issued the following on the prod zLinux guest environment: # mount -o remount,rw /dev/VolGroup01/LogVol00 mount: block device /dev/VolGroup01/LogVol00 is write-protected, mounting read-only Since we are testing our D/R process at the moment for the z/VM LPAR we are unsure at this point whether that is a contributing factor. It should not be but we can't rule it out. We paused our PPRC/Global mirroring from the z/OS side before starting the D/R activities to perform recovery of the z/VM & z/Linux. The problem was found while in the middle of verifying/comparing environments on the zLinux side. I can link to the minidisk that is used to IPL that zLinux guest and it shows R/W when I issue Q LINKS. All other minidisks owned by that zLinux guest are R/W as well. From my perspective (z/VM) all looks good. Any input would be appreciated, if anything to rule out that PPRC/GM would have contributed to this. Thanks. Steve.
Re: zLinux OS disk read-only
Steve, This really sounds like a Linux issue to me, when Linux has r/o(restricted by VM) access to disks it thinks are r/w, you get a MUCH different error message. That said, maybe a re-ipl would help the Linux machine, but I would check your logical volume configurations (pvdisplay, vgdisplay, and lvdisplay) first. Hope this helps, Mike From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Perez, Steve S Sent: Tuesday, March 01, 2011 6:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only When my zLinux Admin issued this command in the zLinux guest machine, he got the "write-protected" message indicating to him that the OS disk is read-only... # mount -o remount,rw /dev/VolGroup01/LogVol00 mount: block device /dev/VolGroup01/LogVol00 is write-protected, mounting read-only He said it wasn't like that yesterday. The likelihood of a finger check is very minimal since the way we have these guest machines start up, which is directly IPL it's OS disk (addr 200). My zLinux Admin tells me that it was fine Monday before the D/R test started this morning. He himself I guess could have finger checked, but he knows very little about how VM works let alone issue the command to link the OS disk device R/O. Thank you for the suggestion on IPLing the guest into CMS first. I will look into it again at some point when more time allows. But in the meantime, this bizarre occurrence has puzzled us. I have since set the console to start at IPL/startup of the guest machine to get some console activity log to see what he's doing at startup. Thanks for you assistance. Kind Regards, Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 4:29 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only You said you ended up with the disk in read-only mode, but M would imply that if you couldn't get it in read-write mode, you wouldn't get it at all. This would lead me to believe that there might have been fingers at work on the console after the log-in and before the boot that might have subsequently linked the disk, possibly with a "LINK * 200 200 MR", maybe? Again, the console log would lead to the footprint of the perp that would tell all. Another fine way to handle the situation and allow some control would be to IPL the guest into CMS before starting the Linux guest. Set up the machine using the CMS profile and do your sanity checks there, then IPL the Linux boot disk when you know things will go well. Given our two CEC environment, and our history before going into CSE, we use this method to check that the image was last run on the current LPAR before IPLing the Linux image, to be sure that it can't be running in the other CEC. We had the same image booted on both systems at the same time once too often, destroying the image (i.e... Once) We use a read-only CMS 191 with a profile to perform this vital sanity check (for us) before allowing the Linux image to start. (In fact, all our linux images share the same 191 minidisk.) Checking the Linux disks to be sure they are RW certainly wouldn't hurt as well. It would be a simple task, especially if you stuck to a standard addressing scheme for all your images. Just an idea to think about. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 3:40 PM, "Perez, Steve S" wrote: I issued a LINK RR against it and did a Q LINKS and it shows no other link access to that disk. Would it be possible that when we paused PPRC and suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) that it may have accessed the dasd the minidisk is on in write mode and caused the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mark Pace Sent: Tuesday, March 01, 2011 2:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S wrote: The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the gu
Re: zLinux OS disk read-only
Are there any additional messages in /var/log/messages when he attempts the mount command? You can start spooling your console immediately with vmcp spool cons \* start (prefix the * with \ from Linux ) You might be getting some messages either on the console or on the /var/log/messages when the mount command fails. Marcy From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Perez, Steve S Sent: Tuesday, March 01, 2011 3:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] zLinux OS disk read-only When my zLinux Admin issued this command in the zLinux guest machine, he got the "write-protected" message indicating to him that the OS disk is read-only... # mount -o remount,rw /dev/VolGroup01/LogVol00 mount: block device /dev/VolGroup01/LogVol00 is write-protected, mounting read-only He said it wasn't like that yesterday. The likelihood of a finger check is very minimal since the way we have these guest machines start up, which is directly IPL it's OS disk (addr 200). My zLinux Admin tells me that it was fine Monday before the D/R test started this morning. He himself I guess could have finger checked, but he knows very little about how VM works let alone issue the command to link the OS disk device R/O. Thank you for the suggestion on IPLing the guest into CMS first. I will look into it again at some point when more time allows. But in the meantime, this bizarre occurrence has puzzled us. I have since set the console to start at IPL/startup of the guest machine to get some console activity log to see what he's doing at startup. Thanks for you assistance. Kind Regards, Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 4:29 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only You said you ended up with the disk in read-only mode, but M would imply that if you couldn't get it in read-write mode, you wouldn't get it at all. This would lead me to believe that there might have been fingers at work on the console after the log-in and before the boot that might have subsequently linked the disk, possibly with a "LINK * 200 200 MR", maybe? Again, the console log would lead to the footprint of the perp that would tell all. Another fine way to handle the situation and allow some control would be to IPL the guest into CMS before starting the Linux guest. Set up the machine using the CMS profile and do your sanity checks there, then IPL the Linux boot disk when you know things will go well. Given our two CEC environment, and our history before going into CSE, we use this method to check that the image was last run on the current LPAR before IPLing the Linux image, to be sure that it can't be running in the other CEC. We had the same image booted on both systems at the same time once too often, destroying the image (i.e... Once) We use a read-only CMS 191 with a profile to perform this vital sanity check (for us) before allowing the Linux image to start. (In fact, all our linux images share the same 191 minidisk.) Checking the Linux disks to be sure they are RW certainly wouldn't hurt as well. It would be a simple task, especially if you stuck to a standard addressing scheme for all your images. Just an idea to think about. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 3:40 PM, "Perez, Steve S" wrote: I issued a LINK RR against it and did a Q LINKS and it shows no other link access to that disk. Would it be possible that when we paused PPRC and suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) that it may have accessed the dasd the minidisk is on in write mode and caused the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mark Pace Sent: Tuesday, March 01, 2011 2:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S wrote: The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest mac
Re: zLinux OS disk read-only
We do not have an ESM in place at the moment. We are still new to zLinux and still getting out feet wet. -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mike Walter Sent: Tuesday, March 01, 2011 4:43 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only Good ideas! > Again, the console log would lead to the footprint of the perp that would tell all. Which leads to another place that might tell... if you have an ESM (External Security Manager) it might have an audit file showing LINK attempts. For example, VM:Secure writes its audit file to the VMSECURE 1D0 mdisk. Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. RPN01 Sent by: "The IBM z/VM Operating System" 03/01/2011 04:28 PM Please respond to "The IBM z/VM Operating System" To IBMVM@LISTSERV.UARK.EDU cc Subject Re: zLinux OS disk read-only You said you ended up with the disk in read-only mode, but M would imply that if you couldn?t get it in read-write mode, you wouldn?t get it at all. This would lead me to believe that there might have been fingers at work on the console after the log-in and before the boot that might have subsequently linked the disk, possibly with a ?LINK * 200 200 MR?, maybe? Again, the console log would lead to the footprint of the perp that would tell all. Another fine way to handle the situation and allow some control would be to IPL the guest into CMS before starting the Linux guest. Set up the machine using the CMS profile and do your sanity checks there, then IPL the Linux boot disk when you know things will go well. Given our two CEC environment, and our history before going into CSE, we use this method to check that the image was last run on the current LPAR before IPLing the Linux image, to be sure that it can?t be running in the other CEC. We had the same image booted on both systems at the same time once too often, destroying the image (i.e... Once) We use a read-only CMS 191 with a profile to perform this vital sanity check (for us) before allowing the Linux image to start. (In fact, all our linux images share the same 191 minidisk.) Checking the Linux disks to be sure they are RW certainly wouldn?t hurt as well. It would be a simple task, especially if you stuck to a standard addressing scheme for all your images. Just an idea to think about. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 3:40 PM, "Perez, Steve S" wrote: I issued a LINK RR against it and did a Q LINKS and it shows no other link access to that disk. Would it be possible that when we paused PPRC and suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) that it may have accessed the dasd the minidisk is on in write mode and caused the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mark Pace Sent: Tuesday, March 01, 2011 2:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S wrote: The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 2:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only How is the disk defined in the CP Directory entry (i.e. What is the mode of the disk), and what is in the console log when the user was logged in that could give a clue about the status of the disk when the user was initialized? The mode will tell you the condition(s) that could lead to it being read only (other users having it read/write or even read only), and the log may even tell you which or how many users gummed up the works, or when things w
Re: zLinux OS disk read-only
When my zLinux Admin issued this command in the zLinux guest machine, he got the "write-protected" message indicating to him that the OS disk is read-only... # mount -o remount,rw /dev/VolGroup01/LogVol00 mount: block device /dev/VolGroup01/LogVol00 is write-protected, mounting read-only He said it wasn't like that yesterday. The likelihood of a finger check is very minimal since the way we have these guest machines start up, which is directly IPL it's OS disk (addr 200). My zLinux Admin tells me that it was fine Monday before the D/R test started this morning. He himself I guess could have finger checked, but he knows very little about how VM works let alone issue the command to link the OS disk device R/O. Thank you for the suggestion on IPLing the guest into CMS first. I will look into it again at some point when more time allows. But in the meantime, this bizarre occurrence has puzzled us. I have since set the console to start at IPL/startup of the guest machine to get some console activity log to see what he's doing at startup. Thanks for you assistance. Kind Regards, Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 4:29 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only You said you ended up with the disk in read-only mode, but M would imply that if you couldn't get it in read-write mode, you wouldn't get it at all. This would lead me to believe that there might have been fingers at work on the console after the log-in and before the boot that might have subsequently linked the disk, possibly with a "LINK * 200 200 MR", maybe? Again, the console log would lead to the footprint of the perp that would tell all. Another fine way to handle the situation and allow some control would be to IPL the guest into CMS before starting the Linux guest. Set up the machine using the CMS profile and do your sanity checks there, then IPL the Linux boot disk when you know things will go well. Given our two CEC environment, and our history before going into CSE, we use this method to check that the image was last run on the current LPAR before IPLing the Linux image, to be sure that it can't be running in the other CEC. We had the same image booted on both systems at the same time once too often, destroying the image (i.e... Once) We use a read-only CMS 191 with a profile to perform this vital sanity check (for us) before allowing the Linux image to start. (In fact, all our linux images share the same 191 minidisk.) Checking the Linux disks to be sure they are RW certainly wouldn't hurt as well. It would be a simple task, especially if you stuck to a standard addressing scheme for all your images. Just an idea to think about. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 3:40 PM, "Perez, Steve S" wrote: I issued a LINK RR against it and did a Q LINKS and it shows no other link access to that disk. Would it be possible that when we paused PPRC and suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) that it may have accessed the dasd the minidisk is on in write mode and caused the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mark Pace Sent: Tuesday, March 01, 2011 2:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S wrote: The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 2:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only How is the disk d
Re: zLinux OS disk read-only
Good ideas! > Again, the console log would lead to the footprint of the perp that would tell all. Which leads to another place that might tell... if you have an ESM (External Security Manager) it might have an audit file showing LINK attempts. For example, VM:Secure writes its audit file to the VMSECURE 1D0 mdisk. Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. RPN01 Sent by: "The IBM z/VM Operating System" 03/01/2011 04:28 PM Please respond to "The IBM z/VM Operating System" To IBMVM@LISTSERV.UARK.EDU cc Subject Re: zLinux OS disk read-only You said you ended up with the disk in read-only mode, but M would imply that if you couldn?t get it in read-write mode, you wouldn?t get it at all. This would lead me to believe that there might have been fingers at work on the console after the log-in and before the boot that might have subsequently linked the disk, possibly with a ?LINK * 200 200 MR?, maybe? Again, the console log would lead to the footprint of the perp that would tell all. Another fine way to handle the situation and allow some control would be to IPL the guest into CMS before starting the Linux guest. Set up the machine using the CMS profile and do your sanity checks there, then IPL the Linux boot disk when you know things will go well. Given our two CEC environment, and our history before going into CSE, we use this method to check that the image was last run on the current LPAR before IPLing the Linux image, to be sure that it can?t be running in the other CEC. We had the same image booted on both systems at the same time once too often, destroying the image (i.e... Once) We use a read-only CMS 191 with a profile to perform this vital sanity check (for us) before allowing the Linux image to start. (In fact, all our linux images share the same 191 minidisk.) Checking the Linux disks to be sure they are RW certainly wouldn?t hurt as well. It would be a simple task, especially if you stuck to a standard addressing scheme for all your images. Just an idea to think about. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 3:40 PM, "Perez, Steve S" wrote: I issued a LINK RR against it and did a Q LINKS and it shows no other link access to that disk. Would it be possible that when we paused PPRC and suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) that it may have accessed the dasd the minidisk is on in write mode and caused the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mark Pace Sent: Tuesday, March 01, 2011 2:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S wrote: The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 2:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only How is the disk defined in the CP Directory entry (i.e. What is the mode of the disk), and what is in the console log when the user was logged in that could give a clue about the status of the disk when the user was initialized? The mode will tell you the condition(s) that could lead to it being read only (other users having it read/write or even read only), and the log may even tell you which or how many users gummed up the works, or when things when oval on you. In any case, it had to have happened at some point, and there has to be a footprint, if you keep your logs. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ - ^^-^^
Re: zLinux OS disk read-only
Yes we looked at PPRC output and no indication of errors. All PPRC responses were normal and commands successfully completed. Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Tony Saul Sent: Tuesday, March 01, 2011 4:17 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only Did you check your PPRC responses? We had some errors when we first tried DR when we first installed VM (about 1 year ago). I can't remember all the details, but it was basically saying that PPRC links had not been broken and we were trying to use Tertiary dasd. We have our second DR test next week, so we are likely to hit the same problems and probably some new ones. Regards, Tony From: "Perez, Steve S" To: IBMVM@LISTSERV.UARK.EDU Sent: Wed, 2 March, 2011 8:21:24 AM Subject: Re: zLinux OS disk read-only No PROFILE EXEC involved. The guest machine directly IPL's the 200 mdisk, which is the OS disk of z/Linux. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Kris Buelens Sent: Tuesday, March 01, 2011 3:36 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only The words M Multiple-write access are somewhat misleading. MW stands for Multiwrite. M is "Multiple", you wil *not* get a link when some other user has a R/W link. With MR, one gets a R/O links when another R/W link exists. In this case, Linux had the minidisk, but in R/O mode, a fact that cannot be explained with this MDISK statement MDISK 200 3390 1 10016 LX53B5 M you get the minidisk R/W or not at all. Maybe a PROFILE EXEC did something? Like: CP Q V 200 if rc<>0 then 'CP LINK * 200 200 MR' 2011/3/1 Mark Pace mailto:pacemainl...@gmail.com>> M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S mailto:sspe...@corelogic.com>> wrote: The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU>] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 2:33 PM To: IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU> Subject: Re: zLinux OS disk read-only How is the disk defined in the CP Directory entry (i.e. What is the mode of the disk), and what is in the console log when the user was logged in that could give a clue about the status of the disk when the user was initialized? The mode will tell you the condition(s) that could lead to it being read only (other users having it read/write or even read only), and the log may even tell you which or how many users gummed up the works, or when things when oval on you. In any case, it had to have happened at some point, and there has to be a footprint, if you keep your logs. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 2:23 PM, "Steve Perez" mailto:sspe...@corelogic.com>> wrote: > Hello All, > > Has anyone run into a situation where the zLinux OS disk has become > READ- > > ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. > > My zLinux Admin were doing compares between the production environment > > versus the Test D/R environment and noticed it. He issued the > following > > on the prod zLinux guest environment: > > # mount -o remount,rw /dev/VolGroup01/LogVol00 > mount: block device /dev/VolGroup01/LogVol00 is write-protected, > mounting > > read-only > > Since we are testing our D/R process at the moment for the z/VM LPAR > we > > are unsure at this point whether that is a contributing factor. It > shoul d not be but we can't rule it out. We paused our PPRC/Global > mirroring fro m the z/OS side before starting the D/R activities to > perform recovery of > > the z/VM &
Re: zLinux OS disk read-only
You said you ended up with the disk in read-only mode, but M would imply that if you couldn¹t get it in read-write mode, you wouldn¹t get it at all. This would lead me to believe that there might have been fingers at work on the console after the log-in and before the boot that might have subsequently linked the disk, possibly with a ³LINK * 200 200 MR², maybe? Again, the console log would lead to the footprint of the perp that would tell all. Another fine way to handle the situation and allow some control would be to IPL the guest into CMS before starting the Linux guest. Set up the machine using the CMS profile and do your sanity checks there, then IPL the Linux boot disk when you know things will go well. Given our two CEC environment, and our history before going into CSE, we use this method to check that the image was last run on the current LPAR before IPLing the Linux image, to be sure that it can¹t be running in the other CEC. We had the same image booted on both systems at the same time once too often, destroying the image (i.e... Once) We use a read-only CMS 191 with a profile to perform this vital sanity check (for us) before allowing the Linux image to start. (In fact, all our linux images share the same 191 minidisk.) Checking the Linux disks to be sure they are RW certainly wouldn¹t hurt as well. It would be a simple task, especially if you stuck to a standard addressing scheme for all your images. Just an idea to think about. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 3:40 PM, "Perez, Steve S" wrote: > I issued a LINK RR against it and did a Q LINKS and it shows no other link > access to that disk. Would it be possible that when we paused PPRC and > suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) > that it may have accessed the dasd the minidisk is on in write mode and caused > the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? > > > > Steve. > > From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf > Of Mark Pace > Sent: Tuesday, March 01, 2011 2:57 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: zLinux OS disk read-only > > M Multiple-write access. Write access is established unless another user holds > a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to > the disk. > > Looks like some other VM has that disk linked in write mode. > > On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S wrote: >> The disk is defined as follows. This is an excerpt from the CP directory: >> >> IPL 200 >> . >> LINK RHMASTER 199 199 RR >> MDISK 200 3390 1 10016 LX53B5 M >> >> Unfortunately, the console log did not get spooled so I don't know what the >> log would have indicated for that disk when the guest machine came up. >> That's on my follow-up list. The guest machine is IPL'd off of its OS (disk >> 200) disk when it comes up (in its CP Directory) so I need to find a way to >> spool the console when it starts and not later after it has gone through its >> initialization. >> >> >> Thanks, >> Steve >> >> -----Original Message- >> From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On >> Behalf Of RPN01 >> Sent: Tuesday, March 01, 2011 2:33 PM >> To: IBMVM@LISTSERV.UARK.EDU >> Subject: Re: zLinux OS disk read-only >> >> How is the disk defined in the CP Directory entry (i.e. What is the mode of >> the disk), and what is in the console log when the user was logged in that >> could give a clue about the status of the disk when the user was >> initialized? >> >> The mode will tell you the condition(s) that could lead to it being read >> only (other users having it read/write or even read only), and the log may >> even tell you which or how many users gummed up the works, or when things >> when oval on you. >> >> In any case, it had to have happened at some point, and there has to be a >> footprint, if you keep your logs. >> >> -- >> Robert P. Nix Mayo Foundation.~. >> RO-OC-1-18 200 First Street SW /V\ >> 507-284-0844 Rochester, MN 55905 /( )\ >> - ^^-^^ >> "In theory, theory and practice are the same, but in practice, theory and >> practice are different." >> >> >> >> On 3/1/11 2:23 P
Re: zLinux OS disk read-only
Issued the command and it still shows R/W. We will bounce the guest machine off hours to determine if that will fix the problem. The VM Operator log does not show any errors that would indicate a write inhibit on the dasd/disk.. Steve From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Marcy Cortes Sent: Tuesday, March 01, 2011 3:50 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only Do a vmcp q v dasd If it shows r/w and is still not working, log the guest off and back on. If it works then, that would indicate it is some kind of RH problem and Linux was confused. If it still does not work, check the VM Operator log for any write inhibit HCP* error messages. That would indicate some problem with the HW stop you did. Marcy From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Perez, Steve S Sent: Tuesday, March 01, 2011 1:41 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] zLinux OS disk read-only I issued a LINK RR against it and did a Q LINKS and it shows no other link access to that disk. Would it be possible that when we paused PPRC and suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) that it may have accessed the dasd the minidisk is on in write mode and caused the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mark Pace Sent: Tuesday, March 01, 2011 2:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S mailto:sspe...@corelogic.com>> wrote: The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU>] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 2:33 PM To: IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU> Subject: Re: zLinux OS disk read-only How is the disk defined in the CP Directory entry (i.e. What is the mode of the disk), and what is in the console log when the user was logged in that could give a clue about the status of the disk when the user was initialized? The mode will tell you the condition(s) that could lead to it being read only (other users having it read/write or even read only), and the log may even tell you which or how many users gummed up the works, or when things when oval on you. In any case, it had to have happened at some point, and there has to be a footprint, if you keep your logs. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 2:23 PM, "Steve Perez" mailto:sspe...@corelogic.com>> wrote: > Hello All, > > Has anyone run into a situation where the zLinux OS disk has become > READ- > > ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. > > My zLinux Admin were doing compares between the production environment > > versus the Test D/R environment and noticed it. He issued the > following > > on the prod zLinux guest environment: > > # mount -o remount,rw /dev/VolGroup01/LogVol00 > mount: block device /dev/VolGroup01/LogVol00 is write-protected, > mounting > > read-only > > Since we are testing our D/R process at the moment for the z/VM LPAR > we > > are unsure at this point whether that is a contributing factor. It > shoul d not be but we can't rule it out. We paused our PPRC/Global > mirroring fro m the z/OS side before starting the D/R activities to > perform recovery of > > the z/VM & z/Linux. The problem was found while in the middle of > verifying/comparing environments on the zLinux side. I can link to > the > > minidisk that is used to IPL that zLinux guest and it shows R/W when I >
Re: zLinux OS disk read-only
On Tuesday, 03/01/2011 at 04:40 EST, "Perez, Steve S" wrote: > I issued a LINK RR against it and did a Q LINKS and it shows no other link > access to that disk. Would it be possible that when we paused PPRC and > suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) > that it may have accessed the dasd the minidisk is on in write mode and caused > the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? If someone played with the PPRC definitions, they could have reversed the primary/secondary relationship, making your volumes the secondaries. You can't write to a secondary. But I would certainly have expected messages on the operator's console if that happened. If this happened, then you break someone's fingers. GDPS breaks and restores PPRC connections only in synchronization with various flavors of CP HYPERSWAP commands. Humans or other solutions are expected to do the same. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Re: zLinux OS disk read-only
Did you check your PPRC responses? We had some errors when we first tried DR when we first installed VM (about 1 year ago). I can't remember all the details, but it was basically saying that PPRC links had not been broken and we were trying to use Tertiary dasd. We have our second DR test next week, so we are likely to hit the same problems and probably some new ones. Regards, Tony From: "Perez, Steve S" To: IBMVM@LISTSERV.UARK.EDU Sent: Wed, 2 March, 2011 8:21:24 AM Subject: Re: zLinux OS disk read-only No PROFILE EXEC involved. The guest machine directly IPL's the 200 mdisk, which is the OS disk of z/Linux. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Kris Buelens Sent: Tuesday, March 01, 2011 3:36 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only The wordsM Multiple-write access are somewhat misleading. MW stands for Multiwrite. M is "Multiple", you wil *not* get a link when some other user has a R/W link. With MR, one gets a R/O links when another R/W link exists. In this case, Linux had the minidisk, but in R/O mode, a fact that cannot be explained with this MDISK statement MDISK 200 3390 1 10016 LX53B5 M you get the minidisk R/W or not at all. Maybe a PROFILE EXEC did something? Like: CP Q V 200 if rc<>0 then 'CP LINK * 200 200 MR' 2011/3/1 Mark Pace M Multiple-write access. Write access is established unless another user holds >a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to >the disk. > > >Looks like some other VM has that disk linked in write mode. > > >On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S wrote: > >The disk is defined as follows. This is an excerpt from the CP directory: >> >>IPL 200 >>. >>LINK RHMASTER 199 199 RR >>MDISK 200 3390 1 10016 LX53B5 M >> >>Unfortunately, the console log did not get spooled so I don't know what the >>log >>would have indicated for that disk when the guest machine came up. That's on >>my >>follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk >>when >>it comes up (in its CP Directory) so I need to find a way to spool the >>console >>when it starts and not later after it has gone through its initialization. >> >> >>Thanks, >>Steve >> >>-Original Message- >>From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On >>Behalf >>Of RPN01 >>Sent: Tuesday, March 01, 2011 2:33 PM >>To: IBMVM@LISTSERV.UARK.EDU >>Subject: Re: zLinux OS disk read-only >> >>How is the disk defined in the CP Directory entry (i.e. What is the mode of >>the >>disk), and what is in the console log when the user was logged in that could >>give a clue about the status of the disk when the user was initialized? >> >>The mode will tell you the condition(s) that could lead to it being read only >>(other users having it read/write or even read only), and the log may even >>tell >>you which or how many users gummed up the works, or when things when oval on >>you. >> >>In any case, it had to have happened at some point, and there has to be a >>footprint, if you keep your logs. >> >>-- >>Robert P. Nix Mayo Foundation .~. >>RO-OC-1-18 200 First Street SW /V\ >>507-284-0844 Rochester, MN 55905 /( )\ >>- ^^-^^ >>"In theory, theory and practice are the same, but in practice, theory and >>practice are different." >> >> >> >>On 3/1/11 2:23 PM, "Steve Perez" wrote: >> >>> Hello All, >>> >>> Has anyone run into a situation where the zLinux OS disk has become >>> READ- >>> >>> ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. >>> >>> My zLinux Admin were doing compares between the production environment >>> >>> versus the Test D/R environment and noticed it. He issued the >>> following >>> >>> on the prod zLinux guest environment: >>> >>> # mount -o remount,rw /dev/VolGroup01/LogVol00 >>> mount: block device /dev/VolGroup01/LogVol00 is write-protected, >>> mounting >>> >>> read-only >>> >>> Since we are testing our D/R process at the moment for the z/VM LPAR >>> we >>> >>> are unsure at this point whether that is a contributing factor. It >>> shoul d not be but
Re: zLinux OS disk read-only
No PROFILE EXEC involved. The guest machine directly IPL's the 200 mdisk, which is the OS disk of z/Linux. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Kris Buelens Sent: Tuesday, March 01, 2011 3:36 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only The words M Multiple-write access are somewhat misleading. MW stands for Multiwrite. M is "Multiple", you wil *not* get a link when some other user has a R/W link. With MR, one gets a R/O links when another R/W link exists. In this case, Linux had the minidisk, but in R/O mode, a fact that cannot be explained with this MDISK statement MDISK 200 3390 1 10016 LX53B5 M you get the minidisk R/W or not at all. Maybe a PROFILE EXEC did something? Like: CP Q V 200 if rc<>0 then 'CP LINK * 200 200 MR' 2011/3/1 Mark Pace mailto:pacemainl...@gmail.com>> M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S mailto:sspe...@corelogic.com>> wrote: The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU>] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 2:33 PM To: IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU> Subject: Re: zLinux OS disk read-only How is the disk defined in the CP Directory entry (i.e. What is the mode of the disk), and what is in the console log when the user was logged in that could give a clue about the status of the disk when the user was initialized? The mode will tell you the condition(s) that could lead to it being read only (other users having it read/write or even read only), and the log may even tell you which or how many users gummed up the works, or when things when oval on you. In any case, it had to have happened at some point, and there has to be a footprint, if you keep your logs. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 2:23 PM, "Steve Perez" mailto:sspe...@corelogic.com>> wrote: > Hello All, > > Has anyone run into a situation where the zLinux OS disk has become > READ- > > ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. > > My zLinux Admin were doing compares between the production environment > > versus the Test D/R environment and noticed it. He issued the > following > > on the prod zLinux guest environment: > > # mount -o remount,rw /dev/VolGroup01/LogVol00 > mount: block device /dev/VolGroup01/LogVol00 is write-protected, > mounting > > read-only > > Since we are testing our D/R process at the moment for the z/VM LPAR > we > > are unsure at this point whether that is a contributing factor. It > shoul d not be but we can't rule it out. We paused our PPRC/Global > mirroring fro m the z/OS side before starting the D/R activities to > perform recovery of > > the z/VM & z/Linux. The problem was found while in the middle of > verifying/comparing environments on the zLinux side. I can link to > the > > minidisk that is used to IPL that zLinux guest and it shows R/W when I > > issue Q LINKS. All other minidisks owned by that zLinux guest are R/W a > s > well. From my perspective (z/VM) all looks good. > > Any input would be appreciated, if anything to rule out that PPRC/GM > woul d have contributed to this. > > Thanks. > Steve. ** This message may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is legally privileged. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are hereby notified that reading, disse
Re: zLinux OS disk read-only
Do a vmcp q v dasd If it shows r/w and is still not working, log the guest off and back on. If it works then, that would indicate it is some kind of RH problem and Linux was confused. If it still does not work, check the VM Operator log for any write inhibit HCP* error messages. That would indicate some problem with the HW stop you did. Marcy From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Perez, Steve S Sent: Tuesday, March 01, 2011 1:41 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] zLinux OS disk read-only I issued a LINK RR against it and did a Q LINKS and it shows no other link access to that disk. Would it be possible that when we paused PPRC and suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) that it may have accessed the dasd the minidisk is on in write mode and caused the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mark Pace Sent: Tuesday, March 01, 2011 2:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S mailto:sspe...@corelogic.com>> wrote: The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU>] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 2:33 PM To: IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU> Subject: Re: zLinux OS disk read-only How is the disk defined in the CP Directory entry (i.e. What is the mode of the disk), and what is in the console log when the user was logged in that could give a clue about the status of the disk when the user was initialized? The mode will tell you the condition(s) that could lead to it being read only (other users having it read/write or even read only), and the log may even tell you which or how many users gummed up the works, or when things when oval on you. In any case, it had to have happened at some point, and there has to be a footprint, if you keep your logs. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 2:23 PM, "Steve Perez" mailto:sspe...@corelogic.com>> wrote: > Hello All, > > Has anyone run into a situation where the zLinux OS disk has become > READ- > > ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. > > My zLinux Admin were doing compares between the production environment > > versus the Test D/R environment and noticed it. He issued the > following > > on the prod zLinux guest environment: > > # mount -o remount,rw /dev/VolGroup01/LogVol00 > mount: block device /dev/VolGroup01/LogVol00 is write-protected, > mounting > > read-only > > Since we are testing our D/R process at the moment for the z/VM LPAR > we > > are unsure at this point whether that is a contributing factor. It > shoul d not be but we can't rule it out. We paused our PPRC/Global > mirroring fro m the z/OS side before starting the D/R activities to > perform recovery of > > the z/VM & z/Linux. The problem was found while in the middle of > verifying/comparing environments on the zLinux side. I can link to > the > > minidisk that is used to IPL that zLinux guest and it shows R/W when I > > issue Q LINKS. All other minidisks owned by that zLinux guest are R/W a > s > well. From my perspective (z/VM) all looks good. > > Any input would be appreciated, if anything to rule out that PPRC/GM > woul d have contributed to this. > > Thanks. > Steve. ** This message may contain confidential or proprietary information intended only for the use of th
Re: zLinux OS disk read-only
I issued a LINK RR against it and did a Q LINKS and it shows no other link access to that disk. Would it be possible that when we paused PPRC and suspended Global Mirror on the z/OS LPAR (shared volumes between all LPARS) that it may have accessed the dasd the minidisk is on in write mode and caused the access mode on the z/VM LPAR to go into a READ-MODE? Is that probable? Steve. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mark Pace Sent: Tuesday, March 01, 2011 2:57 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only M Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S mailto:sspe...@corelogic.com>> wrote: The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU>] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 2:33 PM To: IBMVM@LISTSERV.UARK.EDU<mailto:IBMVM@LISTSERV.UARK.EDU> Subject: Re: zLinux OS disk read-only How is the disk defined in the CP Directory entry (i.e. What is the mode of the disk), and what is in the console log when the user was logged in that could give a clue about the status of the disk when the user was initialized? The mode will tell you the condition(s) that could lead to it being read only (other users having it read/write or even read only), and the log may even tell you which or how many users gummed up the works, or when things when oval on you. In any case, it had to have happened at some point, and there has to be a footprint, if you keep your logs. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 2:23 PM, "Steve Perez" mailto:sspe...@corelogic.com>> wrote: > Hello All, > > Has anyone run into a situation where the zLinux OS disk has become > READ- > > ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. > > My zLinux Admin were doing compares between the production environment > > versus the Test D/R environment and noticed it. He issued the > following > > on the prod zLinux guest environment: > > # mount -o remount,rw /dev/VolGroup01/LogVol00 > mount: block device /dev/VolGroup01/LogVol00 is write-protected, > mounting > > read-only > > Since we are testing our D/R process at the moment for the z/VM LPAR > we > > are unsure at this point whether that is a contributing factor. It > shoul d not be but we can't rule it out. We paused our PPRC/Global > mirroring fro m the z/OS side before starting the D/R activities to > perform recovery of > > the z/VM & z/Linux. The problem was found while in the middle of > verifying/comparing environments on the zLinux side. I can link to > the > > minidisk that is used to IPL that zLinux guest and it shows R/W when I > > issue Q LINKS. All other minidisks owned by that zLinux guest are R/W a > s > well. From my perspective (z/VM) all looks good. > > Any input would be appreciated, if anything to rule out that PPRC/GM > woul d have contributed to this. > > Thanks. > Steve. ** This message may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is legally privileged. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message and any copies immediately thereafter. Thank you. ** CLLD -- Mark D Pace Senior Systems Engineer Mainline Information Systems
Re: zLinux OS disk read-only
The words* M Multiple-write access* are somewhat misleading. MW stands for Multiwrite. M is "Multiple", you wil *not* get a link when some other user has a R/W link. With MR, one gets a R/O links when another R/W link exists. In this case, Linux had the minidisk, but in R/O mode, a fact that cannot be explained with this MDISK statement MDISK 200 3390 1 10016 LX53B5 M you get the minidisk R/W or not at all. Maybe a PROFILE EXEC did something? Like: CP Q V 200 if rc<>0 then 'CP LINK * 200 200 MR' 2011/3/1 Mark Pace > *M* Multiple-write access. Write access is established unless another user > holds > a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to > the disk. > > Looks like some other VM has that disk linked in write mode. > > On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S wrote: > >> The disk is defined as follows. This is an excerpt from the CP directory: >> >> IPL 200 >> . >> LINK RHMASTER 199 199 RR >> MDISK 200 3390 1 10016 LX53B5 M >> >> Unfortunately, the console log did not get spooled so I don't know what >> the log would have indicated for that disk when the guest machine came up. >> That's on my follow-up list. The guest machine is IPL'd off of its OS >> (disk 200) disk when it comes up (in its CP Directory) so I need to find a >> way to spool the console when it starts and not later after it has gone >> through its initialization. >> >> >> Thanks, >> Steve >> >> -Original Message----- >> From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On >> Behalf Of RPN01 >> Sent: Tuesday, March 01, 2011 2:33 PM >> To: IBMVM@LISTSERV.UARK.EDU >> Subject: Re: zLinux OS disk read-only >> >> How is the disk defined in the CP Directory entry (i.e. What is the mode >> of the disk), and what is in the console log when the user was logged in >> that could give a clue about the status of the disk when the user was >> initialized? >> >> The mode will tell you the condition(s) that could lead to it being read >> only (other users having it read/write or even read only), and the log may >> even tell you which or how many users gummed up the works, or when things >> when oval on you. >> >> In any case, it had to have happened at some point, and there has to be a >> footprint, if you keep your logs. >> >> -- >> Robert P. Nix Mayo Foundation.~. >> RO-OC-1-18 200 First Street SW/V\ >> 507-284-0844 Rochester, MN 55905 /( )\ >> -^^-^^ >> "In theory, theory and practice are the same, but in practice, theory and >> practice are different." >> >> >> >> On 3/1/11 2:23 PM, "Steve Perez" wrote: >> >> > Hello All, >> > >> > Has anyone run into a situation where the zLinux OS disk has become >> > READ- >> > >> > ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. >> > >> > My zLinux Admin were doing compares between the production environment >> > >> > versus the Test D/R environment and noticed it. He issued the >> > following >> > >> > on the prod zLinux guest environment: >> > >> > # mount -o remount,rw /dev/VolGroup01/LogVol00 >> > mount: block device /dev/VolGroup01/LogVol00 is write-protected, >> > mounting >> > >> > read-only >> > >> > Since we are testing our D/R process at the moment for the z/VM LPAR >> > we >> > >> > are unsure at this point whether that is a contributing factor. It >> > shoul d not be but we can't rule it out. We paused our PPRC/Global >> > mirroring fro m the z/OS side before starting the D/R activities to >> > perform recovery of >> > >> > the z/VM & z/Linux. The problem was found while in the middle of >> > verifying/comparing environments on the zLinux side. I can link to >> > the >> > >> > minidisk that is used to IPL that zLinux guest and it shows R/W when I >> > >> > issue Q LINKS. All other minidisks owned by that zLinux guest are R/W >> a >> > s >> > well. From my perspective (z/VM) all looks good. >> > >> > Any input would be appreciated, if anything to rule out that PPRC/GM >> > woul d have contributed to this. >> > >> > Thanks. >> > Steve. >> >> ***
Re: zLinux OS disk read-only
Thanks, Mike. That works great! Thats one off my "follow-up" list. Kind Regards, Steve From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mike Walter Sent: Tuesday, March 01, 2011 2:58 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only > so I need to find a way to spool the console when it starts and not later > after it has gone through its initialization. That's easy... Before the first device statement, insert: COMMAND SPOOL CONSOLE TO * START NAME &USERID CONSOLE Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. "Perez, Steve S" Sent by: "The IBM z/VM Operating System" 03/01/2011 02:53 PM Please respond to "The IBM z/VM Operating System" To IBMVM@LISTSERV.UARK.EDU cc Subject Re: zLinux OS disk read-only The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 2:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only How is the disk defined in the CP Directory entry (i.e. What is the mode of the disk), and what is in the console log when the user was logged in that could give a clue about the status of the disk when the user was initialized? The mode will tell you the condition(s) that could lead to it being read only (other users having it read/write or even read only), and the log may even tell you which or how many users gummed up the works, or when things when oval on you. In any case, it had to have happened at some point, and there has to be a footprint, if you keep your logs. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 2:23 PM, "Steve Perez" wrote: > Hello All, > > Has anyone run into a situation where the zLinux OS disk has become > READ- > > ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. > > My zLinux Admin were doing compares between the production environment > > versus the Test D/R environment and noticed it. He issued the > following > > on the prod zLinux guest environment: > > # mount -o remount,rw /dev/VolGroup01/LogVol00 > mount: block device /dev/VolGroup01/LogVol00 is write-protected, > mounting > > read-only > > Since we are testing our D/R process at the moment for the z/VM LPAR > we > > are unsure at this point whether that is a contributing factor. It > shoul d not be but we can't rule it out. We paused our PPRC/Global > mirroring fro m the z/OS side before starting the D/R activities to > perform recovery of > > the z/VM & z/Linux. The problem was found while in the middle of > verifying/comparing environments on the zLinux side. I can link to > the > > minidisk that is used to IPL that zLinux guest and it shows R/W when I > > issue Q LINKS. All other minidisks owned by that zLinux guest are R/W a > s > well. From my perspective (z/VM) all looks good. > > Any input would be appreciated, if anything to rule out that PPRC/GM > woul d have contributed to this. > > Thanks. > Steve. ** This message may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is legally privileged. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message and any copies immediately thereafter. Thank you. ** CLLD The information contained in this e-mail and any accomp
Re: zLinux OS disk read-only
> so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. That's easy... Before the first device statement, insert: COMMAND SPOOL CONSOLE TO * START NAME &USERID CONSOLE Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. "Perez, Steve S" Sent by: "The IBM z/VM Operating System" 03/01/2011 02:53 PM Please respond to "The IBM z/VM Operating System" To IBMVM@LISTSERV.UARK.EDU cc Subject Re: zLinux OS disk read-only The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 2:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only How is the disk defined in the CP Directory entry (i.e. What is the mode of the disk), and what is in the console log when the user was logged in that could give a clue about the status of the disk when the user was initialized? The mode will tell you the condition(s) that could lead to it being read only (other users having it read/write or even read only), and the log may even tell you which or how many users gummed up the works, or when things when oval on you. In any case, it had to have happened at some point, and there has to be a footprint, if you keep your logs. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 2:23 PM, "Steve Perez" wrote: > Hello All, > > Has anyone run into a situation where the zLinux OS disk has become > READ- > > ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. > > My zLinux Admin were doing compares between the production environment > > versus the Test D/R environment and noticed it. He issued the > following > > on the prod zLinux guest environment: > > # mount -o remount,rw /dev/VolGroup01/LogVol00 > mount: block device /dev/VolGroup01/LogVol00 is write-protected, > mounting > > read-only > > Since we are testing our D/R process at the moment for the z/VM LPAR > we > > are unsure at this point whether that is a contributing factor. It > shoul d not be but we can't rule it out. We paused our PPRC/Global > mirroring fro m the z/OS side before starting the D/R activities to > perform recovery of > > the z/VM & z/Linux. The problem was found while in the middle of > verifying/comparing environments on the zLinux side. I can link to > the > > minidisk that is used to IPL that zLinux guest and it shows R/W when I > > issue Q LINKS. All other minidisks owned by that zLinux guest are R/W a > s > well. From my perspective (z/VM) all looks good. > > Any input would be appreciated, if anything to rule out that PPRC/GM > woul d have contributed to this. > > Thanks. > Steve. ** This message may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is legally privileged. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message and any copies immediately thereafter. Thank you. ** CLLD The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any di
Re: zLinux OS disk read-only
*M* Multiple-write access. Write access is established unless another user holds a write, a stable (SR, SW, SM) or an exclusive (ER, EW) mode access to the disk. Looks like some other VM has that disk linked in write mode. On Tue, Mar 1, 2011 at 3:53 PM, Perez, Steve S wrote: > The disk is defined as follows. This is an excerpt from the CP directory: > > IPL 200 > . > LINK RHMASTER 199 199 RR > MDISK 200 3390 1 10016 LX53B5 M > > Unfortunately, the console log did not get spooled so I don't know what the > log would have indicated for that disk when the guest machine came up. > That's on my follow-up list. The guest machine is IPL'd off of its OS > (disk 200) disk when it comes up (in its CP Directory) so I need to find a > way to spool the console when it starts and not later after it has gone > through its initialization. > > > Thanks, > Steve > > -Original Message- > From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On > Behalf Of RPN01 > Sent: Tuesday, March 01, 2011 2:33 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: zLinux OS disk read-only > > How is the disk defined in the CP Directory entry (i.e. What is the mode of > the disk), and what is in the console log when the user was logged in that > could give a clue about the status of the disk when the user was > initialized? > > The mode will tell you the condition(s) that could lead to it being read > only (other users having it read/write or even read only), and the log may > even tell you which or how many users gummed up the works, or when things > when oval on you. > > In any case, it had to have happened at some point, and there has to be a > footprint, if you keep your logs. > > -- > Robert P. Nix Mayo Foundation.~. > RO-OC-1-18 200 First Street SW/V\ > 507-284-0844 Rochester, MN 55905 /( )\ > -^^-^^ > "In theory, theory and practice are the same, but in practice, theory and > practice are different." > > > > On 3/1/11 2:23 PM, "Steve Perez" wrote: > > > Hello All, > > > > Has anyone run into a situation where the zLinux OS disk has become > > READ- > > > > ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. > > > > My zLinux Admin were doing compares between the production environment > > > > versus the Test D/R environment and noticed it. He issued the > > following > > > > on the prod zLinux guest environment: > > > > # mount -o remount,rw /dev/VolGroup01/LogVol00 > > mount: block device /dev/VolGroup01/LogVol00 is write-protected, > > mounting > > > > read-only > > > > Since we are testing our D/R process at the moment for the z/VM LPAR > > we > > > > are unsure at this point whether that is a contributing factor. It > > shoul d not be but we can't rule it out. We paused our PPRC/Global > > mirroring fro m the z/OS side before starting the D/R activities to > > perform recovery of > > > > the z/VM & z/Linux. The problem was found while in the middle of > > verifying/comparing environments on the zLinux side. I can link to > > the > > > > minidisk that is used to IPL that zLinux guest and it shows R/W when I > > > > issue Q LINKS. All other minidisks owned by that zLinux guest are R/W a > > s > > well. From my perspective (z/VM) all looks good. > > > > Any input would be appreciated, if anything to rule out that PPRC/GM > > woul d have contributed to this. > > > > Thanks. > > Steve. > > ** > This message may contain confidential or proprietary information intended > only for the use of the > addressee(s) named above or may contain information that is legally > privileged. If you are > not the intended addressee, or the person responsible for delivering it to > the intended addressee, > you are hereby notified that reading, disseminating, distributing or > copying this message is strictly > prohibited. If you have received this message by mistake, please > immediately notify us by > replying to the message and delete the original message and any copies > immediately thereafter. > > Thank you. > > ** > CLLD > -- Mark D Pace Senior Systems Engineer Mainline Information Systems
Re: zLinux OS disk read-only
The disk is defined as follows. This is an excerpt from the CP directory: IPL 200 . LINK RHMASTER 199 199 RR MDISK 200 3390 1 10016 LX53B5 M Unfortunately, the console log did not get spooled so I don't know what the log would have indicated for that disk when the guest machine came up. That's on my follow-up list. The guest machine is IPL'd off of its OS (disk 200) disk when it comes up (in its CP Directory) so I need to find a way to spool the console when it starts and not later after it has gone through its initialization. Thanks, Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of RPN01 Sent: Tuesday, March 01, 2011 2:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zLinux OS disk read-only How is the disk defined in the CP Directory entry (i.e. What is the mode of the disk), and what is in the console log when the user was logged in that could give a clue about the status of the disk when the user was initialized? The mode will tell you the condition(s) that could lead to it being read only (other users having it read/write or even read only), and the log may even tell you which or how many users gummed up the works, or when things when oval on you. In any case, it had to have happened at some point, and there has to be a footprint, if you keep your logs. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 2:23 PM, "Steve Perez" wrote: > Hello All, > > Has anyone run into a situation where the zLinux OS disk has become > READ- > > ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. > > My zLinux Admin were doing compares between the production environment > > versus the Test D/R environment and noticed it. He issued the > following > > on the prod zLinux guest environment: > > # mount -o remount,rw /dev/VolGroup01/LogVol00 > mount: block device /dev/VolGroup01/LogVol00 is write-protected, > mounting > > read-only > > Since we are testing our D/R process at the moment for the z/VM LPAR > we > > are unsure at this point whether that is a contributing factor. It > shoul d not be but we can't rule it out. We paused our PPRC/Global > mirroring fro m the z/OS side before starting the D/R activities to > perform recovery of > > the z/VM & z/Linux. The problem was found while in the middle of > verifying/comparing environments on the zLinux side. I can link to > the > > minidisk that is used to IPL that zLinux guest and it shows R/W when I > > issue Q LINKS. All other minidisks owned by that zLinux guest are R/W a > s > well. From my perspective (z/VM) all looks good. > > Any input would be appreciated, if anything to rule out that PPRC/GM > woul d have contributed to this. > > Thanks. > Steve. ** This message may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is legally privileged. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message and any copies immediately thereafter. Thank you. ** CLLD
Re: zLinux OS disk read-only
How is the disk defined in the CP Directory entry (i.e. What is the mode of the disk), and what is in the console log when the user was logged in that could give a clue about the status of the disk when the user was initialized? The mode will tell you the condition(s) that could lead to it being read only (other users having it read/write or even read only), and the log may even tell you which or how many users gummed up the works, or when things when oval on you. In any case, it had to have happened at some point, and there has to be a footprint, if you keep your logs. -- Robert P. Nix Mayo Foundation.~. RO-OC-1-18 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/1/11 2:23 PM, "Steve Perez" wrote: > Hello All, > > Has anyone run into a situation where the zLinux OS disk has become READ- > > ONLY access? We are running z/Linux under z/VM 5.4 Redhat 5.4. > > My zLinux Admin were doing compares between the production environment > > versus the Test D/R environment and noticed it. He issued the following > > on the prod zLinux guest environment: > > # mount -o remount,rw /dev/VolGroup01/LogVol00 > mount: block device /dev/VolGroup01/LogVol00 is write-protected, mounting > > read-only > > Since we are testing our D/R process at the moment for the z/VM LPAR we > > are unsure at this point whether that is a contributing factor. It shoul > d > not be but we can't rule it out. We paused our PPRC/Global mirroring fro > m > the z/OS side before starting the D/R activities to perform recovery of > > the z/VM & z/Linux. The problem was found while in the middle of > verifying/comparing environments on the zLinux side. I can link to the > > minidisk that is used to IPL that zLinux guest and it shows R/W when I > > issue Q LINKS. All other minidisks owned by that zLinux guest are R/W a > s > well. From my perspective (z/VM) all looks good. > > Any input would be appreciated, if anything to rule out that PPRC/GM woul > d > have contributed to this. > > Thanks. > Steve.
