Non System z question

[Martha McConaghy]

Sorry to bring up something that is not related to System z, but we are
stumped and I hope someone on this list might have some helpful information.

We have RHEL 5 running on a p550 in several LPARs.  The LUNs for these systems
reside on a storage device that is going away, so I'm moving them to an IBM
SVC.  I've followed the process to move them from an image mode Vdisk to a
managed Vdisk on the SVC.  I can confirm that the process works because I
mapped one of the new disks to another Linux running on a different platform
and we can read the data on it, see the partitions, files, etc.
However, when the disk is mapped to the p550 and attached to the LPAR via VIO,
the data seems to get corrupted.  An AIX formatted label ends up on the disk
and it is unusable.  Even if we remove it from the p550 and map it to a
different system, the disk is still unusable.

I was just wondering if anyone of you have ever run Linux in this type of
configuration (on a p550 with VIO) and have any idea what is happening?  I
suspect that VIO is initializing the disk, but another person is doing that
work and she doesn't know why this is happening.  (I really don't know
anything about pSeries.)

Anyone have any suggestions?


Martha

--
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/

Re: Non System z question

[David Boyes]

 I was just wondering if anyone of you have ever run Linux in this type
 of
 configuration (on a p550 with VIO) and have any idea what is happening?
 I
 suspect that VIO is initializing the disk, but another person is doing
 that
 work and she doesn't know why this is happening.  (I really don't know
 anything about pSeries.)
 
 Anyone have any suggestions?

Check the ucode level of the VIO subsystem on the HMC for the p550 with IBM. 
There were issues in the past with VIO requiring AIX labels and helpfully 
providing them if they weren't present. Also verify that the AIX system has the 
Linux compatibility packages loaded, and that the filesystem being used on the 
volume on the Linux side is ext2. The AIX Linux-friendly code doesn't 
understand anything else very well and tends to assume that if it doesn't 
understand it, it's blank. 

--
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/