From: Neil Brown <neilb@suse.de>
To: linux-raid@vger.kernel.org
Subject: ANNOUNCE: mdadm 2.6.9 - A tool for managing Soft RAID under Linux
Date: Tue, 10 Mar 2009 17:02:05 +1100 [thread overview]
Message-ID: <18870.605.963621.55379@notabene.brown> (raw)
I am pleased to announce the availability of
mdadm version 2.6.9
It is available at the usual places:
countrycode=xx.
http://www.${countrycode}kernel.org/pub/linux/utils/raid/mdadm/
and via git at
git://neil.brown.name/mdadm
http://neil.brown.name/git?p=mdadm
mdadm is a tool for creating, managing and monitoring
device arrays using the "md" driver in Linux, also
known as Software RAID arrays.
Release 2.6.9 contains various bug fixes.
Clearly 2.6.8 was not the final 2.x release.
Hopefully 2.6.9 will be as I don't want go to 2.7, and
2.6.10 might be confusing (though I'll probably go that
way if I need to).
New features will only appear in the 3.x series of which 3.0 will be
release within a few months.
Changelog Entries:
Bernhard Reutner-Fischer (1):
mdadm fix compilation for uClibc
Dustin Kirkland (2):
Fail overtly when asprintf fails to allocate memory
Typo in earlier patch : asprintf -> vasprintf
NeilBrown (11):
Allow --config in --incremental mode.
Kill: Don't use O_EXCL when --force is used.
Assemble: don't assume array is 'clean' unless all devices think it is.
Assemble: set stripe_cache_size properly when restarting a reshape.
map: rebuild map if it doesn't exist.
Free mdstat data structures properly.
Fix the used device size in mdadm -D output.
Document 'max' option to --grow --size in --help output.
Fix possible crash if bitmap metadata is bad.
Monitor: send --test message for arrays in /proc/mdstat that aren't in mdadm.conf
super1: make sure max_dev grows enough when adding a device to an array.
Development of mdadm is sponsored by
SUSE Labs, Novell Inc.
NeilBrown 28th November 2008
reply other threads:[~2009-03-10 6:02 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=18870.605.963621.55379@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