I share DASD all the time. Chris Little put it well:
The issue that goes beyond this is that Linux doesn't understand
shared devices. It can't synchronize writes at the OS level. ...
Right. Last I checked, the kernel cached blocks of data
for block devices (all disk, shared or not!)
I knew you were joking.
I was goof ing on your joking.
;)
-Original Message-
From: David Kreuter [EMAIL PROTECTED]
Sent: Jun 19, 2005 3:40 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD shared between SLES9s.(running on different z/VMs)
I know - I was just joking -
Bill Munson wrote
OpenGFS is known to work as well (at least on the 31bit releases).
You could ask IBM if they have any plans to bring GPFS or SAN FS to
linux on zSeries.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send
On 6/18/05, mainframe_s390 [EMAIL PROTECTED] wrote:
DEDICATE 1000 1000 ===Shared DASD between SLES9A and
SLES9B
You have a very big gun in your hands and it is pointing towards your
foot. This gives both sides simultaneous R/W access to the disk. I
don't think you want to do this. You have
: David Kreuter [EMAIL PROTECTED]
Sent: Jun 17, 2005 1:57 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD shared between SLES9s.(running on different z/VMs)
OK it's Friday I have to ask you Gordon: What's an IBM SE?
David
Wolfe, Gordon W wrote:
In certain circumstances, sharing a limited amount
maintenance.
munson
-Original Message-
From: David Kreuter [EMAIL PROTECTED]
Sent: Jun 17, 2005 1:57 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD shared between SLES9s.(running on different z/VMs)
OK it's Friday I have to ask you Gordon: What's an IBM SE?
David
Wolfe, Gordon W wrote
Hi,all
Thank you for many replies.
I want to use shared DASD(Address:1000 VOLSER:VL1000) for
file-system.
(Not raw device for Oracle RAC)
I defined the below definition to System Config file.
USER_VOLUME_LIST VL1000
RDEVICE 1000 TYPE DASD SHARED YES.
I defined the below definition to USER
Hi,all
I'm very in troubled.
Please teach me.
I want to use shared DASD.
The DASD(ADDRESS:1000) is used by two SLES9s.
SLES9s are running on different z/VMs.
(One SLES9-A is running on z/VM-A, the other SLES9-B is
running on z/VM-B.)
Firstly, can I do above scenario?
Thank you
-
K.M.
Sent: Friday, June 17, 2005 9:36 AM
To: LINUX-390@VM.MARIST.EDU
Subject: DASD shared between SLES9s.(running on different z/VMs)
Hi,all
I'm very in troubled.
Please teach me.
I want to use shared DASD.
The DASD(ADDRESS:1000) is used by two SLES9s.
SLES9s are running on different z/VMs.
(One SLES9
On 6/17/05, Post, Mark K [EMAIL PROTECTED] wrote:
When DASD is shared between LPARs it should be defined as SHARED in
the system configuration file. This disables MDC for the device, and
ensures you do not cache data that is written elsewhere.
If you want to share minidisks among z/VM systems you
:
Sent by: Linux onSubject: DASD shared between
SLES9s.(running on different z/VMs)
390 Port
ahoo.co.jp cc:
Sent by: Linux onSubject: DASD shared between
SLES9s.(running on different z/VMs)
390 Port
[EMAIL PROTECTED]
IST.EDU
: Friday, June 17, 2005 8:40 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD shared between SLES9s.(running on different z/VMs)
yes you can, no you shouldn't.
how are you going to ensure the integrity of your data if two SLES zLinux
are going after the same data?
even if you
-
From: Wolfe, Gordon W [mailto:[EMAIL PROTECTED]
Sent: Friday, June 17, 2005 11:03 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD shared between SLES9s.(running on different z/VMs)
In certain circumstances, sharing a limited amount of dasd read-write among
LPARs is possible using hardware
On 6/17/05, Rob van der Heij [EMAIL PROTECTED] wrote:
When DASD is shared between LPARs it should be defined as SHARED in
the system configuration file. This disables MDC for the device, and
ensures you do not cache data that is written elsewhere.
It's a possibe performance penalty to lose
--
From: Uriel Carrasquilla
Reply To: Linux on 390 Port
Sent: Friday, June 17, 2005 8:40 AM
To: LINUX-390@VM.MARIST.EDU
Subject:Re: DASD shared between SLES9s.(running on different z/VMs)
yes you can, no you shouldn't.
how are you going to ensure the integrity
onSubject: Re: DASD shared
between SLES9s.(running on different z/VMs)
390 Port
[EMAIL PROTECTED
system engineer?
-Original Message-
From: David Kreuter [mailto:[EMAIL PROTECTED]
Sent: Friday, June 17, 2005 12:57 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD shared between SLES9s.(running on different z/VMs)
OK it's Friday I have to ask you Gordon: What's an IBM SE?
David
Wolfe
|
| cc:
|
| Subject: Re: DASD shared between SLES9s.(running on different
z/VMs
: Friday, June 17, 2005 14:18 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD shared between SLES9s.(running on different z/VMs)
An SE is the software equivalent of a CE.
SE = Systems Engineer.
I think they are nearly extinct now as I haven't had a verifiable
sighting of one since 1984.
They used
You could ask IBM if they have any plans to bring GPFS or SAN FS to
linux on zSeries.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
21 matches
Mail list logo
