All of lore.kernel.org
 help / color / mirror / Atom feed
From: "spren.gm@gmail.com" <spren.gm@gmail.com>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: about faulty spare-disk interrupts synchronization
Date: Wed, 23 Dec 2009 19:51:33 +0800	[thread overview]
Message-ID: <200912231951301400282@gmail.com> (raw)

Hi,
Is it intended that when a spare disk status gets faulty (detached from raid or really faulty) 
synchronization is interrupted ? We found that case several days ago with kernel version of 2.6.24, 
after we unplugged a spare disk of a raid5 which had bitmap and was recovering, the spare disk 
status became faulty  and synchronization restarted from 0%. 

Looking into the md code, i find that in md/md.c/md_error(), it doesn't make a difference between 
spare disks and normal disks. Should we make a faulty spare disk not interrupt raid synchronization ?
Disks nowadays have become much larger, and recovering one disk may cost several hours or even longer.

--------------
spren.gm@gmail.com
2009-12-23


             reply	other threads:[~2009-12-23 11:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23 11:51 spren.gm [this message]
2009-12-23 23:31 ` about faulty spare-disk interrupts synchronization 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=200912231951301400282@gmail.com \
    --to=spren.gm@gmail.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.