* [PATCH 0/6] Repository cleanup
@ 2024-02-23 14:51 Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 1/6] mdadm: remove ANNOUNCEs Mariusz Tkaczyk
` (6 more replies)
0 siblings, 7 replies; 12+ messages in thread
From: Mariusz Tkaczyk @ 2024-02-23 14:51 UTC (permalink / raw)
To: jes; +Cc: linux-raid, Mariusz Tkaczyk
Remove legacy files and ANNOUNCEs. They can still be reverted on demand.
Create special documentation folder and move text files out from main
directory.
Mariusz Tkaczyk (6):
mdadm: remove ANNOUNCEs
mdadm: remove TODO
mdadm: remove makedist
mdadm: remove mdadm.spec
mdadm: remove mkinitramfs stuff
mdadm: move documentation to folder
ANNOUNCE-3.0 | 98 --------
ANNOUNCE-3.0.1 | 22 --
ANNOUNCE-3.0.2 | 21 --
ANNOUNCE-3.0.3 | 29 ---
ANNOUNCE-3.1 | 33 ---
ANNOUNCE-3.1.1 | 39 ----
ANNOUNCE-3.1.2 | 46 ----
ANNOUNCE-3.1.3 | 46 ----
ANNOUNCE-3.1.4 | 37 ---
ANNOUNCE-3.1.5 | 42 ----
ANNOUNCE-3.2 | 77 -------
ANNOUNCE-3.2.1 | 75 ------
ANNOUNCE-3.2.2 | 36 ---
ANNOUNCE-3.2.3 | 24 --
ANNOUNCE-3.2.4 | 144 ------------
ANNOUNCE-3.2.5 | 31 ---
ANNOUNCE-3.2.6 | 57 -----
ANNOUNCE-3.3 | 63 ------
ANNOUNCE-3.3.1 | 23 --
ANNOUNCE-3.3.2 | 16 --
ANNOUNCE-3.3.3 | 18 --
ANNOUNCE-3.3.4 | 37 ---
ANNOUNCE-3.4 | 24 --
ANNOUNCE-4.0 | 22 --
ANNOUNCE-4.1 | 16 --
ANNOUNCE-4.2 | 19 --
README.initramfs | 122 ----------
TODO | 213 ------------------
.../external-reshape-design.txt | 0
.../mdadm.conf-example | 0
.../mdmon-design.txt | 0
makedist | 96 --------
mdadm.spec | 47 ----
mkinitramfs | 55 -----
34 files changed, 1628 deletions(-)
delete mode 100644 ANNOUNCE-3.0
delete mode 100644 ANNOUNCE-3.0.1
delete mode 100644 ANNOUNCE-3.0.2
delete mode 100644 ANNOUNCE-3.0.3
delete mode 100644 ANNOUNCE-3.1
delete mode 100644 ANNOUNCE-3.1.1
delete mode 100644 ANNOUNCE-3.1.2
delete mode 100644 ANNOUNCE-3.1.3
delete mode 100644 ANNOUNCE-3.1.4
delete mode 100644 ANNOUNCE-3.1.5
delete mode 100644 ANNOUNCE-3.2
delete mode 100644 ANNOUNCE-3.2.1
delete mode 100644 ANNOUNCE-3.2.2
delete mode 100644 ANNOUNCE-3.2.3
delete mode 100644 ANNOUNCE-3.2.4
delete mode 100644 ANNOUNCE-3.2.5
delete mode 100644 ANNOUNCE-3.2.6
delete mode 100644 ANNOUNCE-3.3
delete mode 100644 ANNOUNCE-3.3.1
delete mode 100644 ANNOUNCE-3.3.2
delete mode 100644 ANNOUNCE-3.3.3
delete mode 100644 ANNOUNCE-3.3.4
delete mode 100644 ANNOUNCE-3.4
delete mode 100644 ANNOUNCE-4.0
delete mode 100644 ANNOUNCE-4.1
delete mode 100644 ANNOUNCE-4.2
delete mode 100644 README.initramfs
delete mode 100644 TODO
rename external-reshape-design.txt => documentation/external-reshape-design.txt (100%)
rename mdadm.conf-example => documentation/mdadm.conf-example (100%)
rename mdmon-design.txt => documentation/mdmon-design.txt (100%)
delete mode 100755 makedist
delete mode 100644 mdadm.spec
delete mode 100644 mkinitramfs
--
2.35.3
^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH 1/6] mdadm: remove ANNOUNCEs
2024-02-23 14:51 [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
@ 2024-02-23 14:51 ` Mariusz Tkaczyk
2024-02-28 14:40 ` Nix
2024-02-23 14:51 ` [PATCH 2/6] mdadm: remove TODO Mariusz Tkaczyk
` (5 subsequent siblings)
6 siblings, 1 reply; 12+ messages in thread
From: Mariusz Tkaczyk @ 2024-02-23 14:51 UTC (permalink / raw)
To: jes; +Cc: linux-raid, Mariusz Tkaczyk
Release stuff is not necessary in repository. Remove it.
Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
---
ANNOUNCE-3.0 | 98 ---------------------------------
ANNOUNCE-3.0.1 | 22 --------
ANNOUNCE-3.0.2 | 21 --------
ANNOUNCE-3.0.3 | 29 ----------
ANNOUNCE-3.1 | 33 ------------
ANNOUNCE-3.1.1 | 39 --------------
ANNOUNCE-3.1.2 | 46 ----------------
ANNOUNCE-3.1.3 | 46 ----------------
ANNOUNCE-3.1.4 | 37 -------------
ANNOUNCE-3.1.5 | 42 ---------------
ANNOUNCE-3.2 | 77 --------------------------
ANNOUNCE-3.2.1 | 75 --------------------------
ANNOUNCE-3.2.2 | 36 -------------
ANNOUNCE-3.2.3 | 24 ---------
ANNOUNCE-3.2.4 | 144 -------------------------------------------------
ANNOUNCE-3.2.5 | 31 -----------
ANNOUNCE-3.2.6 | 57 --------------------
ANNOUNCE-3.3 | 63 ----------------------
ANNOUNCE-3.3.1 | 23 --------
ANNOUNCE-3.3.2 | 16 ------
ANNOUNCE-3.3.3 | 18 -------
ANNOUNCE-3.3.4 | 37 -------------
ANNOUNCE-3.4 | 24 ---------
ANNOUNCE-4.0 | 22 --------
ANNOUNCE-4.1 | 16 ------
ANNOUNCE-4.2 | 19 -------
26 files changed, 1095 deletions(-)
delete mode 100644 ANNOUNCE-3.0
delete mode 100644 ANNOUNCE-3.0.1
delete mode 100644 ANNOUNCE-3.0.2
delete mode 100644 ANNOUNCE-3.0.3
delete mode 100644 ANNOUNCE-3.1
delete mode 100644 ANNOUNCE-3.1.1
delete mode 100644 ANNOUNCE-3.1.2
delete mode 100644 ANNOUNCE-3.1.3
delete mode 100644 ANNOUNCE-3.1.4
delete mode 100644 ANNOUNCE-3.1.5
delete mode 100644 ANNOUNCE-3.2
delete mode 100644 ANNOUNCE-3.2.1
delete mode 100644 ANNOUNCE-3.2.2
delete mode 100644 ANNOUNCE-3.2.3
delete mode 100644 ANNOUNCE-3.2.4
delete mode 100644 ANNOUNCE-3.2.5
delete mode 100644 ANNOUNCE-3.2.6
delete mode 100644 ANNOUNCE-3.3
delete mode 100644 ANNOUNCE-3.3.1
delete mode 100644 ANNOUNCE-3.3.2
delete mode 100644 ANNOUNCE-3.3.3
delete mode 100644 ANNOUNCE-3.3.4
delete mode 100644 ANNOUNCE-3.4
delete mode 100644 ANNOUNCE-4.0
delete mode 100644 ANNOUNCE-4.1
delete mode 100644 ANNOUNCE-4.2
diff --git a/ANNOUNCE-3.0 b/ANNOUNCE-3.0
deleted file mode 100644
index f2d4f8475506..000000000000
--- a/ANNOUNCE-3.0
+++ /dev/null
@@ -1,98 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
-
-I am pleased to (finally) announce the availability of
- mdadm version 3.0
-
-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
-
-
-This is a major new version and as such should be treated with some
-caution. However it has seen substantial testing and is considerred
-to be ready for wide use.
-
-
-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 installed, 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.
-
-NeilBrown 2nd June 2009
diff --git a/ANNOUNCE-3.0.1 b/ANNOUNCE-3.0.1
deleted file mode 100644
index 91b44284b32e..000000000000
--- a/ANNOUNCE-3.0.1
+++ /dev/null
@@ -1,22 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.0.1 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.0.1
-
-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
-
-
-This contains only minor bug fixes over 3.0. If you are using
-3.0, you could consider upgrading.
-
-The brief change log is:
- - Fix various segfaults
- - Fixed for --examine with containers
- - Lots of other little fixes.
-
-NeilBrown 25th September 2009
diff --git a/ANNOUNCE-3.0.2 b/ANNOUNCE-3.0.2
deleted file mode 100644
index 93643d178e21..000000000000
--- a/ANNOUNCE-3.0.2
+++ /dev/null
@@ -1,21 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.0.2 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.0.2
-
-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
-
-
-This just contains one bugfix over 3.0.1 - I was obviously a bit hasty
-in releasing that one.
-
-The brief change log is:
- - Fix crash when hosthost is not set, as often happens in
- early boot.
-
-NeilBrown 25th September 2009
diff --git a/ANNOUNCE-3.0.3 b/ANNOUNCE-3.0.3
deleted file mode 100644
index d6117a1ddc29..000000000000
--- a/ANNOUNCE-3.0.3
+++ /dev/null
@@ -1,29 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.0.3 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.0.3
-
-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
-
-
-This contains a collection of bug fixes and minor enhancements over
-3.0.1.
-
-The brief change log is:
- - Improvements for creating arrays giving just a name, like 'foo',
- rather than the full '/dev/md/foo'.
- - Improvements for assembling member arrays of containers.
- - Improvements to test suite
- - Add option to change increment for RebuildNN messages reported
- by "mdadm --monitor"
- - Improvements to mdmon 'hand-over' from initrd to final root.
- - Handle merging of devices that have left an IMSM array and are
- being re-incorporated.
- - Add missing space in "--detail --brief" output.
-
-NeilBrown 22nd October 2009
diff --git a/ANNOUNCE-3.1 b/ANNOUNCE-3.1
deleted file mode 100644
index 343b85da6274..000000000000
--- a/ANNOUNCE-3.1
+++ /dev/null
@@ -1,33 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.1 - A tool for managing Soft RAID under Linux
-
-Hot on the heals of 3.0.3 I am pleased to announce the availability of
- mdadm version 3.1
-
-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
-
-
-It contains significant feature enhancements over 3.0.x
-
-The brief change log is:
- - Support --grow to change the layout of RAID4/5/6
- - Support --grow to change the chunksize of raid 4/5/6
- - Support --grow to change level from RAID1 -> RAID5 -> RAID6 and
- back.
- - Support --grow to reduce the number of devices in RAID4/5/6.
- - Support restart of these grow options which assembling an array
- which is partially grown.
- - Assorted tests of this code, and of different RAID6 layouts.
-
-Note that a 2.6.31 or later is needed to have access to these.
-Reducing devices in a RAID4/5/6 requires 2.6.32.
-Changing RAID5 to RAID1 requires 2.6.33.
-
-You should only upgrade if you need to use, or which to test, these
-features.
-
-NeilBrown 22nd October 2009
diff --git a/ANNOUNCE-3.1.1 b/ANNOUNCE-3.1.1
deleted file mode 100644
index 9e480dc0e315..000000000000
--- a/ANNOUNCE-3.1.1
+++ /dev/null
@@ -1,39 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.1.1 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.1.1
-
-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
-
-This is a bugfix release over 3.1, which was withdrawn due to serious
-bugs. So it might be best to ignore 3.1 and say that this is a significant
-feature release over 3.0.x
-
-Significant changes are:
- - RAID level conversion between RAID1, RAID5, and RAID6 are
- possible were the kernel supports it (2.6.32 at least)
- - online chunksize and layout changing for RAID5 and RAID6
- where the kernel supports it.
- - reduce the number of devices in a RAID4/5/6 array.
-
- - The default metadata is not v1.1. This metadata is stored at the
- start of the device so is safer in many ways but could interfere with
- boot loaded. The old default (0.90) is still available and fully
- supported.
-
- - The default chunksize is now 512K rather than 64K. This seems more
- appropriate for modern devices.
-
- - The default bitmap chunksize for internal bitmaps is now at least
- 64Meg as fine grained bitmaps tend to impact performance more for
- little extra gain.
-
-This release is believed to be stable and you should feel free to
-upgrade to 3.1.1.
-
-NeilBrown 19th November 2009
diff --git a/ANNOUNCE-3.1.2 b/ANNOUNCE-3.1.2
deleted file mode 100644
index 321b8bef4fae..000000000000
--- a/ANNOUNCE-3.1.2
+++ /dev/null
@@ -1,46 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.1.2 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.1.2
-
-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
-
-This is a bugfix/stability release over 3.1.1.
-
-Significant changes are:
- - The default metadata has change again (sorry about that).
- It is now v1.2 and will hopefully stay that way. It turned
- out there with boot-block issues with v1.1 which make it
- unsuitable for a default, though in many cases it is still
- suitable to use.
- - Stopping a container is not permitted when members are still
- active
- - Add 'homehost' to the valid words for the "AUTO" config file
- line. When followed by "-all", this causes mdadm to
- auto-assemble any array belonging to this host, but not
- auto-assemble anything else.
- - Fix some bugs with "--grow --chunksize=" for changing chunksize.
- - VAR_RUN can be easily changed at compile time just like ALT_RUN.
- This gives distros more flexability in how to manage the
- pid and sock files that mdmon needs.
- - Various mdmon fixes
- - Alway make bitmap 4K-aligned if at all possible.
- - If mdadm.conf lists arrays which have inter-dependencies,
- the previously had to be listed in the "right" order. Now
- any order should work.
- - Fix --force assembly of v1.x arrays which are in the process
- of recovering.
- - Add section on 'scrubbing' to 'md' man page.
- - Various command-line-option parsing improvements.
- - ... and lots of other bug fixes.
-
-
-This release is believed to be stable and you should feel free to
-upgrade to 3.1.2
-
-NeilBrown 10th March 2010
diff --git a/ANNOUNCE-3.1.3 b/ANNOUNCE-3.1.3
deleted file mode 100644
index 95b2b6c1cf6d..000000000000
--- a/ANNOUNCE-3.1.3
+++ /dev/null
@@ -1,46 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.1.3 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.1.3
-
-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
-
-This is a bugfix/stability release over 3.1.2
-
-Significant changes are:
- - mapfile now lives in a fixed location which default to
- /dev/.mdadm/map but can be changed at compile time. This
- location is choses and most distros provide it during early
- boot and preserve it through. As long a /dev exists and is
- writable, /dev/.mdadm will be created.
- Other files file communication with mdmon live here too.
- This fixes a bug reported by Debian and Gentoo users where
- udev would spin in early-boot.
- - IMSM and DDF metadata will not be recognised on partitions
- as they should only be used on whole-disks.
- - Various overflows causes by 2G drives have been addressed.
- - A subarray of an IMSM contain can now be killed with
- --kill-subarray. Also subarrays can be renamed with
- --update-subarray
- - -If (or --incremental --fail) can be used from udev to
- fail and remove from all arrays a device which has been
- unplugged from the system. i.e. hot-unplug-support.
- - "mdadm /dev/mdX --re-add missing" will look for any device
- that looks like it should be a member of /dev/mdX but isn't
- and will automatically --re-add it
- - Now compile with -Wextra to get extra warnings.
- - Lots of minor bug fixes, documentation improvements, etcc
-
-This release is believed to be stable and you should feel free to
-upgrade to 3.1.3
-
-It is expected that the next release will be 3.2 with a number of new
-features. 3.1.4 will only happen if important bugs show up before 3.2
-is stable.
-
-NeilBrown 6th August 2010
diff --git a/ANNOUNCE-3.1.4 b/ANNOUNCE-3.1.4
deleted file mode 100644
index c157a36aa636..000000000000
--- a/ANNOUNCE-3.1.4
+++ /dev/null
@@ -1,37 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.1.4 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.1.4
-
-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
-
-This is a bugfix/stability release over 3.1.3.
-3.1.3 had a couple of embarrasing regressions and a couple of other
-issues surfaces which had easy fixes so I decided to make a 3.1.4
-release after all.
-
-Two fixes related to configs that aren't using udev:
- - Don't remove md devices which 'standard' names on --stop
- - Allow dev_open to work on read-only /dev
-And fixed regressions:
- - Allow --incremental to add spares to an array
- - Accept --no-degraded as a deprecated option rather than
- throwing an error
- - Return correct success status when --incrmental assembling
- a container which does not yet have enough devices.
- - Don't link mdadm with pthreads, only mdmon needs it.
- - Fix compiler warning due to bad use of snprintf
- - Fix spare migration
-
-This release is believed to be stable and you should feel free to
-upgrade to 3.1.4
-
-It is expected that the next release will be 3.2 with a number of new
-features.
-
-NeilBrown 31st August 2010
diff --git a/ANNOUNCE-3.1.5 b/ANNOUNCE-3.1.5
deleted file mode 100644
index baa1f9218b43..000000000000
--- a/ANNOUNCE-3.1.5
+++ /dev/null
@@ -1,42 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.1.5 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.1.5
-
-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
-
-This is a bugfix/stability release over 3.1.4. It contains all the
-important bugfixes found while working on 3.2 and 3.2.1. It will be
-the last 3.1.x release - 3.2.1 is expected to be released in a few days.
-
-Changes include:
- - Fixes for v1.x metadata on big-endian machines.
- - man page improvements
- - Improve '--detail --export' when run on partitions of an md array.
- - Fix regression with removing 'failed' or 'detached' devices.
- - Fixes for "--assemble --force" in various unusual cases.
- - Allow '-Y' to mean --export. This was documented but not implemented.
- - Various fixed for handling 'ddf' metadata. This is now more reliable
- but could benefit from more interoperability testing.
- - Correctly list subarrays of a container in "--detail" output.
- - Improve checks on whether the requested number of devices is supported
- by the metadata - both for --create and --grow.
- - Don't remove partitions from a device that is being included in an
- array until we are fully committed to including it.
- - Allow "--assemble --update=no-bitmap" so an array with a corrupt
- bitmap can still be assembled.
- - Don't allow --add to succeed if it looks like a "--re-add" is probably
- wanted, but cannot succeed. This avoids inadvertently turning
- devices into spares when an array is failed.
-
-This release is believed to be stable and you should feel free to
-upgrade to 3.1.5
-
-
-NeilBrown 23rd March 2011
-
diff --git a/ANNOUNCE-3.2 b/ANNOUNCE-3.2
deleted file mode 100644
index 9e282bc68e51..000000000000
--- a/ANNOUNCE-3.2
+++ /dev/null
@@ -1,77 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.2 - A tool for managing Soft RAID under Linux (DEVEL ONLY)
-
-I am pleased to announce the availability of
- mdadm version 3.2
-
-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 devel-3.2
- http://neil.brown.name/git?p=mdadm
-
-This is a "Developers only" release. Please don't consider using it
-or making it available to others without reading the following.
-
-
-By far the most significant change in this release related to the
-management of reshaping arrays. This code has been substantially
-re-written so that it can work with 'externally managed metadata' -
-Intel's IMSM in particular. We now support level migration and
-OnLine Capacity Expansion on these arrays.
-
-However, while the code largely works it has not been tested
-exhaustively so there are likely to be problems. As the reshape code
-for native metadata arrays was changed as part of this rewrite these
-problems could also result in regressions for reshape of native
-metadata.
-
-It is partly to encourage greater testing that this release is being
-made. Any reports of problem - particular reproducible recipes for
-triggering the problems - will be gratefully received.
-
-It is hopped that a "3.2.1" release will be available in early March
-which will be a bugfix release over this and can be considered
-suitable for general use.
-
-Other changes of note:
-
- - Policy framework.
- Various policy statements can be made in the mdadm.conf to guide
- the behaviour of mdadm, particular with regards to how new devices
- are treated by "mdadm -I".
- Depending on the 'action' associated with a device (identified by
- its 'path') such need devices can be automatically re-added to and
- existing array that they previously fell out off, or automatically
- added as a spare if they appear to contain no data.
-
- - mdadm now has a limited understanding of partition tables. This
- allows the policy framework to make decisions about partitioned
- devices as well.
-
- - --incremental --remove can be told what --path the device was on,
- and this info will be recorded so that another device appearing at
- the same physical location can be preferentially added to the same
- array (provides the spare-same-slot action policy applied to the
- path).
-
- - A new flags "--invalid-backup" flag is available in --assemble
- mode. This can be used to re-assemble an array which was stopping
- in the middle of a reshape, and for which the 'backup file' is no
- longer available or is corrupted. The array may have some
- corruption in it at the point where reshape was up to, but at least
- the rest of the array will become available.
-
-
- - Various internal restructuring - more is needed.
-
-
-Any feed back and bug reports are always welcomed at:
- linux-raid@vger.kernel.org
-
-And please: don't use this in production - particularly not the
---grow functionality.
-
-NeilBrown 1st February 2011
-
-
diff --git a/ANNOUNCE-3.2.1 b/ANNOUNCE-3.2.1
deleted file mode 100644
index 0e7826ca25f5..000000000000
--- a/ANNOUNCE-3.2.1
+++ /dev/null
@@ -1,75 +0,0 @@
-
-
-I am pleased to announce the availability of
- mdadm version 3.2.1
-
-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/mdadm
-
-Many of the changes in this release are of internal interest only,
-restructuring and refactoring code and so forth.
-
-Most of the bugs found and fixed during development for 3.2.1 have been
-back-ported for the recently-release 3.1.5 so this release primarily
-provides a few new features over 3.1.5.
-
-They include:
- - policy framework
- Policy can be expressed for moving spare devices between arrays, and
- for how to handle hot-plugged devices. This policy can be different
- for devices plugged in to different controllers etc.
- This, for example, allows a configuration where when a device is plugged
- in it is immediately included in an md array as a hot spare and
- possibly starts recovery immediately if an array is degraded.
-
- - some understanding of mbr and gpt paritition tables
- This is primarly to support the new hot-plug support. If a
- device is plugged in and policy suggests it should have a partition table,
- the partition table will be copied from a suitably similar device, and
- then the partitions will hot-plug and can then be added to md arrays.
-
- - "--incremental --remove" can remember where a device was removed from
- so if a device gets plugged back in the same place, special policy applies
- to it, allowing it to be included in an array even if a general hotplug
- will not be included.
-
- - enhanced reshape options, including growing a RAID0 by converting to RAID4,
- restriping, and converting back. Also convertions between RAID0 and
- RAID10 and between RAID1 and RAID10 are possible (with a suitably recent
- kernel).
-
- - spare migration for IMSM arrays.
- Spare migration can now work across 'containers' using non-native metadata
- and specifically Intel's IMSM arrays support spare migrations.
-
- - OLCE and level migration for Intel IMSM arrays.
- OnLine Capacity Expansion and level migration (e.g. RAID0 -> RAID5) is
- supported for Intel Matrix Storage Manager arrays.
- This support is currently 'experimental' for technical reasons. It can
- be enabled with "export MDADM_EXPERIMENTAL=1"
-
- - avoid including wayward devices
- If you split a RAID1, mount the two halves as two separate degraded RAID1s,
- and then later bring the two back together, it is possible that the md
- metadata won't properly show that one must over-ride the other.
- mdadm now does extra checking to detect this possibilty and avoid
- potentially corrupting data.
-
- - remove any possible confusion between similar options.
- e.g. --brief and --bitmap were mapped to 'b' and mdadm wouldn't
- notice if one was used where the other was expected.
-
- - allow K,M,G suffixes on chunk sizes
-
-
-While mdadm-3.2.1 is considered to be reasonably stable, you should
-only use it if you want to try out the new features, or if you
-generally like to be on the bleeding edge. If the new features are not
-important to you, then 3.1.5 is probably the appropriate version to be using
-until 3.2.2 comes out.
-
-NeilBrown 28th March 2011
diff --git a/ANNOUNCE-3.2.2 b/ANNOUNCE-3.2.2
deleted file mode 100644
index b70d18b95bff..000000000000
--- a/ANNOUNCE-3.2.2
+++ /dev/null
@@ -1,36 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.2.2 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.2.2
-
-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/mdadm
-
-This release is largely a stablising release for the 3.2 series.
-Many of the changes just fix bugs introduces in 3.2 or 3.2.1.
-
-There are some new features. They are:
- - reshaping IMSM (Intel metadata) arrays is no longer 'experimental',
- it should work properly and be largely compatible with IMSM drivers in
- other platforms.
- - --assume-clean can be used with --grow --size to avoid resyncing the
- new part of the array. This is only support with very new kernels.
- - RAID0 arrays can have chunksize which is not a power of 2. This has been
- supported in the kernel for a while but is only now supprted by
- mdadm.
-
- - A new tool 'raid6check' is available which can check a RAID6 array,
- or part of it, and report which device is most inconsistent with the
- others if any stripe is inconsistent. This is still under development
- and does not have a man page yet. If anyone tries it out and has any
- questions or experience to report, they would be most welcome on
- linux-raid@vger.kernel.org.
-
-Future releases in the 3.2 series will only be made if bugfixes are needed.
-The next release to add features is expected to be 3.3.
-
-NeilBrown 17th June 2011
diff --git a/ANNOUNCE-3.2.3 b/ANNOUNCE-3.2.3
deleted file mode 100644
index 8a8dba4661cd..000000000000
--- a/ANNOUNCE-3.2.3
+++ /dev/null
@@ -1,24 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.2.3 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.2.3
-
-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/mdadm
-
-This release is largely a bugfix release for the 3.2 series with many
-minor fixes with little or no impact.
-
-The largest single area of change is support for reshape of Intel
-IMSM arrays (OnLine Capacity Explansion and Level Migtration).
-Among other fixes, this now has a better chance of surviving if a
-device fails during reshape.
-
-Upgrading is recommended - particularly if you use mdadm for IMSM
-arrays - but not essential.
-
-NeilBrown 23rd December 2011
diff --git a/ANNOUNCE-3.2.4 b/ANNOUNCE-3.2.4
deleted file mode 100644
index e321678604c0..000000000000
--- a/ANNOUNCE-3.2.4
+++ /dev/null
@@ -1,144 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.2.4
-
-It is available at the usual places, now including github:
- countrycode=xx.
- http://www.${countrycode}kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://github.com/neilbrown/mdadm
- git://neil.brown.name/mdadm
- http://neil.brown.name/git/mdadm
-
-This release is largely a bugfix release for the 3.2 series with many
-minor fixes with little or no impact.
-
-"--oneline" log of changes is below. Some notable ones are:
-
- - --offroot argument to improve interactions between mdmon and initrd
- - --prefer argument to select which /dev names to display in some
- circumstances.
- - relax restructions on when "--add" will be allowed
- - Fix bug with adding write-intent-bitmap to active array
- - Now defaults to "/run/mdadm" for storing run-time files.
-
-Upgrading is encouraged.
-
-The next mdadm release is expected to be 3.3 with a number of new
-features.
-
-NeilBrown 9th May 2012
-
-77b3ac8 monitor: make return from read_and_act more symbolic.
-68226a8 monitor: ensure we retry soon when 'remove' fails.
-8453f8d fix: Monitor sometimes crashes
-90fa1a2 Work around gcc-4.7's strict aliasing checks
-0c4304c fix: container creation with --incremental used.
-5d1c7cd FIX: External metadata sometimes is not updated
-3c20f98 FIX: mdmon check in reshape_container() can cause a problem
-59ab9f5 FIX: Typo error in fprint command
-9587c37 imsm: load_super_imsm_all function refactoring
-ec50f7b imsm: load_imsm_super_all supports loading metadata from the device list
-ca9de18 imsm: validate the number of imsm volumes per controller
-30602f5 imsm: display fd in error trace when when store_imsm_mpb failes
-eb155f6 mdmon: Use getopt_long() to parse command line options
-08ca2ad Add --offroot argument to mdadm
-da82751 Add --offroot argument to mdmon
-a0963a8 Spawn mdmon with --offroot if mdadm was launched with --offroot
-f878b24 imsm: fix, the second array need to have the whole available space on devices
-d597705 getinfo_super1: Use MaxSector in place of sb->size
-6ef8905 super1: make aread/awrite always use an aligned buffer.
-de5a472 Remove avail_disks arg from 'enough'.
-da8fe5a Assemble: fix --force assemble during reshape.
-b10c663 config: fix handing of 'homehost' in AUTO line.
-92d49ec FIX: NULL pointer to strdup() can be passed
-d2bde6d imsm: FIX: No new missing disks are allowed during general migration
-111e9fd FIX: Array is not run when expansion disks are added
-bf5cf7c imsm: FIX: imsm_get_allowed_degradation() doesn't count degradation for raid1
-50927b1 Fix: Sometimes mdmon throws core dump during reshape
-78340e2 Flush mdmon before next reshape step during container operation
-e174219 imsm: FIX: Chunk size migration problem
-f93346e FIX: use md position to reshape restart
-6a75c8c imsm: FIX: use md position to reshape restart
-51d83f5 imsm: FIX: Clear migration record when migration switches to next volume.
-e1dd332 FIX: restart reshape when reshape process is stopped just between 2 reshapes
-1ca90aa FIX: Do not try to (continue) reshape using inactive array
-9f1b0f0 config: conf_match should ignore devname when not set.
-d669228 Use posix_memalign() for memory used to write bitmaps
-178950e FIX: Changes in '0' case for reshape position verification
-9200d41 avoid double-free upon "old buggy kernel" sysfs_read failure
-4011421 Print error message if failing to write super for 1.x metadata
-0011874 Use MDMON_DIR for pid files created in Monitor.c
-56d1885 Assemble: don't use O_EXCL until we have checked device content.
-b720636 Assemble: support assembling of a RAID0 being reshaped.
-c69ffac Manage: allow --re-add to failed array.
-52f07f5 Reset bad flag on map update
-911cead super1: support superblocks up to 4K.
-ad6db3c Create: reduce the verbosity of 'default_layout'.
-b2bfdfa super1.c don't keep recalculating bitmap pointer
-4122675 Define and use SUPER1_SIZE for allocations
-1afa930 init_super1() memset full buffer allocated for superblock
-2de0b8a match_metadata_desc1(): Use calloc instead of malloc+memset
-3c0bcd4 Use 4K buffer alignment for superblock allocations
-308340a Use struct align_fd to cache fd's block size for aligned reads/writes
-65ed615 match_metadata_desc0(): Use calloc instead of malloc+memset
-de89706 Generalize ROUND_UP() macro and introduce matching ROUND_UP_PTR()
-0a2f189 super1.c: use ROUND_UP/ROUND_UP_PTR
-654a381 super-intel.c: Use ROUND_UP() instead of manually coding it
-42d5dfd __write_init_super_ddf(): Use posix_memalign() instead of static aligned buffer
-d4633e0 Examine: fix array size calculation for RAID10.
-e62b778 Assemble: improve verbose logging when including old devices.
-0073a6e Remove possible crash during RAID6 -> RAID5 reshape.
-69fe207 Incremental: fix adding devices with --incremental
-bcbb311 Manage: replace 'return 1' with 'goto abort'.
-9f58469 Manage: freeze recovery while adding multiple devices.
-ae6c05a Create: round off size for RAID1 arrays.
-5ca3a90 Grow: print useful error when converting RAID1->RAID5 will fail.
-c07d640 Fix tests/05r1-re-add-nosupper
-2d762ad Fix the new ROUND_UP macro.
-fd324b0 sysfs: fixed sysfs_freeze_array array to work properly with Manage_subdevs.
-5551b11 imsm: avoid overflows for disks over 1TB
-97f81ee clear hi bits if not used after loading metadata from disk
-e03640b simplify calculating array_blocks
-29cd082 show 2TB volumes/disks support in --detail-platform
-2cc699a check volume size in validate_geometry_imsm_orom
-9126b9a check that no disk over 2TB is used to create container when no support
-027c374 imsm: set 2tb disk attribute for spare
-3556c2f Fix typo: wan -> want
-15632a9 parse_size: distinguish between 0 and error.
-fbdef49 Bitmap_offset is a signed number
-508a7f1 super1: leave more space in front of data by default.
-40110b9 Fix two typos in fprintf messages
-342460c mdadm man page: fix typo
-0e7f69a imsm: display maximum volumes per controller and array
-36fd8cc imsm: FIX: Update function imsm_num_data_members() for Raid1/10
-7abc987 imsm: FIX: Add volume size expand support to imsm_analyze_change()
-f3871fd imsm: Add new metadata update for volume size expansion
-54397ed imsm: Execute size change for external metatdata
-016e00f FIX: Support metadata changes rollback
-fbf3d20 imsm: FIX: Support metadata changes rollback
-44f6f18 FIX: Extend size of raid0 array
-7e7e9a4 FIX: Respect metadata size limitations
-65a9798 FIX: Detect error and rollback metadata
-13bcac9 imsm: Add function imsm_get_free_size()
-b130333 imsm: Support setting max size for size change operation
-c41e00b imsm: FIX: Component size alignment check
-58d26a2 FIX: Size change is possible as standalone change only
-4aecb54 FIX: Assembled second array is in read only state during reshape
-ae2416e FIX: resolve make everything compilation error
-480f356 Raid limit of 1024 when scanning for devices.
-c2ecf5f Add --prefer option for --detail and --monitor
-0a99975 Relax restrictions on when --add is permitted.
-7ce0570 imsm: fix: rebuild does not continue after reboot
-b51702b fix: correct extending size of raid0 array
-34a1395 Fix sign extension of bitmap_offset in super1.c
-012a864 Introduce sysfs_set_num_signed() and use it to set bitmap/offset
-5d7b407 imsm: fix: thunderdome may drop 2tb attribute
-5ffdc2d Update test for "is udev active".
-96fd06e Adjust to new standard of /run
-974e039 test: don't worry too much about array size.
-b0a658f Grow: failing the set the per-device size is not an error.
-36614e9 super-intel.c: Don't try to close negative fd
-562aa10 super-intel.c: Fix resource leak from opendir()
-
diff --git a/ANNOUNCE-3.2.5 b/ANNOUNCE-3.2.5
deleted file mode 100644
index 396da12a6f61..000000000000
--- a/ANNOUNCE-3.2.5
+++ /dev/null
@@ -1,31 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.2.5 - A tool for managing Soft RAID under Linux
-
-I am somewhat disappointed to have to announce the availability of
- mdadm version 3.2.5
-
-It is available at the usual places, now including github:
- countrycode=xx.
- http://www.${countrycode}kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://github.com/neilbrown/mdadm
- git://neil.brown.name/mdadm
- http://neil.brown.name/git/mdadm
-
-This release primarily fixes a serious regression in 3.2.4.
-This regression does *not* cause any risk to data. It simply
-means that adding a device with "--add" would sometime fail
-when it should not.
-
-The fix also includes a couple of minor fixes such as making
-the "--layout=preserve" option to "--grow" work again.
-
-A reminder that the default location for runtime files is now
-"/run/mdadm". If you compile this for a distro that does not
-have "/run", you will need to compile with an alternate setting for
-MAP_DIR. e.g.
- make MAP_DIR=/var/run/mdadm
-or
- make MAP_DIR=/dev/.mdadm
-
-NeilBrown 18th May 2012
-
diff --git a/ANNOUNCE-3.2.6 b/ANNOUNCE-3.2.6
deleted file mode 100644
index f5cfd4920576..000000000000
--- a/ANNOUNCE-3.2.6
+++ /dev/null
@@ -1,57 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.2.6 - A tool for managing Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.2.6
-
-It is available at the usual places, now including github:
- countrycode=xx.
- http://www.${countrycode}kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://github.com/neilbrown/mdadm
- git://neil.brown.name/mdadm
- http://neil.brown.name/git/mdadm
-
-This is a stablity release which adds a number of bugfixs to 3.2.5.
-There are no real stand-out fixes, just lots of little bits and pieces.
-
-Below is the "git log --oneline --reverse" list of changes since
-3.2.5.
-
-NeilBrown 25th October 2012
-
-b7e05d2 udev-rules: prevent systemd from mount devices before they are ready.
-0d478e2 mdadm: Fix Segmentation fault.
-42f0ca1 imsm: fix: correct checking volume's degradation
-fcf2195 Monitor: fix inconsistencies in values for ->percent
-5f862fb Monitor: Report NewArray when an array the disappeared, reappears.
-6f51b1c Monitor: fix reporting for Fail vs FailSpare etc.
-68ad53b mdmon: fix arg parsing.
-517f135 Assemble: don't leak memory with fdlist.
-090900c udev-rules: prevent systemd from mount devices before they are ready.
-446e000 sha1.h: remove ansidecl.h header inclusion
-ec894f5 Manage: zero metadata before adding to 'external' array.
-3a84db5 ddf: allow a non-spare to be used to recovery a missing device.
-c5d61ca ddf: hack to fix container recognition.
-23084aa mdmon: fix arg processing for -a
-c4e96a3 mdmon: allow --takeover when original was started with --offroot
-80841df find_free_devnum: avoid auto-using names in /etc/mdadm.conf
-c5c56d6 mapfile: fix mapfile rebuild for containers
-aec89f6 fix segfaults in Detail()
-2117ad1 Fix 'enough' function for RAID10.
-0bc300d Use --offroot flag when assembling md arrays via --incrmental
-ac78f24 Grow: make warning about old metadata more explicit.
-14026ab Replace sha1.h with slightly older version.
-6f6809f Add zlib license to crc32.c
-5267ba0 Handles spaces in array names better.
-c51f288 imsm: allow --assume-clean to work.
-acf7076 Grow: allow --grow --continue to work for native metadata.
-335d2a6 Grow: fix a couple of typos with --assume-clean usage
-9ff1427 Fix open_container
-3713633 mdadm: super0: do not override uuid with homehost
-31bff58 Trivial bugfix and spelling fixes.
-e1e539f Detail: don't report a faulty device as 'spare' or 'rebuilding'.
-22a6461 super0: allow creation of array on 2TB+ devices.
-a5d47a2 Create new md devices consistently
-eb48676 Monitor: don't complain about non-monitorable arrays in mdadm.conf
-ecdf2d7 Query: don't be confused by partition tables.
-f7b75c1 Query: allow member of non-0.90 arrays to be better reported.
diff --git a/ANNOUNCE-3.3 b/ANNOUNCE-3.3
deleted file mode 100644
index f770aa13137f..000000000000
--- a/ANNOUNCE-3.3
+++ /dev/null
@@ -1,63 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.3 - A tools for managing md Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.3
-
-It is available at the usual places:
- http://www.kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://github.com/neilbrown/mdadm
- git://neil.brown.name/mdadm
- http://git.neil.brown.name/git/mdadm
-
-This is a major new release so don't be too surprised if there are a
-few issues. If I hear about them they will be fixed in 3.3.1.
-git log reports nearly 500 changes since 3.2.6 so I won't list them
-all.
-
-Some highlights are:
-
-- Some array reshapes can proceed without needing backup file.
- This is done by changing the 'data_offset' so we never need to write
- any data back over where it was before. If there is no "head space"
- or "tail space" to allow data_offset to change, the old mechanism
- with a backup file can still be used.
-- RAID10 arrays can be reshaped to change the number of devices,
- change the chunk size, or change the layout between 'near'
- and 'offset'.
- This will always change data_offset, and will fail if there is no
- room for data_offset to be moved.
-- "--assemble --update=metadata" can convert a 0.90 array to a 1.0 array.
-- bad-block-logs are supported (but not heavily tested yet)
-- "--assemble --update=revert-reshape" can be used to undo a reshape
- that has just been started but isn't really wanted. This is very
- new and while it passes basic tests it cannot be guaranteed.
-- improved locking between --incremental and --assemble
-- uses systemd to run "mdmon" if systemd is configured to do that.
-- kernel names of md devices can be non-numeric. e.g. "md_home" rather than
- "md0". This will probably confuse lots of other tools, so you need to
- echo CREATE names=yes >> /etc/mdadm.conf
- or the feature will not be used. (you also need a reasonably new kernel).
-- "--stop" can be given a kernel name instead of a device name. i.e
- mdadm --stop md4
- will work even if /dev/md4 doesn't exist.
-- "--detail --export" has some information about the devices in the array
-- --dump and --restore can be used to backup and restore the metadata on an
- array.
-- Hot-replace is supported with
- mdadm /dev/mdX --replace /dev/foo
- and
- mdadm /dev/mdX --replace /dev/foo --with /dev/bar
-- Config file can be a directory in which case all "*.conf" files are
- read in lexical order.
- Default is to read /etc/mdadm.conf and then /etc/mdadm.conf.d
- Thus
- echo CREATE name=yes > /etc/mdadm.conf.d/names.conf
- will also enable the use of named md devices.
-
-- Lots of improvements to DDF support including adding support for
- RAID10 (thanks Martin Wilck).
-
-and lots of bugfixes and other little changes.
-
-NeilBrown 3rd September 2013
diff --git a/ANNOUNCE-3.3.1 b/ANNOUNCE-3.3.1
deleted file mode 100644
index 7d5e666ed1b5..000000000000
--- a/ANNOUNCE-3.3.1
+++ /dev/null
@@ -1,23 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.3.1 - A tool for managing md Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.3.1
-
-It is available at the usual places:
- http://www.kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://github.com/neilbrown/mdadm
- git://neil.brown.name/mdadm
- http://git.neil.brown.name/git/mdadm.git
-
-The main changes are:
- - lots of work on "DDF" support. Hopefully it will be more stable
- now. Bug reports are always welcome.
- - improved interactions with 'systemd'. Where possible, background
- tasks are run from systemd (if it is present) rather then forking
- disassociationg from the session. This is important because udev
- doesn't really let you disassociate.
-
-though there are a number of other little bug fixes too.
-
-NeilBrown 5th June 2014
diff --git a/ANNOUNCE-3.3.2 b/ANNOUNCE-3.3.2
deleted file mode 100644
index 6b549611ef13..000000000000
--- a/ANNOUNCE-3.3.2
+++ /dev/null
@@ -1,16 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.3.2 - A tool for managing md Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.3.2
-
-It is available at the usual places:
- http://www.kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://github.com/neilbrown/mdadm
- git://neil.brown.name/mdadm
- http://git.neil.brown.name/git/mdadm.git
-
-Changes since 3.3.1 are mostly little bugfixes and some man-page
-updates.
-
-NeilBrown 21st August 2014
diff --git a/ANNOUNCE-3.3.3 b/ANNOUNCE-3.3.3
deleted file mode 100644
index ac1b2173b5c0..000000000000
--- a/ANNOUNCE-3.3.3
+++ /dev/null
@@ -1,18 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.3.3 - A tool for managing md Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.3.3
-
-It is available at the usual places:
- http://www.kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://github.com/neilbrown/mdadm
- git://neil.brown.name/mdadm
- http://git.neil.brown.name/git/mdadm.git
-
-The 100 changes since 3.3.3 are mostly little bugfixes and some improvements
-to the selftests.
-raid6check now handle all RAID6 layouts including DDF correctly.
-See git log for the rest.
-
-NeilBrown 24th July 2015
diff --git a/ANNOUNCE-3.3.4 b/ANNOUNCE-3.3.4
deleted file mode 100644
index 52b94562af51..000000000000
--- a/ANNOUNCE-3.3.4
+++ /dev/null
@@ -1,37 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.3.4 - A tool for managing md Soft RAID under Linux
-
-I am somewhat disappointed to have to announce the availability of
- mdadm version 3.3.4
-
-It is available at the usual places:
- http://www.kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://github.com/neilbrown/mdadm
- git://neil.brown.name/mdadm
- http://git.neil.brown.name/git/mdadm.git
-
-In mdadm-3.3 a change was made to how IMSM (Intel Matrix Storage
-Manager) metadata was handled. Previously an IMSM array would only
-be assembled if it was attached to an IMSM controller.
-
-In 3.3 this was relaxed as there are circumstances where the
-controller is not properly detected. Unfortunately this has negative
-consequences which have only just come to light.
-
-If you have an IMSM RAID1 configured and then disable RAID in the
-BIOS, the metadata will remain on the devices. If you then install
-some other OS on one device and then install Linux on the other, Linux
-might eventually start noticing the IMSM metadata (depending a bit on whether
-mdadm is included in the initramfs) and might start up the RAID1. This could
-copy one device over the other, thus trashing one of the installations.
-
-Not good.
-
-So with this release IMSM arrays will only be assembled if attached to
-an IMSM controller, or if "--force" is given to --assemble, or if the
-environment variable IMSM_NO_PLATFORM is set (used primarily for
-testing).
-
-I strongly recommend upgrading to 3.3.4 if you are using 3.3 or later.
-
-NeilBrown 3rd August 2015.
diff --git a/ANNOUNCE-3.4 b/ANNOUNCE-3.4
deleted file mode 100644
index 2689732de524..000000000000
--- a/ANNOUNCE-3.4
+++ /dev/null
@@ -1,24 +0,0 @@
-Subject: ANNOUNCE: mdadm 3.4 - A tool for managing md Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 3.4
-
-It is available at the usual places:
- http://www.kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://github.com/neilbrown/mdadm
- git://neil.brown.name/mdadm
- http://git.neil.brown.name/git/mdadm
-
-The new second-level version number reflects significant new
-functionality, particular support for journalled RAID5/6 and clustered
-RAID1. This new support is probably still buggy. Please report bugs.
-
-There are also a number of fixes for Intel's IMSM metadata support,
-and an assortment of minor bug fixes.
-
-I plan for this to be the last release of mdadm that I provide as I am
-retiring from MD and mdadm maintenance. Jes Sorensen has volunteered
-to oversee mdadm for the next while. Thanks Jes!
-
-NeilBrown 28th January 2016
diff --git a/ANNOUNCE-4.0 b/ANNOUNCE-4.0
deleted file mode 100644
index f79c5408c923..000000000000
--- a/ANNOUNCE-4.0
+++ /dev/null
@@ -1,22 +0,0 @@
-Subject: ANNOUNCE: mdadm 4.0 - A tool for managing md Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 4.0
-
-It is available at the usual places:
- http://www.kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://git.kernel.org/pub/scm/utils/mdadm/mdadm.git
- http://git.kernel.org/cgit/utils/mdadm/
-
-The update in major version number primarily indicates this is a
-release by it's new maintainer. In addition it contains a large number
-of fixes in particular for IMSM RAID and clustered RAID support. In
-addition this release includes support for IMSM 4k sector drives,
-failfast and better documentation for journaled RAID.
-
-This is my first release of mdadm. Please thank Neil Brown for his
-previous work as maintainer and blame me for all the bugs I caused
-since taking over.
-
-Jes Sorensen, 2017-01-09
diff --git a/ANNOUNCE-4.1 b/ANNOUNCE-4.1
deleted file mode 100644
index a273b9a008ec..000000000000
--- a/ANNOUNCE-4.1
+++ /dev/null
@@ -1,16 +0,0 @@
-Subject: ANNOUNCE: mdadm 4.1 - A tool for managing md Soft RAID under Linux
-
-I am pleased to announce the availability of
- mdadm version 4.1
-
-It is available at the usual places:
- http://www.kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://git.kernel.org/pub/scm/utils/mdadm/mdadm.git
- http://git.kernel.org/cgit/utils/mdadm/
-
-The update constitutes more than one year of enhancements and bug fixes
-including for IMSM RAID, Partial Parity Log, clustered RAID support,
-improved testing, and gcc-8 support.
-
-Jes Sorensen, 2018-10-01
diff --git a/ANNOUNCE-4.2 b/ANNOUNCE-4.2
deleted file mode 100644
index 8b22d09ffef2..000000000000
--- a/ANNOUNCE-4.2
+++ /dev/null
@@ -1,19 +0,0 @@
-Subject: ANNOUNCE: mdadm 4.2 - A tool for managing md Soft RAID under Linux
-
-I am pleased to finally announce the availability of mdadm-4.2.
-get 4.2 out the door soon.
-
-It is available at the usual places:
- http://www.kernel.org/pub/linux/utils/raid/mdadm/
-and via git at
- git://git.kernel.org/pub/scm/utils/mdadm/mdadm.git
- http://git.kernel.org/cgit/utils/mdadm/
-
-The release includes more than two years of development and bugfixes,
-so it is difficult to remember everything. Highlights include
-enhancements and bug fixes including for IMSM RAID, Partial Parity
-Log, clustered RAID support, improved testing, and gcc-9 support.
-
-Thank you everyone who contributed to this release!
-
-Jes Sorensen, 2021-12-30
--
2.35.3
^ permalink raw reply related [flat|nested] 12+ messages in thread
* [PATCH 2/6] mdadm: remove TODO
2024-02-23 14:51 [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 1/6] mdadm: remove ANNOUNCEs Mariusz Tkaczyk
@ 2024-02-23 14:51 ` Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 3/6] mdadm: remove makedist Mariusz Tkaczyk
` (4 subsequent siblings)
6 siblings, 0 replies; 12+ messages in thread
From: Mariusz Tkaczyk @ 2024-02-23 14:51 UTC (permalink / raw)
To: jes; +Cc: linux-raid, Mariusz Tkaczyk
This file is not updated in 16 years.
No reasons to keep it. Remove it.
Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
---
TODO | 213 -----------------------------------------------------------
1 file changed, 213 deletions(-)
delete mode 100644 TODO
diff --git a/TODO b/TODO
deleted file mode 100644
index 279d20db9989..000000000000
--- a/TODO
+++ /dev/null
@@ -1,213 +0,0 @@
- - add 'name' field to metadata type and use it.
- - use validate_geometry more
- - metadata should be able to check/reject bitmap stuff.
-
-DDF:
- Three new metadata types:
- ddf - used only to create a container.
- ddf-bvd - used to create an array in a container
- ddf-svd - used to create a secondary array from bvds.
-
- Usage:
- mdadm -C /dev/ddf1 /dev/sd[abcdef]
- mdadm -C /dev/md1 -e ddf /dev/sd[a-f]
- mdadm -C /dev/md1 -l container /dev/sd[a-f]
-
- Each of these create a new ddf container using all those
- devices. The name 'ddf*' signals that ddf metadata should be used.
- '-e ddf' only supports one level - 'container'. 'container' is only
- supported by ddf.
-
- mdadm -C /dev/md1 -l0 -n4 /dev/ddf1 # or maybe not ???
- mdadm -C /dev/md1 -l1 -n2 /dev/sda /dev/sdb
- If exactly one device is given, and it is a container, we select
- devices from that container.
- If devices are given that are already in use, they must be in use by
- a container, and the array is created in the container.
- If devices given are bvds, we slip under the hood to make
- the svd arrays.
-
- mdadm -A /dev/ddf ......
- base drives make a container. Anything in that container is started
- auto-read-only.
- if /dev/ddf is already assembled, we assemble bvds and svds inside it.
-
-
-2005-dec-20
- Want an incremental assembly mode to work nicely with udev.
- Core usage would be something like
- mdadm --incr-assemble /dev/newdevice
- This would
- - examine the device to determine uuid etc.
- - look for a match in /etc/mdadm.conf, abort if not found
- - find that device and collect current contents
- - perform an 'assemble' analysis to make sure we have the best set of devices.
- - remove or add devices as appropriate
- - possibly start the array if it was complete
-
- Other usages could involve
- - specify which array to auto-add to.
- This requires an existing array for uuid matching... is there any point?
-
- -
-
-
-2004-june-02
- * Don't print 'errors' flag, it is meaningless. DONE
- * Handle new superblock format
- * create device file on demand, particularly partitionable devices. DONE
- BUT figure a way to create the partition devices.
- auto=partN
- * Use Event: interface to listen for events. DONE, untested
- * Make sure mdadm -As can assemble multi-level RAIDs ok.
- * --build to build raid1 or multipath arrays
- clean or not ???
-
-----------------------------------------------------------------------------
-* mdadm --monitor to monitor failed multipath paths and re-instate them.
-
-* Maybe make "--help" fit in 80x24 and have a --long-help with more info. DONE
-
-
-* maybe "missing" instead of <bold>missing</> in doco DONE
-* possibly wait for resync to start, or even finish while assembling.- NO
-
-* -Db should have a devices= entry if possible. - DONE
-* when assembling multipath arrays, ignore any error indicators. - DONE
-* rationalise --monitor usage:
- mdadm --monitor
- doesn't do as expected. DONE
-
-* --assemble could have a --update option. - DONE
- following word can be:
- sparc2.2
- super-minor
-
-* mdadm /dev/md11, where md11 is raid0 can segfault, particularly when looking in the
- [UU_UUU] string ... which doesn't exist !
-It should be more sensible. DONE
-
-Example:
-
-from Raimund Sacherer <raimund.sacherer@ngit.at>
-
-mke2fs -m0 -q /dev/ram1 300
-mount -n -t ext2 /dev/ram1 /tmp
-echo DEVICE /dev/[sh]* >> /tmp/mdadm.conf
-mdadm -Esb /dev/[sh]* 2>/dev/null >> /tmp/mdadm.conf
-mdadm -ARsc /tmp/mdadm.conf
-umount /tmp
-
-
-?? Allow -S /dev/md? - current complains subsequent not a/d/r - DONE
-
-* new "Query" mode to subsume --detail and --examine.
- --query or -Q, takes a device and tells if it is an MD device,
- and also tells in a raid superblock is found.
- DONE
-
-* write mdstat.c to parse /proc/mdstat file
- Build list of arrays: name, rebuild-percent
- DONE
-
-* parse /proc/partitions and map major/minor into /dev/* names,
- and use that for default DEVICE list ????
-
-* --detail --scan to read /proc/mdstat, and then iterate over these,
- but assume --brief. --verbose can override
- check each subdevice to see if it is in conf_get_devs.
- Warn if not.
- DONE, but don't warn yet...
-
-* Support multipath ... maybe...
- maybe DONE
-
-* --follow to syslog
-
-* --follow to move spares around DONE
-
-* --follow to notice other events: DONE
- rebuild started
- spare activated
- spare removed
- spare added
-
-------------------------------------
-- --examine --scan scans all drives and build an mdadm.conf file DONE
-
-- check superblock checksum in examine DONE
-- report "chunk" or "rounding" depending on raid level DONE
-- report "linear" instead of "-1" for raid level DONE
-- decode ayout depending on raid level DONE
-- --verbose and --force flags. DONE
-
-- set md_minor, *_disks for Create - DONE
-- for create raid5, how to choose between
- all working, but not insync
- one missing, one spare, insync DONE (--force)
-- and for raid1 - some failed drives... (missing)
-
-- when RUN_ARRAY, make sure *_disks counts are right
-
-- get --detail to extract extra stuff from superblock,
- like uuid DONE
-- --detail --brief to give a config file line DONE
-- parse config file. DONE
-- test...
-
-- when --assemble --scan, if an underlying device is an md device,
- then try to assemble that device first.
-
-
-- mdadm -S /dev/md0 /dev/md1 gives internal error FIXED
-
-- mdadm --detail --scan print summary of what it can find? DONE
-
-
----------
-Assemble doesn't add spares. - DONE
-Create to allow "missing" name for devices.
-Create to accept "--force" for do exactly what is requested
-- get Assemble to upgrade devices if force flag.
-ARRAY lines in config file to have super_minor=n
-ARRAY lines in config file to have device=pattern, and only accept
- those devices
- If UUID given, insist on that
- If not, but super_minor given, require all found with that minor
- to have same uuid
- If only device given, all valid supers on those devices must have
- same uuid
-allow /dev/mdX as first argument before any options
-Possible --dry-run option for create and assemble--force
-
-Assemble to check that all devices mentioned in superblock
- are present.
-
-New mode: --Monitor (or --Follow)
- Periodically check status of all arrays (listed in config file).
- Log every event and apparent cause - or differences
- Email and alert - or run a program - for important events
- Move spares around if necessary.
-
- An Array line can have a spare-group= field that indicates that
- the array shares spares with other arrays with the same
- spare-group name.
- If an array has a failed and no spares, then check all other
- arrays in the spare group. If one has no failures and a spare,
- then consider that spare.
- Choose the smallest considered spare that is large enough.
- If there is one, then hot-remove it from it's home, and
- hot-add it to the array in question.
-
- --mail-to address
- --alert-handler program
-
- Will also extract information from /proc/mdstat if present,
- and consider 20% marks in rebuild as events.
-
- Events are:
- drive fails - causes mail to be sent
- rebuild started
- spare activated
- spare removed
- spare added
--
2.35.3
^ permalink raw reply related [flat|nested] 12+ messages in thread
* [PATCH 3/6] mdadm: remove makedist
2024-02-23 14:51 [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 1/6] mdadm: remove ANNOUNCEs Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 2/6] mdadm: remove TODO Mariusz Tkaczyk
@ 2024-02-23 14:51 ` Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 4/6] mdadm: remove mdadm.spec Mariusz Tkaczyk
` (3 subsequent siblings)
6 siblings, 0 replies; 12+ messages in thread
From: Mariusz Tkaczyk @ 2024-02-23 14:51 UTC (permalink / raw)
To: jes; +Cc: linux-raid, Mariusz Tkaczyk
Archives are generated kernel.org automation, no need to submit
them manually, so remove legacy solution.
Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
---
makedist | 96 --------------------------------------------------------
1 file changed, 96 deletions(-)
delete mode 100755 makedist
diff --git a/makedist b/makedist
deleted file mode 100755
index 0c4b39eba9a9..000000000000
--- a/makedist
+++ /dev/null
@@ -1,96 +0,0 @@
-#!/bin/sh
-# avoid silly sorting
-export LANG=C
-arg=$1
-target=~/public_html/source/mdadm
-if [ " $arg" = " test" ]
-then
- target=/tmp/mdadm-test
- rm -rf $target
- mkdir -p $target
-fi
-if [ -d $target ]
-then :
-else echo $target is not a directory
- exit 2
-fi
-set `grep '^#define VERSION' ReadMe.c `
-version=`echo $3 | sed -e 's/"//g'`
-grep "^.TH MDADM 8 .. v$version" mdadm.8.in > /dev/null 2>&1 ||
- {
- echo mdadm.8.in does not mention version $version.
- exit 1
- }
-grep "^.TH MDMON 8 .. v$version" mdmon.8 > /dev/null 2>&1 ||
- {
- echo mdmon.8 does not mention version $version.
- exit 1
- }
-rpmv=`echo $version | tr - _`
-grep "^Version: *$rpmv$" mdadm.spec > /dev/null 2>&1 ||
- {
- echo mdadm.spec does not mention version $version.
- exit 1
- }
-if [ -f ANNOUNCE-$version ]
-then :
-else
- echo ANNOUNCE-$version does not exist
- exit 1
-fi
-if grep "^ANNOUNCE-$version\$" inventory
-then :
-else { cat inventory ; echo ANNOUNCE-$version ; } | sort -o inventory
-fi
-
-echo version = $version
-base=mdadm-$rpmv.tar.gz
-if [ " $arg" != " diff" ]
-then
- if [ -f $target/$base ]
- then
- echo $target/$base exists.
- exit 1
- fi
- trap "rm $target/$base; exit" 1 2 3
- git archive --prefix=mdadm-$rpmv/ HEAD | gzip --best > $target/$base
- chmod a+r $target/$base
- ls -l $target/$base
- if tar tzf $target/$base | sed 's,[^/]*/,,' | sort | diff -u inventory -
- then : correct files found
- else echo "Extra files, or inventory is out-of-date"
- rm $target/$base
- exit 1
- fi
- rpmbuild -ta $target/$base || exit 1
- find ~/rpmbuild/RPMS -name "*mdadm-$version-*" \
- -exec cp {} $target/RPM \;
- cp ANNOUNCE-$version $target/ANNOUNCE
- cp ChangeLog $target/ChangeLog
- if [ " $arg" != " test" ]
- then
- echo -n "Confirm signing this release? "
- read a
- if [ " $a" != " y" ]; then echo OK - bye. ; exit 1; fi
- if zcat $target/$base | gpg -ba > $target/$base.sign && gpg -ba $target/ANNOUNCE
- then
- kup put $target/$base $target/$base.sign \
- /pub/linux/utils/raid/mdadm/mdadm-$version.tar.gz
- kup put $target/ANNOUNCE $target/ANNOUNCE.asc /pub/linux/utils/raid/mdadm/ANNOUNCE
- else
- echo signing failed
- exit 1
- fi
- fi
-else
- if [ ! -f $target/$base ]
- then
- echo $target/$base does not exist.
- exit 1
- fi
- ( cd .. ; ln -s mdadm.v2 mdadm-$version ; tar chf - --exclude=.git --exclude="TAGS" --exclude='*,v' --exclude='*~' --exclude='*.o' --exclude mdadm --exclude=mdadm'.[^ch0-9]' --exclude=RCS mdadm-$version ; rm mdadm-$version ) | gzip --best > /var/tmp/mdadm-new.tgz
- mkdir /var/tmp/mdadm-old ; zcat $target/$base | ( cd /var/tmp/mdadm-old ; tar xf - )
- mkdir /var/tmp/mdadm-new ; zcat /var/tmp/mdadm-new.tgz | ( cd /var/tmp/mdadm-new ; tar xf - )
- diff -ru /var/tmp/mdadm-old /var/tmp/mdadm-new
- rm -rf /var/tmp/mdadm-old /var/tmp/mdadm-new /var/tmp/mdadm-new.tgz
-fi
--
2.35.3
^ permalink raw reply related [flat|nested] 12+ messages in thread
* [PATCH 4/6] mdadm: remove mdadm.spec
2024-02-23 14:51 [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
` (2 preceding siblings ...)
2024-02-23 14:51 ` [PATCH 3/6] mdadm: remove makedist Mariusz Tkaczyk
@ 2024-02-23 14:51 ` Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 5/6] mdadm: remove mkinitramfs stuff Mariusz Tkaczyk
` (2 subsequent siblings)
6 siblings, 0 replies; 12+ messages in thread
From: Mariusz Tkaczyk @ 2024-02-23 14:51 UTC (permalink / raw)
To: jes; +Cc: linux-raid, Mariusz Tkaczyk
This file is outdated, various distributions has their own specs.
Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
---
mdadm.spec | 47 -----------------------------------------------
1 file changed, 47 deletions(-)
delete mode 100644 mdadm.spec
diff --git a/mdadm.spec b/mdadm.spec
deleted file mode 100644
index 12e7859a16a4..000000000000
--- a/mdadm.spec
+++ /dev/null
@@ -1,47 +0,0 @@
-Summary: mdadm is used for controlling Linux md devices (aka RAID arrays)
-Name: mdadm
-Version: 4.3
-Release: 1
-Source: https://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-%{version}.tar.gz
-URL: https://neil.brown.name/blog/mdadm
-License: GPL
-Group: Utilities/System
-BuildRoot: %{_tmppath}/%{name}-root
-Obsoletes: mdctl
-
-%description
-mdadm is a program that can be used to create, manage, and monitor
-Linux MD (Software RAID) devices.
-
-%prep
-%setup -q
-# we want to install in /sbin, not /usr/sbin...
-%define _exec_prefix %{nil}
-
-%build
-# This is a debatable issue. The author of this RPM spec file feels that
-# people who install RPMs (especially given that the default RPM options
-# will strip the binary) are not going to be running gdb against the
-# program.
-make CXFLAGS="$RPM_OPT_FLAGS" SYSCONFDIR="%{_sysconfdir}"
-
-%install
-make DESTDIR=$RPM_BUILD_ROOT MANDIR=%{_mandir} BINDIR=%{_sbindir} install
-install -D -m644 mdadm.conf-example $RPM_BUILD_ROOT/%{_sysconfdir}/mdadm.conf
-
-%clean
-rm -rf $RPM_BUILD_ROOT
-
-%files
-%defattr(-,root,root)
-%doc TODO ChangeLog mdadm.conf-example COPYING
-%{_sbindir}/mdadm
-%{_sbindir}/mdmon
-/usr/lib/udev/rules.d/01-md-raid-creating.rules
-/usr/lib/udev/rules.d/63-md-raid-arrays.rules
-/usr/lib/udev/rules.d/64-md-raid-assembly.rules
-/usr/lib/udev/rules.d/69-md-clustered-confirm-device.rules
-%config(noreplace,missingok)/%{_sysconfdir}/mdadm.conf
-%{_mandir}/man*/md*
-
-%changelog
--
2.35.3
^ permalink raw reply related [flat|nested] 12+ messages in thread
* [PATCH 5/6] mdadm: remove mkinitramfs stuff
2024-02-23 14:51 [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
` (3 preceding siblings ...)
2024-02-23 14:51 ` [PATCH 4/6] mdadm: remove mdadm.spec Mariusz Tkaczyk
@ 2024-02-23 14:51 ` Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 6/6] mdadm: move documentation to folder Mariusz Tkaczyk
2024-02-29 14:11 ` [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
6 siblings, 0 replies; 12+ messages in thread
From: Mariusz Tkaczyk @ 2024-02-23 14:51 UTC (permalink / raw)
To: jes; +Cc: linux-raid, Mariusz Tkaczyk
This script uses mdadm.static which is known to not be abandoned
(probably not working) from years. Mdadm is integrated with dracut
and mkinitramfs these days.
Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
---
README.initramfs | 122 -----------------------------------------------
mkinitramfs | 55 ---------------------
2 files changed, 177 deletions(-)
delete mode 100644 README.initramfs
delete mode 100644 mkinitramfs
diff --git a/README.initramfs b/README.initramfs
deleted file mode 100644
index c5fa6680d187..000000000000
--- a/README.initramfs
+++ /dev/null
@@ -1,122 +0,0 @@
-Assembling md arrays at boot time.
----------------------------------
-December 2005
-
-These notes apply to 2.6 kernels only and, in some cases,
-to 2.6.15 or later.
-
-Md arrays can be assembled at boot time using the 'autodetect' functionality
-which is triggered by storing components of an array in partitions of type
-'fd' - Linux Raid Autodetect.
-They can also be assembled by specifying the component devices in a
-kernel parameter such as
- md=0,/dev/sda,/dev/sdb
-In this case, /dev/md0 will be assembled (because of the 0) from the listed
-devices.
-
-These mechanisms, while useful, do not provide complete functionality
-and are unlikely to be extended. The preferred way to assemble md
-arrays at boot time is using 'mdadm'. To assemble an array which
-contains the root filesystem, mdadm needs to be run before that
-filesystem is mounted, and so needs to be run from an initial-ram-fs.
-It is how this can work that is the primary focus of this document.
-
-It should be noted up front that only the array containing the root
-filesystem should be assembled from the initramfs. Any other arrays
-should be assembled under the control of files on the main filesystem
-as this enhanced flexibility and maintainability.
-
-A minimal initramfs for assembling md arrays can be created using 3
-files and one directory. These are:
-
-/bin Directory
-/bin/mdadm statically linked mdadm binary
-/bin/busybox statically linked busybox binary
-/bin/sh hard link to /bin/busybox
-/init a shell script which call mdadm appropriately.
-
-An example init script is:
-
-==============================================
-#!/bin/sh
-
-echo 'Auto-assembling boot md array'
-mkdir /proc
-mount -t proc proc /proc
-if [ -n "$rootuuid" ]
-then arg=--uuid=$rootuuid
-elif [ -n "$mdminor" ]
-then arg=--super-minor=$mdminor
-else arg=--super-minor=0
-fi
-echo "Using $arg"
-mdadm -Acpartitions $arg --auto=part /dev/mda
-cd /
-mount /dev/mda1 /root || mount /dev/mda /root
-umount /proc
-cd /root
-exec chroot . /sbin/init < /dev/console > /dev/console 2>&1
-=============================================
-
-This could certainly be extended, or merged into a larger init script.
-Though tested and in production use, it is not presented here as
-"The Right Way" to do it, but as a useful example.
-Some key points are:
-
- /proc needs to be mounted so that /proc/partitions can be accessed
- by mdadm, and so that /proc/filesystems can be accessed by mount.
-
- The uuid of the array can be passed in as a kernel parameter
- (rootuuid). As the kernel doesn't use this value, it is made available
- in the environment for /init
-
- If no uuid is given, we default to md0, (--super-minor=0) which is a
- commonly used to store the root filesystem. This may not work in
- all situations.
-
- We assemble the array as a partitionable array (/dev/mda) even if we
- end up using the whole array. There is no cost in using the partitionable
- interface, and in this context it is simpler.
-
- We try mounting both /dev/mda1 and /dev/mda as they are the most like
- part of the array to contain the root filesystem.
-
- The --auto flag is given to mdadm so that it will create /dev/md*
- files automatically. This is needed as /dev will not contain
- and md files, and udev will not create them (as udev only created device
- files after the device exists, and mdadm need the device file to create
- the device). Note that the created md files may not exist in /dev
- of the mounted root filesystem. This needs to be deal with separately
- from mdadm - possibly using udev.
-
- We do not need to create device files for the components which will
- be assembled into /dev/mda. mdadm finds the major/minor numbers from
- /proc/partitions and creates a temporary /dev file if one doesn't already
- exist.
-
-The script "mkinitramfs" which is included with the mdadm distribution
-can be used to create a minimal initramfs. It creates a file called
-'init.cpio.gz' which can be specified as an 'initrd' to lilo or grub
-(or whatever boot loader is being used).
-
-
-
-
-Resume from an md array
------------------------
-
-If you want to make use of the suspend-to-disk/resume functionality in Linux,
-and want to have swap on an md array, you will need to assemble the array
-before resume is possible.
-However, because the array is active in the resumed image, you do not want
-anything written to any drives during the resume process, such as superblock
-updates or array resync.
-
-This can be achieved in 2.6.15-rc1 and later kernels using the
-'start_readonly' module parameter.
-Simply include the command
- echo 1 > /sys/module/md_mod/parameters/start_ro
-before assembling the array with 'mdadm'.
-You can then echo
- 9:0
-or whatever is appropriate to /sys/power/resume to trigger the resume.
diff --git a/mkinitramfs b/mkinitramfs
deleted file mode 100644
index c6275ddb45d0..000000000000
--- a/mkinitramfs
+++ /dev/null
@@ -1,55 +0,0 @@
-#!/bin/sh
-
-# make sure we are being run in the right directory...
-if [ -f mkinitramfs ]
-then :
-else
- echo >&2 mkinitramfs must be run from the mdadm source directory.
- exit 1
-fi
-if [ -f /bin/busybox ]
-then : good, it exists
- case `file /bin/busybox` in
- *statically* ) : good ;;
- * ) echo >&2 mkinitramfs: /bin/busybox is not statically linked: cannot proceed.
- exit 1
- esac
-else
- echo >&2 "mkinitramfs: /bin/busybox doesn't exist - please install it statically linked."
- exit 1
-fi
-
-rm -rf initramfs
-mkdir initramfs
-mkdir initramfs/bin
-make mdadm.static
-cp mdadm.static initramfs/bin/mdadm
-cp /bin/busybox initramfs/bin/busybox
-ln initramfs/bin/busybox initramfs/bin/sh
-cat <<- END > initramfs/init
- #!/bin/sh
-
- echo 'Auto-assembling boot md array'
- mkdir /proc
- mount -t proc proc /proc
- if [ -n "$rootuuid" ]
- then arg=--uuid=$rootuuid
- elif [ -n "$mdminor" ]
- then arg=--super-minor=$mdminor
- else arg=--super-minor=0
- fi
- echo "Using $arg"
- mdadm -Acpartitions $arg --auto=part /dev/mda
- cd /
- mount /dev/mda1 /root || mount /dev/mda /root
- umount /proc
- cd /root
- exec chroot . /sbin/init < /dev/console > /dev/console 2>&1
-END
-chmod +x initramfs/init
-
-(cd initramfs
- find init bin | cpio -o -H newc | gzip --best
-) > init.cpio.gz
-rm -rf initramfs
-ls -l init.cpio.gz
--
2.35.3
^ permalink raw reply related [flat|nested] 12+ messages in thread
* [PATCH 6/6] mdadm: move documentation to folder
2024-02-23 14:51 [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
` (4 preceding siblings ...)
2024-02-23 14:51 ` [PATCH 5/6] mdadm: remove mkinitramfs stuff Mariusz Tkaczyk
@ 2024-02-23 14:51 ` Mariusz Tkaczyk
2024-02-29 14:11 ` [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
6 siblings, 0 replies; 12+ messages in thread
From: Mariusz Tkaczyk @ 2024-02-23 14:51 UTC (permalink / raw)
To: jes; +Cc: linux-raid, Mariusz Tkaczyk
Move documentation text files to directory.
Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
---
.../external-reshape-design.txt | 0
mdadm.conf-example => documentation/mdadm.conf-example | 0
mdmon-design.txt => documentation/mdmon-design.txt | 0
3 files changed, 0 insertions(+), 0 deletions(-)
rename external-reshape-design.txt => documentation/external-reshape-design.txt (100%)
rename mdadm.conf-example => documentation/mdadm.conf-example (100%)
rename mdmon-design.txt => documentation/mdmon-design.txt (100%)
diff --git a/external-reshape-design.txt b/documentation/external-reshape-design.txt
similarity index 100%
rename from external-reshape-design.txt
rename to documentation/external-reshape-design.txt
diff --git a/mdadm.conf-example b/documentation/mdadm.conf-example
similarity index 100%
rename from mdadm.conf-example
rename to documentation/mdadm.conf-example
diff --git a/mdmon-design.txt b/documentation/mdmon-design.txt
similarity index 100%
rename from mdmon-design.txt
rename to documentation/mdmon-design.txt
--
2.35.3
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 1/6] mdadm: remove ANNOUNCEs
2024-02-23 14:51 ` [PATCH 1/6] mdadm: remove ANNOUNCEs Mariusz Tkaczyk
@ 2024-02-28 14:40 ` Nix
2024-02-28 15:40 ` Mariusz Tkaczyk
0 siblings, 1 reply; 12+ messages in thread
From: Nix @ 2024-02-28 14:40 UTC (permalink / raw)
To: Mariusz Tkaczyk; +Cc: jes, linux-raid
On 23 Feb 2024, Mariusz Tkaczyk uttered the following:
> Release stuff is not necessary in repository. Remove it.
... it's actually pretty useful to have the ANNOUNCEs there for people
building from the repo. Given that the changelog is not updated, having
a summary of changes *somewhere* without having to grovel around in
mailing list archives seems like a thing that shouldn't just be thrown
out as "not necessary".
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 1/6] mdadm: remove ANNOUNCEs
2024-02-28 14:40 ` Nix
@ 2024-02-28 15:40 ` Mariusz Tkaczyk
2024-03-07 13:03 ` Nix
0 siblings, 1 reply; 12+ messages in thread
From: Mariusz Tkaczyk @ 2024-02-28 15:40 UTC (permalink / raw)
To: Nix; +Cc: jes, linux-raid
On Wed, 28 Feb 2024 14:40:22 +0000
Nix <nix@esperi.org.uk> wrote:
> On 23 Feb 2024, Mariusz Tkaczyk uttered the following:
>
> > Release stuff is not necessary in repository. Remove it.
>
> ... it's actually pretty useful to have the ANNOUNCEs there for people
> building from the repo. Given that the changelog is not updated, having
> a summary of changes *somewhere* without having to grovel around in
> mailing list archives seems like a thing that shouldn't just be thrown
> out as "not necessary".
>
Agree, we have to maintain it but in simpler form. I will create CHANGELOG
instead. I will copy the content of those files to changelog, with some
modifications.
Thanks for comment.
Mariusz
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 0/6] Repository cleanup
2024-02-23 14:51 [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
` (5 preceding siblings ...)
2024-02-23 14:51 ` [PATCH 6/6] mdadm: move documentation to folder Mariusz Tkaczyk
@ 2024-02-29 14:11 ` Mariusz Tkaczyk
6 siblings, 0 replies; 12+ messages in thread
From: Mariusz Tkaczyk @ 2024-02-29 14:11 UTC (permalink / raw)
To: jes; +Cc: linux-raid
On Fri, 23 Feb 2024 15:51:40 +0100
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com> wrote:
> Remove legacy files and ANNOUNCEs. They can still be reverted on demand.
> Create special documentation folder and move text files out from main
> directory.
>
> Mariusz Tkaczyk (6):
> mdadm: remove ANNOUNCEs
> mdadm: remove TODO
> mdadm: remove makedist
> mdadm: remove mdadm.spec
> mdadm: remove mkinitramfs stuff
> mdadm: move documentation to folder
>
I applied them expect first one.
ANNOUNCEs stay for now.
Thanks,
Mariusz
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 1/6] mdadm: remove ANNOUNCEs
2024-02-28 15:40 ` Mariusz Tkaczyk
@ 2024-03-07 13:03 ` Nix
2024-03-08 7:35 ` Mariusz Tkaczyk
0 siblings, 1 reply; 12+ messages in thread
From: Nix @ 2024-03-07 13:03 UTC (permalink / raw)
To: Mariusz Tkaczyk; +Cc: jes, linux-raid
On 28 Feb 2024, Mariusz Tkaczyk spake thusly:
> On Wed, 28 Feb 2024 14:40:22 +0000
> Nix <nix@esperi.org.uk> wrote:
>
>> On 23 Feb 2024, Mariusz Tkaczyk uttered the following:
>>
>> > Release stuff is not necessary in repository. Remove it.
>>
>> ... it's actually pretty useful to have the ANNOUNCEs there for people
>> building from the repo. Given that the changelog is not updated, having
>> a summary of changes *somewhere* without having to grovel around in
>> mailing list archives seems like a thing that shouldn't just be thrown
>> out as "not necessary".
>
> Agree, we have to maintain it but in simpler form. I will create CHANGELOG
> instead. I will copy the content of those files to changelog, with some
> modifications.
They are a bit of a mess at the top level though. Maybe move them into
misc/ or a new doc/ or something?
--
NULL && (void)
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 1/6] mdadm: remove ANNOUNCEs
2024-03-07 13:03 ` Nix
@ 2024-03-08 7:35 ` Mariusz Tkaczyk
0 siblings, 0 replies; 12+ messages in thread
From: Mariusz Tkaczyk @ 2024-03-08 7:35 UTC (permalink / raw)
To: Nix; +Cc: jes, linux-raid
On Thu, 07 Mar 2024 13:03:28 +0000
Nix <nix@esperi.org.uk> wrote:
> On 28 Feb 2024, Mariusz Tkaczyk spake thusly:
>
> > On Wed, 28 Feb 2024 14:40:22 +0000
> > Nix <nix@esperi.org.uk> wrote:
> >
> >> On 23 Feb 2024, Mariusz Tkaczyk uttered the following:
> >>
> >> > Release stuff is not necessary in repository. Remove it.
> >>
> >> ... it's actually pretty useful to have the ANNOUNCEs there for people
> >> building from the repo. Given that the changelog is not updated, having
> >> a summary of changes *somewhere* without having to grovel around in
> >> mailing list archives seems like a thing that shouldn't just be thrown
> >> out as "not necessary".
> >
> > Agree, we have to maintain it but in simpler form. I will create CHANGELOG
> > instead. I will copy the content of those files to changelog, with some
> > modifications.
>
> They are a bit of a mess at the top level though. Maybe move them into
> misc/ or a new doc/ or something?
>
In other projects files like that are handled in main directory. I should
consider moving code into "/src" directory, udev stuff into "/udev", man files
into "/man" instead.
If you would like to try create some patches to help me with cleanup I will be
appreciated!
For now, I'm working on following files:
- README.md - general instructions; what is it, how to contribute, etc.
- MAINTAINERS.md - instructions for maintainers.
- CHANGELOG.md - release stuff.
I choose markdown because it is most popular and it gives ".md" it the name:)
I should send them to review next week.
Thanks,
Mariusz
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2024-03-08 7:35 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-02-23 14:51 [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 1/6] mdadm: remove ANNOUNCEs Mariusz Tkaczyk
2024-02-28 14:40 ` Nix
2024-02-28 15:40 ` Mariusz Tkaczyk
2024-03-07 13:03 ` Nix
2024-03-08 7:35 ` Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 2/6] mdadm: remove TODO Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 3/6] mdadm: remove makedist Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 4/6] mdadm: remove mdadm.spec Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 5/6] mdadm: remove mkinitramfs stuff Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 6/6] mdadm: move documentation to folder Mariusz Tkaczyk
2024-02-29 14:11 ` [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).