diff options
| -rw-r--r-- | ANNOUNCE-3.0-devel1 | 84 | ||||
| -rw-r--r-- | ReadMe.c | 2 | ||||
| -rwxr-xr-x | inventory | 14 | ||||
| -rw-r--r-- | mdadm.8 | 2 | ||||
| -rw-r--r-- | mdadm.spec | 2 | ||||
| -rw-r--r-- | mdassemble.8 | 2 |
6 files changed, 102 insertions, 4 deletions
diff --git a/ANNOUNCE-3.0-devel1 b/ANNOUNCE-3.0-devel1 new file mode 100644 index 0000000..89ed2e3 --- /dev/null +++ b/ANNOUNCE-3.0-devel1 @@ -0,0 +1,84 @@ +Subject: ANNOUNCE: mdadm 3.0-devel1 - A tool for managing Soft RAID under Linux + +I am pleased to announce the availability of + mdadm version 3.0-devel1 + +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 is not intended for +production use yet, but rather for testing and ongoing development. + +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. + +The manual pages have not yet been updated, but here is a brief outline. + +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] + +The 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 18th September 2008 + @@ -24,7 +24,7 @@ #include "mdadm.h" -char Version[] = Name " - v2.6.7 - 6th June 2008\n"; +char Version[] = Name " - v3.0-devel1 - 18th September 2008\n"; /* * File: ReadMe.c @@ -22,6 +22,7 @@ ANNOUNCE-2.6.4 ANNOUNCE-2.6.5 ANNOUNCE-2.6.6 ANNOUNCE-2.6.7 +ANNOUNCE-3.0-devel1 Assemble.c bitmap.c bitmap.h @@ -29,6 +30,8 @@ Build.c ChangeLog config.c COPYING +crc32.c +crc32.h Create.c Detail.c dlink.c @@ -42,10 +45,12 @@ inventory kernel-patch-2.6.18 kernel-patch-2.6.18.6 kernel-patch-2.6.19 +kernel-patch-2.6.25 Kill.c makedist Makefile Manage.c +managemon.c mapfile.c md.4 md5.h @@ -57,6 +62,8 @@ mdadm.h mdadm.spec mdassemble.8 mdassemble.c +mdmon.c +mdmon.h mdopen.c md_p.h mdstat.c @@ -64,17 +71,23 @@ md_u.h misc/ misc/syslog-events mkinitramfs +monitor.c Monitor.c +msg.c +msg.h pwgr.c Query.c raid5extend.c ReadMe.c README.initramfs restripe.c +sg_io.c sha1.c sha1.h super0.c super1.c +super-ddf.c +super-intel.c swap_super.c sysfs.c test @@ -120,6 +133,7 @@ tests/06update-uuid tests/06wrmostly tests/07autoassemble tests/07autodetect +tests/07reshape5intr tests/07testreshape5 tests/check tests/testdev @@ -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 "" v2.6.7 +.TH MDADM 8 "" v3.0-devel1 .SH NAME mdadm \- manage MD devices .I aka @@ -1,6 +1,6 @@ Summary: mdadm is used for controlling Linux md devices (aka RAID arrays) Name: mdadm -Version: 2.6.7 +Version: 3.0_devel1 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 d60c775..d8aa0f3 100644 --- a/mdassemble.8 +++ b/mdassemble.8 @@ -1,5 +1,5 @@ .\" -*- nroff -*- -.TH MDASSEMBLE 8 "" v2.6.7 +.TH MDASSEMBLE 8 "" v3.0-devel1 .SH NAME mdassemble \- assemble MD devices .I aka |