All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Alexander Lyakas <alex.bolshoy@gmail.com>
Cc: Jan Kasprzak <kas@fi.muni.cz>,
	linux-raid <linux-raid@vger.kernel.org>,
	John Robinson <john.robinson@anonymous.org.uk>
Subject: Re: RAID-10 explicitly defined drive pairs?
Date: Thu, 22 Mar 2012 21:31:14 +1100	[thread overview]
Message-ID: <20120322213114.61fd4e44@notabene.brown> (raw)
In-Reply-To: <CAGRgLy4Q5FhHMAeU3egqEfFKR_h1HneReg0sD_+hCmsF3WDzQw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

On Thu, 22 Mar 2012 12:01:48 +0200 Alexander Lyakas <alex.bolshoy@gmail.com>
wrote:

> Neil,
> 
> >  echo frozen > /sys/block/mdN/md/sync_action
> >  mdadm --add /dev/mdN /dev......
> >  echo recover > /sys/block/mdN/md/sync_action
> >
> > it should do them all at once.
> >
> > I should teach mdadm about this..
> 
> What is required to do that from mdadm? I don't see any other place
> where MD_RECOVERY_FROZEN is set, except via sysfs. So do you suggest
> that mdadm use sysfs for that?

Yes.

http://neil.brown.name/git?p=mdadm;a=commitdiff;h=9f58469128c99c0d7f434d28657f86789334f253

> Also, what should be done if mdadm succeeds to "freeze" the array, but
> fails to "unfreeze" it for some reason?

What could possibly cause that?
I guess if someone kills mdadm while it was running..


NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-03-22 10:31 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 [this message]
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
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=20120322213114.61fd4e44@notabene.brown \
    --to=neilb@suse.de \
    --cc=alex.bolshoy@gmail.com \
    --cc=john.robinson@anonymous.org.uk \
    --cc=kas@fi.muni.cz \
    --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.