From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Preparing for mdadm-3.3
Date: Tue, 25 Jun 2013 10:40:20 +0200 [thread overview]
Message-ID: <wrfjobaueg7f.fsf@redhat.com> (raw)
In-Reply-To: <20130625094211.20134bed@notabene.brown> (NeilBrown's message of "Tue, 25 Jun 2013 09:42:11 +1000")
NeilBrown <neilb@suse.de> writes:
> On Mon, 24 Jun 2013 18:10:23 +0200 Jes Sorensen <Jes.Sorensen@redhat.com>
> wrote:
>
>> NeilBrown <neilb@suse.de> writes:
>> > Hi all,
>> > it has been way too long since an mdadm release. So I'm hoping to pull one
>> > together over the next few weeks. It will be mdadm-3.3
>> > My goal is to have it out by 25th July (i.e. one month).
>>
>> Hi Neil,
>>
>> I don't see any mention of hot replace support in your log. Did this get
>> canned or did I just lose track of everything? Admittedly my marbles
>> have gotten lost regularly the last couple of months.
>>
>
> Hi Jes,
> yes, hot replace support is something I should have mentioned but didn't
>
> mdadm /dev/md0 --replace /dev/foo
>
> will try to replace /dev/foo with a spare.
>
> mdadm /dev/md0 --replace /dev/foo --with /dev/bar
>
> will try to replace it with the spare "/dev/bar".
>
> Testing of that would be good too.
> I'll be sure to mention that in the 3.3 announcement. Thanks.
Great, I'll try and package up mdadm-3.3-rc1 and see if I can get QA on
my end to test it.
Cheers,
Jes
next prev parent reply other threads:[~2013-06-25 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 7:18 Preparing for mdadm-3.3 NeilBrown
2013-06-24 13:44 ` Mark Knecht
2013-06-24 23:38 ` NeilBrown
[not found] ` <wrfjli5zfq1c.fsf@redhat.com>
2013-06-24 23:42 ` NeilBrown
2013-06-25 8:40 ` Jes Sorensen [this message]
2013-06-27 18:24 ` Martin Wilck
2013-07-01 23:41 ` NeilBrown
2013-07-25 8:02 ` NeilBrown
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=wrfjobaueg7f.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--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 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.