: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
From: Ward, Mike S mw...@ssfcu.org
Subject: Re: initializing z/Linux disks
In-Reply-To:
Ad7457cbb6214164aa8715a5f0e19d8102ce22e3...@msgcmsv21023.ent.wfb.bank.corp
Content-Type: text/plain; charset=us-ascii
I thought
Ah, but while that was true of a ³real² 3390, is that also now true of
emulated 3390¹s which are split across varying numbers of essentially SCSI
disks? A single 3390 mod 27 might be split up over several 9 gig physical
disks in order to implement the emulation. Is the controller smart enough to
On 3/26/2010 at 12:44 PM, RPN01 nix.rob...@mayo.edu wrote:
Is the controller smart enough to
be able to start an I/O to each, even though the I/O*s were sent to the same
3390 address?
It might be, but CP and Linux are not, so the waters aren't all that muddy
after all. We really don't want
But just to push things a bit further, isn't PAV the key to getting into the
rat's nest successfully? If a volume has PAV aliases, then CP can start more
than one I/O on the volume at a time. And, if it is sufficiently broken into
smaller minidisks, then Linux can take advantage of the PAV paths
On Friday, 03/26/2010 at 12:45 EDT, RPN01 nix.rob...@mayo.edu wrote:
Ah, but while that was true of a ?real? 3390, is that also now true of
emulated
3390?s which are split across varying numbers of essentially SCSI disks?
A
single 3390 mod 27 might be split up over several 9 gig physical
On Friday, 03/26/2010 at 12:26 EDT, Schuh, Richard rsc...@visa.com
wrote:
As evidenced by the statements in the post repeated below, there is
discussion
of the offset from real cylinder 0 to real cylinder 1. That implies a
protected
cylinder 0 and necessitates CCW translation, does it not?
On Wednesday, 03/24/2010 at 04:31 EDT, David Boyes dbo...@sinenomine.net
wrote:
On 3/24/10 3:40 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
When giving guests access to real cyl 0, I suggest:
1. If using a full-pack mindisk, use the DEVNO version instead of
volser.
That way it
Another point I¹ve not seen mentioned, and I¹m not sure if it¹s true or
not...
Given a dedicated volume to a Linux guest, won¹t the guest start only one
I/O to the device at a time, and wait for it to complete? If you break up a
larger volume into several minidisks (like a mod 27 into mod 9¹s)
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: initializing z/Linux disks
On Wednesday, 03/24/2010 at 04:51 EDT, Ward, Mike S
mw...@ssfcu.org
wrote:
I thought there was overhead in specifying it as a minidisk rather
than a dedicated full disk. The overhead would be in the
translation
You know the old virtualization saying, Never depend on the kindness
of
guests.
Alan Altmark
One might be entertaining angels unaware...8-)
There is maybe some misunderstanding: (leaving out PAV a while) a device can
handle only 1 IO at a time, guests know that, CP too. So indeed a linux
will not send a new IO if the previous one to that disk hasn't ended yet,
the guets will queue it. With several guests with minidisks on the same
On Thursday, 03/25/2010 at 12:11 EDT, Schuh, Richard rsc...@visa.com
wrote:
With it not being a full-pack as Mike mentioned in his post, there would
always
have to be CCW translation, would there not? The question is whether
that is a
significant hit compared to the full pack including
On Thursday, 03/25/2010 at 11:45 EDT, RPN01 nix.rob...@mayo.edu wrote:
Another point I?ve not seen mentioned, and I?m not sure if it?s true or
not...
Given a dedicated volume to a Linux guest, won?t the guest start only
one I/O
to the device at a time, and wait for it to complete? If you
Hi
I have a question. What I have been doing up to this point for a new
z/Linux guest build is, not necessarily in this order and does not
necessarily include all steps but,
Crave out the DASD for the z/Linux guest
Init the DASD using CPFMTXA putting a label on the disk
@LISTSERV.UARK.EDU
Subject: initializing z/Linux disks
Hi
I have a question. What I have been doing up to this point for a new
z/Linux guest build is, not necessarily in this order and does not
necessarily include all steps but,
Crave out the DASD for the z/Linux guest
Init the DASD using
...@cms.hhs.gov
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
03/24/2010 12:53 PM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
initializing z/Linux disks
Hi
I have a question. What I have been doing up
Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Mike Walter
Sent: Wednesday, March 24, 2010 2:12 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: initializing z/Linux disks
Use LXFMT from z/VM, no need to reformat the disk under Linux.
Mike Walter
Hewitt
On 3/24/10 1:53 PM, Martin, Terry R. (CMS/CTR) (CTR)
terry.mar...@cms.hhs.gov wrote:
Hi
I have a question. What I have been doing up to this point for a new z/Linux
guest build is, not necessarily in this order and does not necessarily include
all steps but,
Crave out the DASD for
...@listserv.uark.edu] On Behalf
Of David Boyes
Sent: Wednesday, March 24, 2010 11:20 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: [IBMVM] initializing z/Linux disks
On 3/24/10 1:53 PM, Martin, Terry R. (CMS/CTR) (CTR)
terry.mar...@cms.hhs.gov wrote:
Hi
I have a question. What I have been doing
On 3/24/10 2:40 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote:
You can DEDICATE by label rather than by real address.
But I still don't like Linux having cyl 0 :)
Nice to know. I'd missed that in the help files. Still, safer to let CP and
z/OS duke that one out, and let Linux get on
Terry -- You have to init the DASD when using minidisks- using CPFMTXA to
put a label on -- and you also want to format cylinder 0 to ensure it's seen
as a CP volume. When the zLinux guest does an 'init' -- it is doing a
format of the whole disk - not just an 'init' and label. You can
On Wednesday, 03/24/2010 at 03:22 EDT, David Boyes dbo...@sinenomine.net
wrote:
On 3/24/10 2:40 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com
wrote:
You can DEDICATE by label rather than by real address.
But I still don't like Linux having cyl 0 :)
Nice to know. I'd missed that in the
On 3/24/2010 at 03:38 PM, Scott Rohling scott.rohl...@gmail.com wrote:
I'm not sure how DFDSS reacts to Linux formatted volumes, offhand .. it
does fine with CPVOL volumes and minidisks.
It looks like a regular OS volume with no free space on it. That was the whole
reason the CDL was
and 0x0300 are the
outcome.
Thanks
From:
Scott Rohling scott.rohl...@gmail.com
To:
IBMVM@LISTSERV.UARK.EDU
Date:
03/24/2010 02:39 PM
Subject:
Re: initializing z/Linux disks
Sent by:
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
Terry -- You have to init the DASD when using minidisks- using
z/OS duke that one out, and let Linux get on with doing useful stuff.
When giving guests access to real cyl 0, I suggest:
1. If using a full-pack mindisk, use the DEVNO version instead of volser.
That way it doesn't matter if the guest changes the label.
Unless you use mirroring and move to
why would you do that rather than use minidisks
Just curious, if XRC is wanted, VM doesn't timestamp I/Os, but linux does?
If you use dedicates, isn't the data movers happier?
only a wee bit happier for the cyl 0 VM writes on. Linux will still timestamp
on minidisks. and if you
On Wednesday, 03/24/2010 at 04:51 EDT, Ward, Mike S mw...@ssfcu.org
wrote:
I thought there was overhead in specifying it as a minidisk rather than
a dedicated full disk. The overhead would be in the translation of the
I/O addresses and such. You know like linux reading cyl 0 when it's
really
@LISTSERV.UARK.EDU
Subject: Re: initializing z/Linux disks
Terry -- You have to init the DASD when using minidisks- using CPFMTXA
to put a label on -- and you also want to format cylinder 0 to ensure
it's seen as a CP volume. When the zLinux guest does an 'init' -- it
is doing a format
28 matches
Mail list logo
