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>
Subject: Aiming for release of mdadm-3.3.1 next week (early June)
Date: Mon, 26 May 2014 09:45:36 +1000	[thread overview]
Message-ID: <20140526094536.3e1e4bdc@notabene.brown> (raw)

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


I seem to remember suggesting a while ago that mdadm 3.3.1 would be out
before Easter.  Clearly this didn't happen, but I think I'm now about ready.
So I plan to release mdadm-3.3.1 in the first week of June.  I think it is
mostly ready now, but a few self-tests are complaining and I need to determine
where the fault is.

I've made a few changes to the DDF code just recently - mostly cleaning up
and small adjustments, but if anyone uses DDF and want to double check that
the current code still works for them, I wouldn't object.

I've also added "misc/mdcheck" which is meant to run nightly and initiate a
'check' on all drives periodically.  It will stop the 'check' after a set
period of time and  continue from where it left off.  It is currently fair
basic and I like  it that way, but if there are particular features that
people would  like to see in this sort of script, now would be a good time to
say "the script of here does the same thing only much better, why not just
use that"...

There have been quite a few changes to improve interaction with systemd.
This probably isn't all perfect yet but hopefully once it is in a real
release it will get tested more.

Thanks in advance for any testing and/or feedback.

NeilBrown

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

                 reply	other threads:[~2014-05-25 23:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140526094536.3e1e4bdc@notabene.brown \
    --to=neilb@suse.de \
    --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 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).