mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@redhat.com>
To: <gaby@applianceware.com>
Cc: <torvalds@transmeta.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] for Multiple Device driver - md.c (kernel 2.4.12)
Date: Fri, 12 Oct 2001 02:23:21 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0110120220290.7954-100000@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110111801490.1143-100000@gaby.applianceware.com>


On Thu, 11 Oct 2001 gaby@applianceware.com wrote:

> Suppose you can hot-swap a hard disk in a system. Now if you have a
> degraded Software RAID device (for example a RAID-5 with one disk
> failed) and you replace the failed disk on-the-fly you cannot start
> reconstruction (with raidhotadd) of the Software RAID device with the
> replaced disk because it says it is BUSY.

this is possible already: you should first raidhotremove the failed drive,
then raidhotadd the new drive. It can be the 'same' drive if it's a
hot-swap disk, or it can be another, spare disk.

> +	if (rdev && rdev->faulty) {
> +		err = hot_remove_disk(mddev, dev);

what your patch does is a forced remove of any drive that is
raidhotadd-ed. This is less finegrained than the current solution, and
might make the method more volatile. (easier to mess up accidentally.) Is
there anything your patch allows that is not possible today, via
raidhotremove+raidhotadd?

	Ingo


  reply	other threads:[~2001-10-12  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12  1:23 gaby
2001-10-12  6:23 ` Ingo Molnar [this message]
2001-10-12 19:09   ` Jean-Gabriel Rican

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=Pine.LNX.4.33.0110120220290.7954-100000@devserv.devel.redhat.com \
    --to=mingo@redhat.com \
    --cc=gaby@applianceware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®