linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: linux RAID <linux-raid@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
	Doug Ledford <dledford@redhat.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	Dan Williams <dan.j.williams@intel.com>,
	"Dorau, Lukasz" <lukasz.dorau@intel.com>,
	"Czarnowska, Anna" <anna.czarnowska@intel.com>,
	Przemyslaw Czarnowski
	<przemyslaw.hawrylewicz.czarnowski@intel.com>,
	Clint Byrum <clint@ubuntu.com>
Subject: mdadm-3.2.5 coming soon :-(
Date: Tue, 15 May 2012 21:50:20 +1000	[thread overview]
Message-ID: <20120515215020.76fd9c6f@notabene.brown> (raw)
In-Reply-To: <20120503142201.649766de@notabene.brown>

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


It turns out that there is a nasty regression in 3.2.4.
--add is even more broken than it was before.  My testing
doesn't test new mdadm against arrays created with old mdadm, and
so missed it.  I should probably find a way to improve on that.

So 3.2.4 isn't really a good idea so I'll be releasing 3.2.5 on Friday.
I currently have 5 patches since 3.2.4.  So it'll be a small but
(hopefully) safe update.

If anyone knows of any other issues that have cropped up wit 3.2.4, please
let me know.

Thanks,
NeilBrown

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

  parent reply	other threads:[~2012-05-15 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03  4:22 Last call for input to mdadm-3.2.4 NeilBrown
2012-05-03  9:18 ` Jes Sorensen
2012-05-15 11:50 ` NeilBrown [this message]
2012-05-15 15:22   ` mdadm-3.2.5 coming soon :-( Maciej Naruszewicz
2012-05-17  5:44     ` NeilBrown
2012-05-17  8:28       ` Patelczyk, Maciej
2012-05-17 11:52         ` Patelczyk, Maciej
2012-05-18  3:44           ` 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=20120515215020.76fd9c6f@notabene.brown \
    --to=neilb@suse.de \
    --cc=Jes.Sorensen@redhat.com \
    --cc=anna.czarnowska@intel.com \
    --cc=clint@ubuntu.com \
    --cc=dan.j.williams@intel.com \
    --cc=dledford@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lukasz.dorau@intel.com \
    --cc=mjt@tls.msk.ru \
    --cc=przemyslaw.hawrylewicz.czarnowski@intel.com \
    /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).