From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n6SDpHHt005819 for ; Tue, 28 Jul 2009 09:51:17 -0400 Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id n6SDotAK025103 for ; Tue, 28 Jul 2009 09:50:55 -0400 Received: by ey-out-2122.google.com with SMTP id 9so11410eyd.39 for ; Tue, 28 Jul 2009 06:50:55 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <52F0ADF3-B499-4EE4-BDA1-B8DED2C9BD42@karlsbakk.net> References: <29ae894c0907260312m3b2ffb2ex5cbef456f3c49bee@mail.gmail.com> <20090727135628.GA3782@us.ibm.com> <52F0ADF3-B499-4EE4-BDA1-B8DED2C9BD42@karlsbakk.net> Date: Tue, 28 Jul 2009 15:50:54 +0200 Message-ID: <29ae894c0907280650h4dc525bbn4a808366ae8935cb@mail.gmail.com> Subject: Re: [linux-lvm] Mirroring implementation From: brem belguebli Content-Type: multipart/alternative; boundary=0016e64be264063df0046fc45c1a Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: LVM general discussion and development --0016e64be264063df0046fc45c1a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Roy, I would be better indeed, but practically, even if it is supposed to reques= t both disks (san arrays) in //, the closest array will almost always be the first to answer unless it is overloaded. What I'm looking for is the behaviour for writes, as I don't want to deal with failure scenarios in which I could find outdated data on my last remaining mirror leg. 2009/7/28, Roy Sigurd Karlsbakk : > > On 27. juli. 2009, at 15.56, malahal@us.ibm.com wrote: > > It writes in parallel. Reads from a single device (switches on a device >> failure only). >> > > > Wouldn't it be better to read in parallel, from different places? I've > heard some controllers can do this, so that the reading will be somehow l= ike > reading from a RAID-0 stripe. > > roy > -- > Roy Sigurd Karlsbakk > (+47) 97542685 > roy@karlsbakk.net > http://blogg.karlsbakk.net/ > -- > I all pedagogikk er det essensielt at pensum presenteres intelligibelt. D= et > er et element=E6rt imperativ for alle pedagoger =E5 unng=E5 eksessiv anve= ndelse av > idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvat= e > og relevante synonymer p=E5 norsk. > > > _______________________________________________ > linux-lvm mailing list > linux-lvm@redhat.com > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > --0016e64be264063df0046fc45c1a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Roy,
=A0
I would be better indeed, but practically, even if it is supposed to r= equest both disks (san arrays) in //, the closest array=A0 will almost alwa= ys be the first to answer unless it is overloaded.
=A0
What=A0I'm looking for is the behaviour=A0for writes, as I don'= ;t want=A0to deal with failure scenarios in which I could find outdated dat= a on=A0my last remaining mirror leg.
=A0
=A0

=A0
2009/7/28, Roy Sigurd Karlsbakk <roy@karlsbakk.net>:
On 27. juli. 2= 009, at 15.56, malahal@us.ibm.com= wrote:

It writes in parallel. Reads fro= m a single device (switches on a device
failure only).


Wouldn't it be better to read in parallel, from differen= t places? I've heard some controllers can do this, so that the reading = will be somehow like reading from a RAID-0 stripe.

roy
--
Roy Sigurd Karlsbakk
(+47) 97542685
roy@karlsbakk.net
http:/= /blogg.karlsbakk.net/
--
I all pedagogikk er det essensielt at pensum prese= nteres intelligibelt. Det er et element=E6rt imperativ for alle pedagoger = =E5 unng=E5 eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fl= este tilfeller eksisterer adekvate og relevante synonymer p=E5 norsk.=20



____________= ___________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.r= edhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

--0016e64be264063df0046fc45c1a--