linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Paul Clements <paul.clements@steeleye.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: write only raid1
Date: Wed, 10 Nov 2004 11:13:18 -0500	[thread overview]
Message-ID: <1100103198.3190.68.camel@localhost.localdomain> (raw)
In-Reply-To: <41923A34.5000709@steeleye.com>

i now understand what you mean. i saw that async write operation and i
do not realize that is what u think write only.

so base on the patch, since i already know exactly that one device will
never be read. a simpler way might be

1) modify mdadm to allow one device to be configured as write only
2) add a write only flag in device info and check the flag when do read
balance.

so no need to update the time at all if no persistent bitmap purpose.

i saw the 2.4.x kernel raid has write only flag while dropped in 2.6.x.
i guess that is for reconstruction. but we can make use of that for this
purpose as well.

"write only" can be part of the async write or async replication. but i
think raid1 code should be able to allow write only to be a standalone
feature so others may have their own async write solution.

ming



On Wed, 2004-11-10 at 10:56, Paul Clements wrote:
> Ming Zhang wrote:
> > On Wed, 2004-11-10 at 10:05, Paul Clements wrote:
> > 
> >>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.
> >>
> > 
> > can u send me the patch then i can have a look?
> 
> my patches are here:
> 
> http://parisc-linux.org/~jejb/md_bitmap/
> 
> you're looking for the async write portion of the code, which has the 
> write-only functionality in it (later patches do not contain that code, 
> so look at the older ones)
> 
> check the mailing list archives for discussion
> 
> Peter's patch is here:
> 
> http://marc.theaimsgroup.com/?l=linux-raid&m=109238533827986&w=2
> 
> 
> --
> Paul


      reply	other threads:[~2004-11-10 16:13 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
2004-11-10 15:45   ` Ming Zhang
2004-11-10 15:56     ` Paul Clements
2004-11-10 16:13       ` 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=1100103198.3190.68.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=linux-raid@vger.kernel.org \
    --cc=paul.clements@steeleye.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;
as well as URLs for NNTP newsgroup(s).