From 1679bef2eeb641b77d72bf20e9fbbd555cc0a1cb Mon Sep 17 00:00:00 2001 From: NeilBrown Date: Wed, 5 Nov 2008 17:14:06 +1100 Subject: [PATCH] Release 3.0-devel2 Signed-off-by: NeilBrown --- ANNOUNCE-3.0-devel2 | 98 +++++++++++++++++++++++++++++++++++++++++++++ ReadMe.c | 2 +- inventory | 2 + mdadm.8 | 2 +- mdadm.spec | 2 +- mdassemble.8 | 2 +- 6 files changed, 104 insertions(+), 4 deletions(-) create mode 100644 ANNOUNCE-3.0-devel2 diff --git a/ANNOUNCE-3.0-devel2 b/ANNOUNCE-3.0-devel2 new file mode 100644 index 00000000..0f2924ce --- /dev/null +++ b/ANNOUNCE-3.0-devel2 @@ -0,0 +1,98 @@ +Subject: ANNOUNCE: mdadm 3.0-devel2 - A tool for managing Soft RAID under Linux + +I am pleased to announce the availability of + mdadm version 3.0-devel2 + +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 + +Note that this is a "devel" release. It should be used with +caution, though it is believed to be close to release-candidate stage. + +The significant change which justifies the new major version number is +that mdadm can now handle metadata updates entirely in userspace. +This allows mdadm to support metadata formats that the kernel knows +nothing about. + +Currently two such metadata formats are supported: + - DDF - The SNIA standard format + - Intel Matrix - The metadata used by recent Intel ICH controlers. + +Also the approach to device names has changed significantly. + +If udev is installed on the system, mdadm will not create any devices +in /dev. Rather it allows udev to manage those devices. For this to work +as expected, the included udev rules file should be installed. + +If udev is not install, mdadm will still create devices and symlinks +as required, and will also remove them when the array is stopped. + +mdadm now requires all devices which do not have a standard name (mdX +or md_dX) to live in the directory /dev/md/. Names in this directory +will always be created as symlinks back to the standard name in /dev. + +The man pages contain some information about the new externally managed +metadata. However see below for a more condensed overview. + +Externally managed metadata introduces the concept of a 'container'. +A container is a collection of (normally) physical devices which have +a common set of metadata. A container is assembled as an md array, but +is left 'inactive'. + +A container can contain one or more data arrays. These are composed from +slices (partitions?) of various devices in the container. + +For example, a 5 devices DDF set can container a RAID1 using the first +half of two devices, a RAID0 using the first half of the remain 3 devices, +and a RAID5 over thte second half of all 5 devices. + +A container can be created with + + mdadm --create /dev/md0 -e ddf -n5 /dev/sd[abcde] + +or "-e imsm" to use the Intel Matrix Storage Manager. + +An array can be created within a container either by giving the +container name and the only member: + + mdadm -C /dev/md1 --level raid1 -n 2 /dev/md0 + +or by listing the component devices + + mdadm -C /dev/md2 --level raid0 -n 3 /dev/sd[cde] + +To assemble a container, it is easiest just to pass each device in turn to +mdadm -I + + for i in /dev/sd[abcde] + do mdadm -I $i + done + +This will assemble the container and the components. + +Alternately the container can be assembled explicitly + + mdadm -A /dev/md0 /dev/sd[abcde] + +Then the components can all be assembled with + + mdadm -I /dev/md0 + +For each container, mdadm will start a program called "mdmon" which will +monitor the array and effect any metadata updates needed. The array is +initially assembled readonly. It is up to "mdmon" to mark the metadata +as 'dirty' and which the array to 'read-write'. + +The version 0.90 and 1.x metadata formats supported by previous +versions for mdadm are still supported and the kernel still performs +the same updates it use to. The new 'mdmon' approach is only used for +newly introduced metadata types. + +Any testing and feedback will be greatly appreciated. + +NeilBrown 5th November 2008 + diff --git a/ReadMe.c b/ReadMe.c index e361f1dc..13f52202 100644 --- a/ReadMe.c +++ b/ReadMe.c @@ -24,7 +24,7 @@ #include "mdadm.h" -char Version[] = Name " - v3.0-devel1 - 18th September 2008\n"; +char Version[] = Name " - v3.0-devel2 - 5th November 2008\n"; /* * File: ReadMe.c diff --git a/inventory b/inventory index 0a9f788f..2d86d3aa 100755 --- a/inventory +++ b/inventory @@ -23,6 +23,7 @@ ANNOUNCE-2.6.5 ANNOUNCE-2.6.6 ANNOUNCE-2.6.7 ANNOUNCE-3.0-devel1 +ANNOUNCE-3.0-devel2 Assemble.c bitmap.c bitmap.h @@ -46,6 +47,7 @@ kernel-patch-2.6.18 kernel-patch-2.6.18.6 kernel-patch-2.6.19 kernel-patch-2.6.25 +kernel-patch-2.6.27 Kill.c makedist Makefile diff --git a/mdadm.8 b/mdadm.8 index 92e579bc..43224195 100644 --- a/mdadm.8 +++ b/mdadm.8 @@ -5,7 +5,7 @@ .\" the Free Software Foundation; either version 2 of the License, or .\" (at your option) any later version. .\" See file COPYING in distribution for details. -.TH MDADM 8 "" v3.0-devel1 +.TH MDADM 8 "" v3.0-devel2 .SH NAME mdadm \- manage MD devices .I aka diff --git a/mdadm.spec b/mdadm.spec index ba85fbf8..c290b4e3 100644 --- a/mdadm.spec +++ b/mdadm.spec @@ -1,6 +1,6 @@ Summary: mdadm is used for controlling Linux md devices (aka RAID arrays) Name: mdadm -Version: 3.0_devel1 +Version: 3.0_devel2 Release: 1 Source: http://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-%{version}.tgz URL: http://neil.brown.name/blog/mdadm diff --git a/mdassemble.8 b/mdassemble.8 index d8aa0f3a..a0d07bb6 100644 --- a/mdassemble.8 +++ b/mdassemble.8 @@ -1,5 +1,5 @@ .\" -*- nroff -*- -.TH MDASSEMBLE 8 "" v3.0-devel1 +.TH MDASSEMBLE 8 "" v3.0-devel2 .SH NAME mdassemble \- assemble MD devices .I aka -- 2.39.2