linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Jed Davidow <jed@ultralame.com>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-raid@vger.kernel.org
Subject: Re: md rotates RAID5 spare at boot
Date: Fri, 11 Jan 2008 09:01:43 +1100	[thread overview]
Message-ID: <18310.38343.339990.718263@notabene.brown> (raw)
In-Reply-To: message from Jed Davidow on Thursday January 10

On Thursday January 10, jed@ultralame.com wrote:
> 
> It looks to me like md inspects and attempts to assemble after each 
> drive controller is scanned (from dmesg, there appears to be a failed 
> bind on the first three devices after they are scanned, and then again 
> when the second controller is scanned).  Would the scan order cause a 
> spare to be swapped in?
> 

This suggests that "mdadm --incremental" is being used to assemble the
arrays.  Every time udev finds a new device, it gets added to
whichever array is should be in.
If it is called as "mdadm --incremental --run", then it will get
started as soon as possible, even if it is degraded.  With the
"--run", it will wait until all devices are available.

Even with "mdadm --incremental --run", you shouldn't get a resync if
the last device is added before the array is written to.

What distro are you running?
What does
   grep -R mdadm /etc/udev

show?

NeilBrown

  reply	other threads:[~2008-01-10 22:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 20:07 md rotates RAID5 spare at boot Jed Davidow
2008-01-10 18:03 ` Jed Davidow
2008-01-10 21:23   ` this goes go my megaraid probs too was: " Eric S. Johansson
2008-01-10 20:47 ` Bill Davidsen
2008-01-10 20:53   ` Jed Davidow
2008-01-10 22:01     ` Neil Brown [this message]
2008-01-10 23:41       ` Jed Davidow
2008-01-10 23:43       ` Jed Davidow
2008-01-11  0:24         ` Neil Brown
     [not found]       ` <47869D2C.7020805@ultralame.com>
2008-01-11  0:22         ` Neil Brown
2008-01-11  0:38           ` Jed Davidow
2008-01-11  1:12             ` 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=18310.38343.339990.718263@notabene.brown \
    --to=neilb@suse.de \
    --cc=davidsen@tmr.com \
    --cc=jed@ultralame.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 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).