The problem was a the dev_loss_tmo. It using the default causing the read only issue. The correct dev_loss_tmo is 120 solving the problem.
Thanks for your help Robert, Sam and Gregory. Victor Echavarry System Programmer, EVERTEC LLC -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz Powiedziuk Sent: Wednesday, January 21, 2015 12:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: relocation put read only FCP What Robert said might be correct. The other thing I would check if that won't help is: - hosts definition on the XIV and Zonning in SAN switches When you relocate virtual machine from one LPAR to another you are also switching FCP channels under the hood for the relocated linux guest. Which means your linux guest after the reloctation will talk to the XIV from different FCP channels with different WWPNs. XIV must have these new WWPN in the host deffinition for this guest (LUN Masking). Also zone definitions in SAN Switches have to contain "new" WWPNs. Regards Gregory Powiedziuk 2015-01-21 9:43 GMT-05:00 Victor Echavarry Diaz <vechava...@evertecinc.com>: > This is a multi-part MIME message. > > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > > We are doing relocation testing under z/VM 6.3. We test a SLES 11SP2 > and o= racle 10.2. We bring up on both z/vm LPARS in standalone way > and works fine= on both LPARS. When we begin relocation from any of > the LPAR, immediately = the SAN file system goes in read only mode. > I'm attaching part of the log a= t the moment of failure. The SAN is a > XIV We are running z/VM 6.3. > > Thanks for your help > > Victor Echavarry > System Programmer, EVERTEC LLC > > > > > > WARNING: This email and any files transmitted with it are confidential > and intended solely for the use of the individual or entity to whom > they are addressed. If you have received this email in error please > delete it immedi= ately. > Please note that any views or opinions presented in this email are > solely t= hose of the author and do not necessarily represent those of > EVERTEC, Inc. or its affiliates. Finally, the integrity and security > of this message cannot be guaranteed on the Internet, and as such > EVERTEC, Inc. and its affiliates ac= cept no liability for any damage > caused by any virus transmitted by this email. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ WARNING: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of EVERTEC, Inc. or its affiliates. Finally, the integrity and security of this message cannot be guaranteed on the Internet, and as such EVERTEC, Inc. and its affiliates accept no liability for any damage caused by any virus transmitted by this email.
