diff options
| -rw-r--r-- | debian/NEWS | 107 |
1 files changed, 0 insertions, 107 deletions
diff --git a/debian/NEWS b/debian/NEWS deleted file mode 100644 index 691f717..0000000 --- a/debian/NEWS +++ /dev/null @@ -1,107 +0,0 @@ -mdadm (3.2.2-1) unstable; urgency=low - - Metadata format change requires recent Grub - The following only applies to users who want to let the grub-pc bootloader - load the kernel directly off a RAID device created with mdadm 3.x and - default values, or when the metadata version is explicitly set using -e. - - Specifically, this includes all arrays created during or after the - installation of Debian squeeze (mdadm-3.1.4+8efb9d1). Arrays created with - older mdadm versions, and RAIDs created with the command-line option - -e 0.9 are not affected. - - Versions of grub-pc older than 1.98+20100720-1 will not be able to boot - directly off a RAID with the 1.x metadata formats (the new default is 1.2). - To ensure a bootable system, please make sure to use grub-pc 1.98+20100720-1 - or later, which is provided by Debian squeeze. An unbootable system may be - rescued with Super Grub2 Disk (http://www.supergrubdisk.org/super-grub2-disk/) - or grml (http://grml.org/). - - -- Scott Schaefer <saschaefer@neurodiverse.org> Wed, 27 Jul 2011 20:21:50 -0400 - -mdadm (3.1.4-1+8efb9d1) unstable; urgency=low - - Default metadata format for newly created arrays has changed from - 0.90 to 1.2. Location of the superblock is now 4Kb from the start - of the device, instead of at the end of the device for 0.90. - The change from 0.9 to 1.x lifted many restrictions of the old - metadata format, and change in location (from end to 4k after - start for 1.2) reduced chances to confuse a raid array with - filesystem inside it. It is now less easy to mount a component - device as separate filesystem by incident, thus destroying the - array. - - Also, chunk size by default is 512K (was 64K) and bitmap chunk size - is 64Mb. - - -- Michael Tokarev <mjt@tls.msk.ru> Sat, 10 Sep 2011 13:35:12 +0400 - -mdadm (2.6.7-2) unstable; urgency=low - - /dev/disk symlinks: - mdadm now creates symlinks in /dev/disk/by-id, using the template - md-uuid-* for the array UUIDs and md-name-* for any names assigned to - arrays (version-1 superblocks only). Thanks to Suse for the udev rules - file. - - mdrun removed: - This version also removes mdrun once and for all. If you are still using - mdrun, please ensure that you have a valid /etc/mdadm/mdadm.conf file (run - /usr/share/mdadm/mkconf --generate to get one), and run - - mdadm --assemble --scan --auto=yes - - -- martin f. krafft <madduck@debian.org> Wed, 02 Jul 2008 10:57:32 +0200 - -mdadm (2.5.3.git200608201206-1) unstable; urgency=low - - This version makes mdadm.conf mandatory. If you do not have such a file, it - will be created for you. - - You must verify the contents of this file and ensure that it represents your - local configuration. See /usr/share/doc/mdadm/README.upgrading-2.5.3.gz for - more information. - - -- martin f. krafft <madduck@debian.org> Sun, 20 Aug 2006 21:58:43 +0100 - -mdadm (2.5-1) unstable; urgency=low - - mdrun has been (finally) obsoleted, and an appropriate warning message is - written to the console if you (or a script) attempts to run it. If you - cannot live without mdrun, you can disable the warning by setting - USE_DEPRECATED_MDRUN=1 in /etc/default/mdadm. Note that mdrun will *not* be - supported. Please also see /usr/share/doc/mdadm/README.mdrun . - - -- martin f. krafft <madduck@debian.org> Tue, 30 May 2006 23:25:13 +0200 - -mdadm (2.4.1-5) unstable; urgency=low - - This version drops the automatic generation of the /etc/mdadm/mdadm.conf - file on every boot (if it was missing). This means that you need to ensure - that you have a valid configuration file. If none is present during package - configuration, mdadm *will* try to generate one, but it will only contain - information about arrays that were running at the time of package - configuration. Arrays not listed in the configuration file will *not* be - started automatically after boot (with the exception of the root partition). - - If you want to recreate your configuration file, either figure out what it - should contain from the mdadm.conf(5) manpage, or simply assemble and run - all the arrays the way you like it, then run - /usr/share/mdadm/mkconf force-generate /etc/mdadm/mdadm.conf - - -- martin f. krafft <madduck@debian.org> Sat, 03 Jun 2006 17:45:47 +0200 - -mdadm (2.4.1-1) unstable; urgency=low - - As of version 2.3, mdadm uses /etc/mdadm.conf as its main configuration - file, and falls back to /etc/mdadm/mdadm.conf if the former is not found. - Since Debian uses /etc/mdadm/mdadm.conf as the configuration file path, this - order was reverted: Debian's mdadm reads /etc/mdadm/mdadm.conf as its main - file and falls back to /etc/mdadm.conf if the former is not found. - - An incompatible change in the reshaping of RAID 5 arrays was made in this - upstream release. If you want to reshape a RAID 5 array with a version-1 - superblock, please make sure to use mdadm 2.4.1 and at least a 2.6.17-rc2 - kernel. - - -- martin f. krafft <madduck@debian.org> Tue, 16 May 2006 13:07:49 -0500 |