> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
> Behalf Of Marcy Cortes
> Sent: Friday, April 06, 2007 4:32 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Pros/Cons of FCP connection DASD
>
>
> >"SAN is cheaper"
On 4/6/07, Marcy Cortes <[EMAIL PROTECTED]> wrote:
This one I don't quite get? If I'm using the same DS8000, why would it
be cheaper? Unless you are saying you have more options to purchase
other things than just the same old IBM, EMC, HDS stuff.
I believe the perceived difference is in staff
> >"SAN is cheaper" -- I don't usually pay attention to the bills. I'm
an
> >engineer. But from what I hear management and others saying, SAN
will
> >save us a lot.
>
> This one I don't quite get? If I'm using the same DS8000, why would it
> be cheaper? Unless you are saying you have more opti
On Fri, 2007-04-06 at 16:31 -0500, Marcy Cortes wrote:
> >"SAN is cheaper" ...
>
> This one I don't quite get? If I'm using the same DS8000, why would it
> be cheaper?
I can think of one way...
If you want to do multipath I/O, for ECKD disk that's PAV and will cost
you extra for the PAV licensin
>"SAN is cheaper" -- I don't usually pay attention to the bills. I'm an
>engineer. But from what I hear management and others saying, SAN will
>save us a lot.
This one I don't quite get? If I'm using the same DS8000, why would it
be cheaper? Unless you are saying you have more options to purch
> What about having zLinux take ownership of an existing AIX or Windows
or
> Solaris filesystem?
R/O access to Windows NTFS and FAT, no problem. R/W is a bit more
experimental.
AIX and Solaris: depends on what filesystem was used on the AIX/Solaris
systems. Zfs on Solaris isn't supported (yet --
systems sharing have read
only access, unless you use a cluster filesystem.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
David Boyes
Sent: Friday, April 06, 2007 10:49 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Pros/Cons of FCP connection DASD
You will have
k you.
David Boyes <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port
04/06/2007 10:51 AM
Please respond to
Linux on 390 Port
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: Pros/Cons of FCP connection DASD
You will have problems if any system writes to a shared filesystem.
The
> buf
You will have problems if any system writes to a shared filesystem.
The
> buffering in Unix, Linux and Windows will make a filesystem
inconsistent
> unless the filesystem has some kind of clustering support built in.
Thus the comment on coordinating access...
> You still
> need to coordinate acc
Lionel asked:
> You mentioned sharing the SAN with Windows, AIX, ... - I assume you just
> mean sharing the SAN and not sharing a common filesystem - or do you
mean
> that zLinux can share the same filesystem (data) as AIX?
No I mean sharing the filesystems, not just the pool or storage
subsyste
] Behalf Of
David Boyes
Sent: Friday, April 06, 2007 8:39 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Pros/Cons of FCP connection DASD
> Richard - thank you for your very thoughtful and helpful analysis.
Right
> now all I have is 'mainframe' DASD available to my z/VM environment
but
&g
John asked:
> can you elaborate a little on you avoid putting " WWPN+LUN addressing to
> the initial RAMDISK"? Is your home-grown script run by CMS
> pre-Linux-boot or run by Linux early during Linux boot?
Runs in Linux. It is not a CMS program, but reads one or more CMS files.
For SuSE, it r
> Richard - thank you for your very thoughtful and helpful analysis.
Right
> now all I have is 'mainframe' DASD available to my z/VM environment
but
> I've had IBM and others pushing to get access to the SAN.
You'll want that, if for no other reason than it lets you get access to
all that overallo
the sender immediately by reply e-mail and delete
the e-mail from your system.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Troth
Sent: Friday, April 06, 2007 10:51 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Pros/Cons of FCP connection DASD
Richard - thank you for your very thoughtful and helpful analysis. Right
now all I have is 'mainframe' DASD available to my z/VM environment but
I've had IBM and others pushing to get access to the SAN.
You mentioned sharing the SAN with Windows, AIX, ... - I assume you just
mean sharing the SA
Great question, Lionel.
pro:
SAN looks the same to all platforms which use it
SAN connects to mainframe Linux as easily as to other Unix and Linux
SAN eliminates unused emulation
SAN is cheaper
"SAN looks the same" -- If you DDR a 3390 from one system to another, you
get a perfect copy. Nice!
So we can tell our IBM rep when we order those additional processors to
'Book 'em, Danu!'
(sorry. It had to be said.)
-Original Message-
From: "Jim Elliott <[EMAIL PROTECTED]>" <[EMAIL PROTECTED]>
To: "LINUX-390@VM.MARIST.EDU"
Sent
On Mon, 26 Mar 2007 16:37:39 -0800
barton <[EMAIL PROTECTED]> wrote:
> I don't understand - where would an installation with many linux servers get
> SCSI I/O
> information that identifies a device response time and shows delays
> associated with that
> I/O? I/O statistics are "nice", but how a
I don't understand - where would an installation with many linux servers get
SCSI I/O
information that identifies a device response time and shows delays associated
with that
I/O? I/O statistics are "nice", but how are they helpful?
Ingo Adlung wrote:
That's somewhat outdated information a
> Even this info. is dated. There are considerable differences
> between the FCP firmware for Ficon Express 2 on Trex, and the
> firmware for Ficon Express 2 on Danu.
To translate: Trex = z990 and Danu = z9 EC
Jim
--
For LINUX-3
Linux on 390 Port wrote on 03/26/2007 04:52:17
PM:
> That's somewhat outdated information at least for SLES 9 & 10.
> We have Linux I/O statistics for FCP/SCSI and shortly we'll have
> FCP adapter I/O statistics, too.
>
> It is true that ECKD attached disks provide QoS features like
> end-to-en
That's somewhat outdated information at least for SLES 9 & 10.
We have Linux I/O statistics for FCP/SCSI and shortly we'll have
FCP adapter I/O statistics, too.
It is true that ECKD attached disks provide QoS features like
end-to-end data protection and is the dominant I/O attachment
for Linux. It
When performance is bad, do you want to know why? Until we know how to show when the SAN
is impacting your application and how - do you want to trust your production to something
where performance is not manageable?
For example, an ibm controller was benchmarked first as eckd, then as scsi. on ec
Depending on the size of your shop, but money is a consideration in
smaller shops.
i.e. You already have ficon attached dasd with twin ficon cards.
Now you need another pair of FCP cards (at how much per card), and FCP
attached dasd (lparing your current DS6800 orr DS8000, or a separate
dasd sub
-Lionel B. Dyck wrote: -
>I've heard several good reasons to have my zlinux images use dasd
>that is on the fibre connected san and a few for using the old
>tried and true dasd. What I'd like to find out is what is true and
>what isn't - basically what is considered the best practice for
>
>>> On Mon, Mar 26, 2007 at 12:09 PM, in message
<[EMAIL PROTECTED]>, "Lionel B.
Dyck" <[EMAIL PROTECTED]> wrote:
> I've heard several good reasons to have my zlinux images use dasd that is
> on the fibre connected san and a few for using the old tried and true
> dasd. What I'd like to find out
The biggest point in favor of the 3390 style DASD is that the 3990
(emulated) takes care of the mirroring and multipathing for me, where the
FCP SAN disk is not mirrored or multipathed unless I do it myself in Linux.
You may gain some file transfer speed, but you pay for it in CPU.
--
.~.
Linux on 390 Port wrote on 03/26/2007 12:09:58
PM:
> I've heard several good reasons to have my zlinux images use dasd that
is
> on the fibre connected san and a few for using the old tried and true
> dasd. What I'd like to find out is what is true and what isn't -
basically
> what is consi
In my view it depends on what you need:
- a few very large disks, go for FCP
FCP luns can't be suballocated (as far as I know), so wanting a lot of
small ones won't give you any fun with the storage admin.
- lots of small disks, go for old style ECKD
LVMing lots of ECKD disks to get a large alloc
I've heard several good reasons to have my zlinux images use dasd that is
on the fibre connected san and a few for using the old tried and true
dasd. What I'd like to find out is what is true and what isn't - basically
what is considered the best practice for zlinux dasd.
Thus - what do y'all t
30 matches
Mail list logo
