All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Brad Campbell <lists2009@fnarfbargle.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Couple of questions.
Date: Sun, 10 Apr 2011 18:02:54 +1000	[thread overview]
Message-ID: <20110410180254.5d59696a@notabene.brown> (raw)
In-Reply-To: <4DA08600.5020604@fnarfbargle.com>

On Sun, 10 Apr 2011 00:14:56 +0800 Brad Campbell <lists2009@fnarfbargle.com>
wrote:

> 1 - When adding 2 missing disks to a RAID-6 (let's say a 4 drive RAID-6 
> that was created with only 2 disks initally) why does it sync the first, 
> then sync the second rather than doing both together?
>   ie mdadm --add /dev/md0 /dev/sd[ab]

Because the devices are added one at a time and between the moment when sda
is added and when sdb is added a recovery starts.

mdadm should write 'frozen' the 'sync_action' before adding the devices, and
then 'idle' after adding them both.  But it doesn't yet.
You could...
  echo frozen > /sys/block/md0/md/sync_action
  mdadm /dev/md0 --add /dev/sd[ab]
  echo idle > /sys/block/md0/md/sync_action

NeilBrown


> 
> 2 - If a drive disappears how do I remove it from an array.
>   Let's say I have a 10 drive RAID-6 that has an odd error on a disk. 
> The disk goes away (sdl), the disk comes back as sdq as md is still 
> hanging on to the name sdl. I add sdq to the array, but I can't remove 
> sdl as it physically no longer exists. udev has removed the device node 
> and mdadm can't remove it from the array as it can't tell what it was.
> 
> Like this :
> Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
> md0 : active raid6 sdq[10] sdc[0] sdd[6] sdl[1](F) sdh[9] sda[8] sde[7] 
> sdg[5] sdb[4] sdf[3] sdm[2]
>        7814078464 blocks super 1.2 level 6, 64k chunk, algorithm 2 
> [10/10] [UUUUUUUUUU]
> 
> Nothing urgent, just musings after the last weeks oddities.
> 
> Regards,
> Brad
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2011-04-10  8:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-09 16:14 Couple of questions Brad Campbell
2011-04-09 23:17 ` Roman Mamedov
2011-04-10  8:02 ` NeilBrown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-16  0:01 Adrian McMenamin
2006-03-16 10:42 ` Takashi Iwai
2006-03-16 21:08   ` Adrian McMenamin
2006-03-17  0:10     ` Carlos Munoz
2006-03-17  0:20     ` Lee Revell
2006-03-16 23:34   ` Adrian McMenamin
2006-03-17  0:16     ` Lee Revell
2006-03-17 10:13       ` Takashi Iwai
2006-03-17 20:27         ` Adrian McMenamin
2006-03-17 20:29           ` Takashi Iwai
2006-03-17 23:29             ` Adrian McMenamin
2006-03-17 23:46               ` Lee Revell
2006-03-17 23:51                 ` Adrian McMenamin
2006-03-17 23:58                   ` Lee Revell
2006-03-18  0:08                     ` Adrian McMenamin
2006-03-18  0:17                       ` Lee Revell
2006-03-18  0:22                         ` Adrian McMenamin
2006-03-18 11:08   ` Adrian McMenamin
2006-03-20 18:11     ` Carlos Munoz
1998-03-20 18:39 couple " Nick Verhaegen

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=20110410180254.5d59696a@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists2009@fnarfbargle.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 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.