From: Ming Zhang <mingz@ele.uri.edu>
To: Neil Brown <neilb@suse.de>
Cc: Rik Herrin <rikherrin@yahoo.com>, linux-raid@vger.kernel.org
Subject: Re: Controlling Reading and Writing in RAID 1 configuration
Date: Thu, 27 Apr 2006 21:31:52 -0400 [thread overview]
Message-ID: <1146187912.11547.211.camel@localhost.localdomain> (raw)
In-Reply-To: <17489.20083.873352.723996@cse.unsw.edu.au>
On Fri, 2006-04-28 at 09:06 +1000, Neil Brown wrote:
> On Thursday April 27, mingz@ele.uri.edu wrote:
> >
> > On Fri, 2006-04-28 at 08:04 +1000, Neil Brown wrote:
> > > On Tuesday April 25, rikherrin@yahoo.com wrote:
> > > > Hi,
> > > > I have a setup where I want to use RAID 1 to mirror
> > > > my data over the LAN. I am exposing 2x500 GB-sized
> > > > devices via iSCSI and was wondering if I could
> > > > configure the RAID 1 to write to both members of the
> > > > RAID 1 configuration but only read from one as one
> >
> > only read from one disk, shall this be a "--read-preferred" ?
>
> No. The one(s) you don't read from is the odd-one-out. The one(s)
> you read from are 'normal' and don't get a special flag.
>
> >
> > i checked email archive, but still not quite understand on this
> > "--write-mostly". for raid1, u anyway need to write all components, so
> > why there is a "mostly"?
> >
>
> Mostly it will just write to this device.
> But if all the non-write-mostly device fail, then it will read from
> this device. So it isn't write-only. It is write-mostly.
>
> Make sense?
i know why my English language test had that low score now.
thx!
>
> NeilBrown
prev parent reply other threads:[~2006-04-28 1:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 12:58 Controlling Reading and Writing in RAID 1 configuration Rik Herrin
2006-04-27 22:04 ` Neil Brown
2006-04-27 22:38 ` Ming Zhang
2006-04-27 23:06 ` Neil Brown
2006-04-28 1:31 ` Ming Zhang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1146187912.11547.211.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=rikherrin@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox