Why don't you ATTACH the LPAR Linux volume's device address to your VM Linux guest? Then you should be able to dynamically add the address (using that /proc interface that I keep forgetting). Once you've done that, simply do a "mount" command. Oh, make sure that the filesystem is not mounted on the LPAR Linux.
Another possibility is to "read only" mount the LPAR volume to the LPAR linux, then use DD or z/OS to COPY the contents to another address, then do the above. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of James Melin > Sent: Friday, October 08, 2004 12:34 PM > To: [EMAIL PROTECTED] > Subject: Re: Moving an LPAR Linux to VM - Problem > > > I have a GBE. You thinking NFS mount them? > > Is there a way to just have z/OS native LPAR linux volumes > show up readable > by linux in VM? > > > > > > "Post, Mark K" > <[EMAIL PROTECTED] > m> > To > Sent by: Linux on [EMAIL PROTECTED] > 390 Port > cc > <[EMAIL PROTECTED] > IST.EDU> > Subject > Re: Moving an LPAR > Linux to VM - > Problem > 10/08/2004 11:46 > AM > > > Please respond to > Linux on 390 Port > <[EMAIL PROTECTED] > IST.EDU> > > > > > > > How much network bandwidth do you have between the Linux LPAR > and the Linux > Guest, compared to how much data you need to move? > > > Mark Post > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of James > Melin > Sent: Friday, October 08, 2004 8:45 AM > To: [EMAIL PROTECTED] > Subject: Moving an LPAR Linux to VM - Problem > > > Hello learned list members... got a good one for you. > > Once upon a time, when we first built Linux, we went with > LPAR mode because > this was strictly under the radar. I was given some disk, and > as it turns > out, our Storage Administrator at the time fat-fingered the > amount of space > for the 'mod-9' volumes, and we had 10116 cyl volumes instead > of 10016 cyl. > So my volumes were 100 cyl 'fat'. We found this out at a > Disaster recovery > exercise. > > Anyway, an attempted solution was to re-allocate the space > for the linux > partion to be slightly less than a real mod 9. 150250 tracks, > I believe. We > were still doing full volume backups on those because we > hadn't discovered > the 'tracks' option for dfsms. > > We have the following situation. 1) We cannot define the > 'fat' mod 9's to > VM. Or at least we don't know how. When we tried that with > one that was > empty, we were unable to get VM to recognized the disk with > 10116 cyls. > They > worked if we just told it they were 10016 cyls. That said, I > cannot simply > put those devices in the VM configuration and mount them for > copy of the > file system to new disk. > > Conversely, the Linux LPAR's are device restricted, in that > they cannot see > all of the disk farm. They are also on a different > mainframe(z/800 - VM on > z/900), though the disk is shared. I'm told dynamically > adding mod 9 disk > that z/VM knows about to the z/800 is not possible, so I > cannot mount those > volumes and do a disk copy. > > I attempted to do a 'tracks' backup of the disk volume to > just cover the > tracks where the z/linux file system was residing and then > restore it to > disk that VM can use via z/os. That didn't seem to work. I > didn't get a > mountable file system on the VM defined disk under a freshly > defined linux > guest. > > The only thing I can think of is try to find a mod 9 or two > that the z/800 > Lpar, and VM Lpar can all see, and do something like locally > mount the > mod-9, copy the file system and then attempt to mount it > under a vm linux > guest. > > If anyone else has an idea, I'm all ears. This pretty much > took my entire > day yesterday, trying different variations on this. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access > instructions, send email > to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO > LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO > LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
