ANNOUNCE: mdadm-1.0.9 - prelease for 1.1.0

ANNOUNCE: mdadm-1.0.9 - prelease for 1.1.0

[Neil Brown]

Hi all,
 I have just placed mdadm-1.0.9 at

   http://www.cse.unsw.edu.au/~neilb/source/mdadm/mdadm-1.0.9.tgz

 and it should appear at
 
   http://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-1.0.9.tar.gz

 shortly.

 I plan to release it as 1.1.0 and announce it more widely after
 incorporating any feedback.

 I expect the next release of mdadm after 1.1.0 to have  support for
 different superblock layouts (shortly to appear in 2.5...) and to be
 called version 2.0 (though there might be some 1.9. pre-releases
 first).

 The changelog includes:

    -   Documentation updates including kernel parameters documented
	in md.4
    -   --assemble --force for raid4/5 will mark clean, needed for 2.5
    -   --detail prints out the events counter as well
    -   flush device before reading superblock to be sure to get
	current data
    -   added mdadm.static target to makefile for static linking
    -	--monitor was ignoring  /dev/md0 due to off-by-one error
    -	Fix assorted typos
    -   Fix printing of Gibibytes - calc was wrong.
    -   Fix printing of Array Size in --detail when very big.
    -   --monitor no longer tries to work for raid0 or linear as these
	have nothing to be monitors.
    -   The word 'partitions' on a DEVICE line will cause all partitions
	listed in /proc/partitions to be considered
    -   If the config file is called 'partitions' then it will be treated
        as though it contained exactly 'device partitions' so e.g.
	  mdadm -Ebsc partitions
	will fill all raid partitions easily.	
    -	successfully assemble multipath devices by ignoring raid_disk
	value from superblock (it is always the same).
    -   --assemble not tied to MD_SB_DISKS limit quite so much
    -   Support compiling with tcc
    -   Support compiling with uclibc - just skip scan of /dev
    -   Add --update= option for Assemble mode.  Either sparc2.2
	or super-minor updates are possible.  See mdadm.8

 Please try it out and let me know what you think.

NeilBrown

Re: ANNOUNCE: mdadm-1.0.9 - prelease for 1.1.0

[Friedrich Lobenstock]

Hi!

Neil Brown wrote:
> Hi all,
>  I have just placed mdadm-1.0.9 at
> 
>    http://www.cse.unsw.edu.au/~neilb/source/mdadm/mdadm-1.0.9.tgz
> 
>  and it should appear at
>  
>    http://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-1.0.9.tar.gz
> 
>  shortly.

Might I suggest you store this accouncement in a file and put it at the
same place as mdadm? At least the changelog. Thanks.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock         FL226-RIPE             Internetservices
URL: http://www.fl.priv.at/                     Email: fl@fl.priv.at
____________________________________________________________________

Re: ANNOUNCE: mdadm-1.0.9 - prelease for 1.1.0

[Derek Vadala]

On Wed, 12 Feb 2003, Neil Brown wrote:

>     -   If the config file is called 'partitions' then it will be treated
>         as though it contained exactly 'device partitions' so e.g.
> 	  mdadm -Ebsc partitions
> 	will fill all raid partitions easily.

So the difference between this and mdadm -Dbs is that it generates config
entries for arrays that are online, but -Ebcs partitions gets a list of
all the block devices from /proc/partitions and generates array lines
based on those.

How come -Dbs lists only num-device, and UUID while -Ebsc lists both of
those as well as the devices list?

This -Ebsc partitions is a nice feature by the way.

-- 
Derek Vadala, derek@cynicism.com, http://www.cynicism.com/~derek

Re: ANNOUNCE: mdadm-1.0.9 - prelease for 1.1.0

[Neil Brown]

On Thursday February 20, derek@cynicism.com wrote:
> On Wed, 12 Feb 2003, Neil Brown wrote:
> 
> >     -   If the config file is called 'partitions' then it will be treated
> >         as though it contained exactly 'device partitions' so e.g.
> > 	  mdadm -Ebsc partitions
> > 	will fill all raid partitions easily.
> 
> So the difference between this and mdadm -Dbs is that it generates config
> entries for arrays that are online, but -Ebcs partitions gets a list of
> all the block devices from /proc/partitions and generates array lines
> based on those.

Yep.

> 
> How come -Dbs lists only num-device, and UUID while -Ebsc lists both of
> those as well as the devices list?
> 

Because the information is trivially and obviously available when
doing -E, but not quite so obviously available when doing -D.  Still
it shouldn't be hard to add that info.  I will put it on my todo list
for 1.1.


> This -Ebsc partitions is a nice feature by the way.
> 

Thanks,  It's the result of user feed back.  I like to encourage user
feedback!! 

NeilBrown