All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Hardy <mhardy@h3c.com>
To: linux-raid@vger.kernel.org
Subject: Re: [PATCH md 9 of 9] Optimise reconstruction when re-adding a recently failed drive.
Date: Thu, 17 Feb 2005 16:51:27 -0800	[thread overview]
Message-ID: <42153C0F.1030904@h3c.com> (raw)
In-Reply-To: <E1D1wCK-0000Xe-Qm@notabene.cse.unsw.edu.au>


NeilBrown wrote:
> When an array is degraded, bit in the intent-bitmap are
> never cleared. So if a recently failed drive is re-added, we only need
> to reconstruct the block that are still reflected in the
> bitmap.
> This patch adds support for this re-adding.

Hi there -

If I understand this correctly, this means that:

1) if I had a raid1 mirror (for example) that has no writes to it since 
a resync
2) a drive fails out, and some writes occur
3) when I re-add the drive, only the areas where the writes occurred 
would be re-synced?

I can think of a bunch of peripheral questions around this scenario, and 
bad sectors / bad sector clearing, but I may not be understanding the 
basic idea, so I wanted to ask first.

-Mike

  reply	other threads:[~2005-02-18  0:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18  0:40 [PATCH md 0 of 9] Introduction NeilBrown
2005-02-18  0:40 ` [PATCH md 6 of 9] Improve the interface to sync_request NeilBrown
2005-02-18  0:40 ` [PATCH md 1 of 9] Remove possible oops in md/raid1 NeilBrown
2005-02-18  0:40 ` [PATCH md 9 of 9] Optimise reconstruction when re-adding a recently failed drive NeilBrown
2005-02-18  0:51   ` Mike Hardy [this message]
2005-02-18  0:58     ` Neil Brown
2005-02-18  0:40 ` [PATCH md 4 of 9] Merge md_enter_safemode into md_check_recovery NeilBrown
2005-02-18  0:40 ` [PATCH md 2 of 9] Make raid5 and raid6 robust against failure during recovery NeilBrown
2005-02-18  0:40 ` [PATCH md 7 of 9] Optimised resync using Bitmap based intent logging NeilBrown
2005-02-18  0:40 ` [PATCH md 5 of 9] Improve locking on 'safemode' and move superblock writes NeilBrown
2005-02-18  0:40 ` [PATCH md 8 of 9] raid1 support for bitmap intent logging NeilBrown
2005-02-18  0:40 ` [PATCH md 3 of 9] Remove kludgy level check from md.c NeilBrown
2005-02-18 14:25 ` [PATCH md 0 of 9] Introduction Phantazm
2005-02-20 22:55   ` 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=42153C0F.1030904@h3c.com \
    --to=mhardy@h3c.com \
    --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 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.