linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Neil Brown <neilb@suse.de>, Alexandre Oliva <aoliva@redhat.com>,
	linux-raid <linux-raid@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: modifying degraded raid 1 then re-adding other members is bad
Date: Tue, 08 Aug 2006 21:17:05 +0200	[thread overview]
Message-ID: <m3fyg7m40e.fsf@defiant.localdomain> (raw)
In-Reply-To: <44D8732C.2060207@tls.msk.ru> (Michael Tokarev's message of "Tue, 08 Aug 2006 15:19:08 +0400")

Michael Tokarev <mjt@tls.msk.ru> writes:

> Why we're updating it BACKWARD in the first place?

Another scenario: 1 disk (of 2) is removed, another is added, RAID-1
is rebuilt, then the disk added last is removed and replaced by
the disk which was removed first. Would it trigger this problem?

> Also, why, when we adding something to the array, the event counter is
> checked -- should it resync regardless?

I think it's a full start, not a hot add. For hot add contents of
the new disk should be ignored.
-- 
Krzysztof Halasa

  reply	other threads:[~2006-08-08 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08  9:38 modifying degraded raid 1 then re-adding other members is bad Alexandre Oliva
2006-08-08 11:12 ` Neil Brown
2006-08-08 11:19   ` Michael Tokarev
2006-08-08 19:17     ` Krzysztof Halasa [this message]
2006-08-08 22:33       ` Neil Brown
2006-08-08 22:30     ` Neil Brown
2006-08-09  6:35       ` Jan Engelhardt
2006-08-09 23:18         ` Neil Brown
2006-08-09  9:01     ` Helge Hafting

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=m3fyg7m40e.fsf@defiant.localdomain \
    --to=khc@pm.waw.pl \
    --cc=aoliva@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=neilb@suse.de \
    /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).