linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Jeff Breidenbach <jeff@jab.org>
Cc: Brett Maton <Brett.Maton@simplyhealth.co.uk>, linux-raid@vger.kernel.org
Subject: Re: mdadm break / restore soft mirror
Date: Thu, 13 Dec 2007 15:16:08 +1100	[thread overview]
Message-ID: <18272.45576.359862.395170@notabene.brown> (raw)
In-Reply-To: message from Jeff Breidenbach on Wednesday December 12

On Wednesday December 12, jeff@jab.org wrote:
> 
> >If you can be certain that the device that you break out of the mirror
> >is never altered, then you could add an internal bitmap while the
> >array is split and the rebuild will go much faster.
> 
> Is this also a viable speedup for the "kep rotating backup drives through
> the array" strategy? If so, how much speedup are we talking about? Assume
> the array changes by 1% before a backup drive gets rotated in again.
> 

Not really...

The bitmap only records areas of the array that have changed since one
particular moment in time.  For rotating backs you would really want
several moments in time.
Whenever the array is non-degraded, the bitmap forgets any old state.

What you could do is set the number of devices in the array to 3 so
they it always appears to be degraded, then rotate your backup drives
through the array.  The number of dirty bits in the bitmap will
steadily grow and so resyncs will take longer.  Once it crosses some
threshold you set the array back to having 2 devices to that it looks
non-degraded and clean the bitmap.  Then each device will need a full
resync after which you will get away with partial resyncs for a while.

Not ideal, but it might work.

If 1% changes each time, then you will initially get a 100 fold
speedup, dropping away after that.

NeilBrown

  reply	other threads:[~2007-12-13  4:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 22:08 mdadm break / restore soft mirror Brett Maton
2007-12-12 22:27 ` Richard Scobie
2007-12-13  1:19 ` Neil Brown
2007-12-13  4:00   ` Jeff Breidenbach
2007-12-13  4:16     ` Neil Brown [this message]
2007-12-14  7:40       ` Jeff Breidenbach
2007-12-14  9:08         ` Neil Brown
2007-12-14 19:13           ` Jeff Breidenbach
2007-12-14 19:52             ` Jeff Breidenbach
2007-12-13 22:45 ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2007-12-13  7:02 Brett Maton
2007-12-14  0:04 ` Neil Brown

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=18272.45576.359862.395170@notabene.brown \
    --to=neilb@suse.de \
    --cc=Brett.Maton@simplyhealth.co.uk \
    --cc=jeff@jab.org \
    --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).