From: NeilBrown <neilb@suse.de>
To: linux-raid@vger.kernel.org
Subject: Preparing for mdadm-3.3
Date: Mon, 24 Jun 2013 17:18:18 +1000 [thread overview]
Message-ID: <20130624171818.71a9688a@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 2251 bytes --]
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).
To this end I have tagged "mdadm-3.3-rc1" in my git tree and pushed it out
in the hope that people might test it.
You can "git pull" or "git clone" from
git://neil.brown.name/mdadm/
of if you really like tar files:
http://git.neil.brown.name/git?p=mdadm.git;a=snapshot;h=refs/tags/mdadm-3.3-rc1;sf=tgz
Now would be a good time to test anything your are interested in, or remind
me of something you wanted that hasn't been done yet, or send me your mdadm
patches that you have been meaning to send me but never seem to get around
to it.
Some of the new things in mdadm-3.3 are:
- Reshape various arrays without needing backup file. This is done by
changing the 'data_offset' so we never need to write any data back over
where it was before.
- "--assemble --update=metadata" can convert a 0.90 array to a 1.0 array.
- bad-block-logs are supported (but not heavily tested yet)
- "--assemble --update=revert-reshape" can be used to undo a reshape that has
just been started but isn't really wanted. This also needs lots of testing.
- improved locking between --incremental and --assemble
- uses systemd to run "mdmon" if systemd is configured to do that.
- kernel names of md devices can be non-numeric. e.g. "md_home" rather than
"md0". This will probably confuse lots of other tools, so you need to
echo CREATE names=yes >> /etc/mdadm.conf
or the feature will not be used. (you also need a reasonably new kernel).
- "--stop" can be given a kernel name instead of a device name. i.e
mdadm --stop md4
will work even if /dev/md4 doesn't exist.
- "--detail --export" has some information about the devices in the array
- --dump and --retstore can be used to backup and restore the metadata on an
array.
and lots of bugfixes and other little changes.
I somehow got unsubscribed from linux-raid (again) a few weeks back, so if
anything was sent to the list and not me that I should know about, now might
be a good time to resend that too.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next reply other threads:[~2013-06-24 7:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 7:18 NeilBrown [this message]
2013-06-24 13:44 ` Preparing for mdadm-3.3 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
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=20130624171818.71a9688a@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).