From: Paul Clements <paul.clements@steeleye.com>
To: mingz@ele.uri.edu
Cc: Neil Brown <neilb@cse.unsw.edu.au>, linux-raid@vger.kernel.org
Subject: Re: write only raid1
Date: Wed, 10 Nov 2004 10:05:34 -0500 [thread overview]
Message-ID: <41922E3E.7050206@steeleye.com> (raw)
In-Reply-To: <1100096418.3190.4.camel@localhost.localdomain>
Ming Zhang wrote:
> is there any technical issue that lead not to be implemented?
No. In fact, it has been implemented. Both Peter T. Breuer and I have
come up with slightly different patches to implement the write only
functionality.
> is there any place to find previous discussion on this? i try the google
> but fail. i do no know which key word can find that. thx.
Try the archives of this mailing list:
http://marc.theaimsgroup.com/?l=linux-raid&r=1&w=2
This has been discussed a couple of times and patches have been posted
to the list in the past.
--
Paul
> On Thursday November 4, mingz@ele.uri.edu wrote:
>
>>Hi, folks?
>>
>>I would like to know if current RAID1 support or willing to support a
>>RAID1 with a write only device? For example, u can setup 2 disks to
>
> form
>
>>a raid1, you fork 2 writes to both disks while you only read from one.
>>this will be very useful for logging purpose or replication.
>
>
> This functionality has been discussed, but have not been implemented
> in a released kernel yet.
>
> NeilBrown
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2004-11-10 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 14:20 write only raid1 Ming Zhang
2004-11-10 15:05 ` Paul Clements [this message]
2004-11-10 15:45 ` Ming Zhang
2004-11-10 15:56 ` Paul Clements
2004-11-10 16:13 ` Ming Zhang
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=41922E3E.7050206@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=linux-raid@vger.kernel.org \
--cc=mingz@ele.uri.edu \
--cc=neilb@cse.unsw.edu.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.