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" <[email protected]> To: [email protected] 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:[email protected]] On Behalf Of Kris Buelens Sent: Tuesday, March 01, 2011 3:36 PM To: [email protected] 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 <[email protected]> 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 <[email protected]> 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:[email protected]] On >>Behalf >>Of RPN01 >>Sent: Tuesday, March 01, 2011 2:33 PM >>To: [email protected] >>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" <[email protected]> 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 > > > > > > > -- Kris Buelens, IBM Belgium, VM customer support
