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:
signature.asc
Description: PGP signature
