All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: RAID 1 resync with both members good.
Date: Fri, 8 May 2009 08:07:33 +0200	[thread overview]
Message-ID: <20090508060733.GA7759@maude.comedia.it> (raw)
In-Reply-To: <a93e6da36d0a72953e6a2cce74323e2d.squirrel@neil.brown.name>

On Fri, May 08, 2009 at 10:32:01AM +1000, NeilBrown wrote:
>On Thu, May 7, 2009 6:08 pm, Simon Jackson wrote:
>> Could someone help me understand why I am seeing the following
>> behaviour?
>>
>> We use a pair of disks with 3 RAID1 partitions inside an appliance
>> system.
>>
>> During testing we have seen some instances of the RAID devices resyncing
>> even though both members are marked as good in the output of
>> /proc/mdstat.
>
>That is exactly as expectedc.
>If one of the devices had failed and was being replaced by a spare, you
>would see "recovery" not "resync".
>
>Resync happens after an unclean shutdown.
>In that case, both drives have good data, but they might not be the same.
>The resync makes sure that all copies have exactly the same data.
>
>So you there must have been an unclean shutdown before the most recent
>restart.

or a stupid udev rule that gets incremental assembly wrong

L.

-- 
Luca Berra -- bluca@comedia.it
         Communication Media & Services S.r.l.
  /"\
  \ /     ASCII RIBBON CAMPAIGN
   X        AGAINST HTML MAIL
  / \

  reply	other threads:[~2009-05-08  6:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07  8:08 RAID 1 resync with both members good Simon Jackson
2009-05-07 19:18 ` Richard Scobie
2009-05-07 20:19   ` Mario 'BitKoenig' Holbe
     [not found] ` <3D76E016F4A2A749A1EB1A3FD83E22BC02783863@uk-email.terastack.bluearc.c om>
2009-05-08  0:32   ` NeilBrown
2009-05-08  6:07     ` Luca Berra [this message]
2009-05-08  7:15     ` Simon Jackson

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=20090508060733.GA7759@maude.comedia.it \
    --to=bluca@comedia.it \
    --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.