linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Ian Dall <ian@beware.dropbear.id.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Proposed enhancement to mdadm:  Allow "--write-behind=" to be done in grow mode.
Date: Mon, 9 Jul 2007 11:30:21 +1000	[thread overview]
Message-ID: <18065.36781.477223.658707@notabene.brown> (raw)
In-Reply-To: message from Ian Dall on Tuesday July 3

On Tuesday July 3, ian@beware.dropbear.id.au wrote:
> There doesn't seem to be any designated place to send bug reports and
> feature requests to mdadm, so I hope I am doing the right thing by
> sending it here.

Yes. Exactly the right thing, thanks.

I have applied the patch and pushed it out into .git.  It will appear
in the next release of mdadm.

Thank,
NeilBrown

> 
> I have a small patch to mdamd which allows the write-behind amount to be
> set a array grow time (instead of currently only at grow or create
> time). I have tested this fairly extensively on some arrays built out of
> loop back devices, and once on a real live array. I haven't lot any data
> and it seems to work OK, though it is possible I am missing something.
> 
> --- mdadm-2.6.1/mdadm.c.writebehind	2006-12-21 16:12:50.000000000 +1030
> +++ mdadm-2.6.1/mdadm.c	2007-06-30 13:16:22.000000000 +0930
> @@ -827,6 +827,7 @@
>  			bitmap_chunk = bitmap_chunk ? bitmap_chunk * 1024 : 512;
>  			continue;
>  
> +		case O(GROW, WriteBehind):
>  		case O(BUILD, WriteBehind):
>  		case O(CREATE, WriteBehind): /* write-behind mode */
>  			write_behind = DEFAULT_MAX_WRITE_BEHIND;
> 
> 
> -- 
> Ian Dall <ian@beware.dropbear.id.au>

      parent reply	other threads:[~2007-07-09  1:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 13:52 Does "--write-behind=" have to be done at create time? Ian Dall
2007-06-29 15:28 ` Ian Dall
2007-07-03 13:12   ` Proposed enhancement to mdadm: Allow "--write-behind=" to be done in grow mode Ian Dall
2007-07-03 14:03     ` David Greaves
2007-07-04  2:30       ` Ian Dall
2007-07-04 13:45         ` Bill Davidsen
2007-07-05 15:37         ` Bill Davidsen
2007-07-09  1:30     ` Neil Brown [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=18065.36781.477223.658707@notabene.brown \
    --to=neilb@suse.de \
    --cc=ian@beware.dropbear.id.au \
    --cc=linux-raid@vger.kernel.org \
    /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).