Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: linux-raid@vger.kernel.org
Subject: ANNOUNCE: mdadm 2.6.3 - A tool for managing Soft RAID under Linux
Date: Mon, 20 Aug 2007 14:26:46 +1000	[thread overview]
Message-ID: <18121.6150.30420.474493@notabene.brown> (raw)



I am pleased to announce the availability of
   mdadm version 2.6.3

It is available at the usual places:
   http://www.cse.unsw.edu.au/~neilb/source/mdadm/
and
   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.3  adds a  few minor bug  fixes to 2.6.2

Changelog Entries:
    -   allow --write-behind to be set for --grow.
    -   When adding new disk to an array, don't reserve so much bitmap
        space that the disk cannot store the required data. (Needed when
	1.x array was created with older mdadm).
    -   When adding a drive that was a little too small, we did not get
	the correct error message.
    -   Make sure that if --assemble find an array in the critical region
	of a reshape, and cannot find the critical data to restart the
	reshape, it gives an error message.
    -   Fix segfault with '--detail --export' and non-persistent
        superblocks.
    -   Various manpage updates.
    -   Improved 'raid4' support (--assemble, --monitor)
    -   Option parsing fixes w.r.t -a
    -   Interpret "--assemble --metadata=1" to allow any version 1.x
	metadata, and be more specific in the "metadata=" message printed
	with --examine --brief
    -   Fix spare migration in --monitor.

Development of mdadm is sponsored by
 SUSE Labs, Novell Inc.

NeilBrown  20th August 2007

                 reply	other threads:[~2007-08-20  4:26 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=18121.6150.30420.474493@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