From: NeilBrown <neilb@suse.de>
To: Alexander Lyakas <alex.bolshoy@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID-10 explicitly defined drive pairs?
Date: Tue, 10 Jun 2014 10:11:22 +1000 [thread overview]
Message-ID: <20140610101122.53d16123@notabene.brown> (raw)
In-Reply-To: <CAGRgLy5tauPMAoy=3QkErvtQPjz3FrNYTxQ-2rxTP6nO5tRXXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Mon, 9 Jun 2014 17:26:38 +0300 Alexander Lyakas <alex.bolshoy@gmail.com>
wrote:
> > Why do you refuse to freeze the array if it's not "idle"? What will
> > happen is that current recover/resync will abort, drives will be
> > added, and on unfreezing, array will resume (restart?) recovery with
> > all drives. If array was resyncing, however, it will start recovering
> > the newly added drives, because kernel prefers recovery over resync
> > (as we discussed earlier).
> Indeed, since dea3786ae2cf74ecb0087d1bea1aa04e9091ad5c, I see that you
> agree to freeze the array also in case it is recovering.
I guess I did..... though I don't remember seeing the email that you have
quoted. I can see it in my inbox, but it seems that I never replied. Maybe
I was too busy that day :-(
If there other outstanding issues, feel free to resend.
(If I don't reply it is more likely to be careless than deliberate, so in
general you should feel free to resend if I don't respond in a week or so).
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-06-10 0:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 11:54 RAID-10 explicitly defined drive pairs? Jan Kasprzak
2011-12-12 15:33 ` John Robinson
2012-01-06 15:08 ` Jan Kasprzak
2012-01-06 16:39 ` Peter Grandi
2012-01-06 19:16 ` Stan Hoeppner
2012-01-06 20:11 ` Jan Kasprzak
2012-01-06 22:55 ` Stan Hoeppner
2012-01-07 14:25 ` Peter Grandi
2012-01-07 16:25 ` Stan Hoeppner
2012-01-09 13:46 ` Peter Grandi
2012-01-10 3:54 ` Stan Hoeppner
2012-01-10 4:13 ` NeilBrown
2012-01-10 16:25 ` Stan Hoeppner
2012-01-12 11:58 ` Peter Grandi
2012-01-12 12:47 ` Peter Grandi
2012-01-12 21:24 ` Stan Hoeppner
2012-01-06 20:55 ` NeilBrown
2012-01-06 21:02 ` Jan Kasprzak
2012-03-22 10:01 ` Alexander Lyakas
2012-03-22 10:31 ` NeilBrown
2012-03-25 9:30 ` Alexander Lyakas
2012-04-04 16:56 ` Alexander Lyakas
2014-06-09 14:26 ` Alexander Lyakas
2014-06-10 0:11 ` NeilBrown [this message]
2014-06-11 16:05 ` Alexander Lyakas
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=20140610101122.53d16123@notabene.brown \
--to=neilb@suse.de \
--cc=alex.bolshoy@gmail.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 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.