OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/mdadm?expand=0&rev=2

mdadm-2.5.3-infoname.diff

@@ -1,11 +0,0 @@
---- super1.c
-+++ super1.c
-@@ -538,7 +538,7 @@
- 			strncpy(info->name, c+1, 31 - (c-sb->set_name));
- 		else
- 			strncpy(info->name, sb->set_name, 32);
--		info->name[33] = 0;
-+		info->name[32] = 0;
- 	}
- 	if (strcmp(update, "name") == 0) {
- 		if (info->name[0] == 0)

mdadm-2.5.3.tar.bz2

@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:22e8364dcc528b1e5e4ee8f25ef4a6f0e9c648f1f1d2d7dbe688c929a3369672
-size 135019

mdadm-2.6.1.tar.bz2

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a9028779f73bcfb55ad0e415de60557f68b2fd9a61d17e3bd07dd0d559f2cf02
+size 149000

mdadm.changes

@@ -1,3 +1,123 @@
+-------------------------------------------------------------------
+Mon Apr  2 15:00:10 CEST 2007 - mmarek@suse.cz
+
+- updated to 2.6.1
+  * --monitor was producing some meaningless warnings due to a bug.
+  * Fix some compiler warnings.
+  * Fully support --grow for raid6.  If a reshape crashed during
+    the critical period, mdadm wouldn't restore the Q information
+    properly.
+  * Update documentation for --grow.
+  * Report bitmap status in --detail and --examine
+  * Default to v1 superblocks instead of v0.90 if the array
+    is too big for 0.90 to handle.
+  * Sort the output of "mdadm --detail --scan" so that it is
+    in a suitable order for assembling arrays. i.e. components come
+    before an array that they are part of.
+  * Require bitmap files to have a '/' in their name.
+  * Rewrite 'reshape' support including performing a backup
+    of the critical region for a raid5 growth, and restoring that
+    backup after a crash.
+  * Put a 'canary' at each end of the backup so a corruption
+    can be more easily detected.
+  * Support --backup-file for backing-up critical section during
+    growth.
+  * Erase old superblocks (of different versions) when creating new
+    array.
+  * Allow --monitor to work with arrays with >28 devices
+  * Report reshape information in --detail
+  * Handle symlinks in /dev better
+  * Fix mess in --detail output which a device is missing.
+  * Support 'bitmap=' in mdadm.conf for auto-assembling arrays with
+    write-intent bitmaps in separate files.
+  * Fix alignment problem in version-1 superblocks.
+    NOTE: This is an incompatable change affecting raid5 reshape.
+    If you want to reshape a raid5 using version-1 superblocks,
+    use 2.6.17-rc2 or later, and mdadm-2.4.1 or later.
+  * Support 'mailfrom' line in mdadm.conf so the From: line in alert
+    emails can be explicitly set.
+  * Arrange that SparesMissing (which is similar in import to
+    DegradedArray) generates an Email.
+  * Assume "DEVICE partitions" if no DEVICE line is given.
+  * Support new 'offset' layout for raid10.
+  * When creating a bitmap file, choose a chunksize to limit number
+    of bitmap chunks to 2 million.  More than this can cause kmalloc
+    failure.
+  * New 'CREATE' line in mdadm.conf for defaults such as owner, group,
+    mode and auto-flag
+  * --detail checks if array has been started or not and includes that
+    in report.
+  * When using --update=uuid on an array with a bitmap, update the
+    bitmap's uuid too.
+  * Add a copy of /proc/mdstat to the mail message sent by mdadm
+    --monitor.
+  * New flag --no-degraded to avoid starting arrays if there are
+    fewer devices available than last time the array was started.
+    This is only needed with --scan, as with --scan, that behaviour
+    is the default.
+  * Support for 'homehost' concept.  This is a fairly major update.
+    It includes a configfile option and a command line option for
+    specifying a homehost, records that host in the superblock,
+    and reports the homehost where possible.
+  * Support for Auto Assembly.  "mdadm -As" will, if provided with
+    the name of a homehost, try to assemble all arrays it can find
+    that were created for that homehost.  See man pages for more details.
+  * Don't try to create devices with --manage or --grow
+  * allow default metadata (superblock) type to be specified
+    in mdadm.conf
+  * Avoid some misdetection of overlapping partitions
+  * Add 'Array Slot' line to --examine for version-1 superblocks
+    to make it a bit easier to see what is happening.
+  * Work around bug in --add handling for  version-1 superblocks
+    in 2.6.17 (and prior).
+  * Make -assemble a bit more resilient to finding strange
+    information in superblocks.
+  * When creating devices in /dev/md/ create matching symlinks
+    from /dev.  e.g. /dev/md0 -> /dev/md/0.
+    Allow this to be disabled in mdadm.conf or on command line.
+  * Allow a number (of partitions) after the 'yes' option to --auto=
+    This is particularly useful in the 'create' line in mdadm.conf.
+  * Remove partitions from any whole device that is made part of
+    an md array.  This is a work-around for annoying messages
+    when the first block on some drive accidentally looks like a
+    partition table.
+  * Close stray fd in mdassemble so that it can assemble stacked
+    devices
+  * If mdassemble finds an array already assembled, it marks it
+    read-write.
+  * Remove error in md_open if array is already active.  This isn't
+    needed and gets in the ways if an array was created e.g. in
+    initramfs, but device doesn't yet exist in /dev.
+  * When --assemble --scan is run, if all arrays that could be found
+    have already been started, don't report an error.
+  * Allow --assemble --force to mark a raid6 clean when it has two
+    missing devices (which is needed else if won't assemble.
+    Without this fix it would only assemble if one or zero
+    missing devices.
+  * Support --update=devicesize for cases where the underlying device
+    can change size.
+  * Default to --auto=yes so the array devices with 'standard' names
+    get created automatically, as this is almost always what is wanted.
+  * Give useful message if raid4/5/6 cannot be started because it is
+    not clean and is also degraded.
+  * Increase raid456 stripe cache size if needed to --grow the array.
+    The setting used unfortunately requires intimate knowledge of the
+    kernel, and it not reset when the reshape finishes.
+  * Change 'Device Size' to 'Used Dev Size' because it only shows how
+    much of each device is actually used, not how big they are.
+  * --wait or -W will wait for resync activity to finish on the given
+    devices.
+  * If two drives in a raid5 disappear at the same time, then "-Af"
+    will add them both in rather than just one and forcing the array
+    to 'clean'.  This is slightly safer in some cases.
+  * Don't hold md device open for so long in --monitor mode - map_dev
+    can be slow and interferes with trying to stop the array.
+  * Support --uuid= with --create to choose your own UUID.
+  * New major more "--incremental" for incremental assemble of arrays,
+    intended for use with udev.
+  * lots of bugfixes
+  * manpage updates
+
 -------------------------------------------------------------------
 Wed Jan 10 11:58:14 CET 2007 - mmarek@suse.cz
 

mdadm.spec

@@ -1,5 +1,5 @@
 #
-# spec file for package mdadm (Version 2.5.3)
+# spec file for package mdadm (Version 2.6.1)
 #
 # Copyright (c) 2007 SUSE LINUX Products GmbH, Nuernberg, Germany.
 # This file and all modifications and additions to the pristine
@@ -11,8 +11,8 @@
 # norootforbuild
 
 Name:           mdadm
-Version:        2.5.3
+Version:        2.6.1
-Release:        20
+Release:        1
 BuildRequires:  opensp sgmltool
 PreReq:         %fillup_prereq %insserv_prereq
 Obsoletes:      raidtools
@@ -29,7 +29,6 @@ Source3:        mdadmd
 Source4:        boot.md
 Source5:        mdrun
 Source6:        raidautorun.c
-Patch:          %{name}-%{version}-infoname.diff
 
 %description
 Mdadm is a program that can be used to control Linux md devices. It is
@@ -44,7 +43,6 @@ Authors:
 
 %prep
 %setup -q -a1
-%patch
 
 %build
 %{suse_update_config -f}
@@ -120,7 +118,124 @@ rm -rf $RPM_BUILD_ROOT
 %{_sbindir}/*
 %{_var}/adm/fillup-templates/sysconfig.mdadm
 
-%changelog -n mdadm
+%changelog
+* Mon Apr 02 2007 - mmarek@suse.cz
+- updated to 2.6.1
+  * --monitor was producing some meaningless warnings due to a bug.
+  * Fix some compiler warnings.
+  * Fully support --grow for raid6.  If a reshape crashed during
+  the critical period, mdadm wouldn't restore the Q information
+  properly.
+  * Update documentation for --grow.
+  * Report bitmap status in --detail and --examine
+  * Default to v1 superblocks instead of v0.90 if the array
+  is too big for 0.90 to handle.
+  * Sort the output of "mdadm --detail --scan" so that it is
+  in a suitable order for assembling arrays. i.e. components come
+  before an array that they are part of.
+  * Require bitmap files to have a '/' in their name.
+  * Rewrite 'reshape' support including performing a backup
+  of the critical region for a raid5 growth, and restoring that
+  backup after a crash.
+  * Put a 'canary' at each end of the backup so a corruption
+  can be more easily detected.
+  * Support --backup-file for backing-up critical section during
+  growth.
+  * Erase old superblocks (of different versions) when creating new
+  array.
+  * Allow --monitor to work with arrays with >28 devices
+  * Report reshape information in --detail
+  * Handle symlinks in /dev better
+  * Fix mess in --detail output which a device is missing.
+  * Support 'bitmap=' in mdadm.conf for auto-assembling arrays with
+  write-intent bitmaps in separate files.
+  * Fix alignment problem in version-1 superblocks.
+  NOTE: This is an incompatable change affecting raid5 reshape.
+  If you want to reshape a raid5 using version-1 superblocks,
+  use 2.6.17-rc2 or later, and mdadm-2.4.1 or later.
+  * Support 'mailfrom' line in mdadm.conf so the From: line in alert
+  emails can be explicitly set.
+  * Arrange that SparesMissing (which is similar in import to
+  DegradedArray) generates an Email.
+  * Assume "DEVICE partitions" if no DEVICE line is given.
+  * Support new 'offset' layout for raid10.
+  * When creating a bitmap file, choose a chunksize to limit number
+  of bitmap chunks to 2 million.  More than this can cause kmalloc
+  failure.
+  * New 'CREATE' line in mdadm.conf for defaults such as owner, group,
+  mode and auto-flag
+  * --detail checks if array has been started or not and includes that
+  in report.
+  * When using --update=uuid on an array with a bitmap, update the
+  bitmap's uuid too.
+  * Add a copy of /proc/mdstat to the mail message sent by mdadm
+    --monitor.
+  * New flag --no-degraded to avoid starting arrays if there are
+  fewer devices available than last time the array was started.
+  This is only needed with --scan, as with --scan, that behaviour
+  is the default.
+  * Support for 'homehost' concept.  This is a fairly major update.
+  It includes a configfile option and a command line option for
+  specifying a homehost, records that host in the superblock,
+  and reports the homehost where possible.
+  * Support for Auto Assembly.  "mdadm -As" will, if provided with
+  the name of a homehost, try to assemble all arrays it can find
+  that were created for that homehost.  See man pages for more details.
+  * Don't try to create devices with --manage or --grow
+  * allow default metadata (superblock) type to be specified
+  in mdadm.conf
+  * Avoid some misdetection of overlapping partitions
+  * Add 'Array Slot' line to --examine for version-1 superblocks
+  to make it a bit easier to see what is happening.
+  * Work around bug in --add handling for  version-1 superblocks
+  in 2.6.17 (and prior).
+  * Make -assemble a bit more resilient to finding strange
+  information in superblocks.
+  * When creating devices in /dev/md/ create matching symlinks
+  from /dev.  e.g. /dev/md0 -> /dev/md/0.
+  Allow this to be disabled in mdadm.conf or on command line.
+  * Allow a number (of partitions) after the 'yes' option to --auto=
+  This is particularly useful in the 'create' line in mdadm.conf.
+  * Remove partitions from any whole device that is made part of
+  an md array.  This is a work-around for annoying messages
+  when the first block on some drive accidentally looks like a
+  partition table.
+  * Close stray fd in mdassemble so that it can assemble stacked
+  devices
+  * If mdassemble finds an array already assembled, it marks it
+  read-write.
+  * Remove error in md_open if array is already active.  This isn't
+  needed and gets in the ways if an array was created e.g. in
+  initramfs, but device doesn't yet exist in /dev.
+  * When --assemble --scan is run, if all arrays that could be found
+  have already been started, don't report an error.
+  * Allow --assemble --force to mark a raid6 clean when it has two
+  missing devices (which is needed else if won't assemble.
+  Without this fix it would only assemble if one or zero
+  missing devices.
+  * Support --update=devicesize for cases where the underlying device
+  can change size.
+  * Default to --auto=yes so the array devices with 'standard' names
+  get created automatically, as this is almost always what is wanted.
+  * Give useful message if raid4/5/6 cannot be started because it is
+  not clean and is also degraded.
+  * Increase raid456 stripe cache size if needed to --grow the array.
+  The setting used unfortunately requires intimate knowledge of the
+  kernel, and it not reset when the reshape finishes.
+  * Change 'Device Size' to 'Used Dev Size' because it only shows how
+  much of each device is actually used, not how big they are.
+  * --wait or -W will wait for resync activity to finish on the given
+  devices.
+  * If two drives in a raid5 disappear at the same time, then "-Af"
+  will add them both in rather than just one and forcing the array
+  to 'clean'.  This is slightly safer in some cases.
+  * Don't hold md device open for so long in --monitor mode - map_dev
+  can be slow and interferes with trying to stop the array.
+  * Support --uuid= with --create to choose your own UUID.
+  * New major more "--incremental" for incremental assemble of arrays,
+  intended for use with udev.
+  * lots of bugfixes
+  * manpage updates
 * Wed Jan 10 2007 - mmarek@suse.cz
 - use raidautorun instead of mdrun to autodetect the raid arrays in
   boot.md [#230733]