[FFe] Merge new upstream version 3.3 from Debian testing - lots of bugfixes + important new features

[Mantas Kriaučiūnas]

mdadm in Ubuntu 14.04 (Trusty) is 2 years old - ver. 3.2.5, while Debian contains up to date version - 3.3

Please merge new upstream version 3.3 from Debian testing (released 3rd September 2013):

This is a major new release, 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

See http://article.gmane.org/gmane.linux.raid/44013

Here is changelog from Debian:

mdadm (3.3-2) unstable; urgency=low
  * use 63-md-raid-arrays.rules instead of old 64-md-raid.rules
    (Closes: #726237)
  * do not use builtin blkid in udev rules, as our udev (at least
    on wheezy) does not have it (use-external-blkid.diff)
 -- Michael Tokarev <email address hidden> Mon, 14 Oct 2013 15:49:54 +0400

mdadm (3.3-1) unstable; urgency=low
  [ Michael Tokarev ]
  * new upstream 3.3 release (Closes: #718896)
    See ANNOUNCE-3.3 for details.
    Patches:
    - refreshed debian-conffile-location.diff
      (added .conf.d)
    - removed debian-disable-udev-incr-assembly.diff
      (do not ship udev-md-raid-assembly.rules for now)
    - refreshed debian-no-Werror.diff
    - refreshed sha1-includes.diff
    - removed patches (included upstream)A:
       spelling-and-manpages.patch
       fix-enough-function-for-RAID10.patch
       fix-segfaults-in-detail.patch
       super0-do-not-override-uuid-with-homehost.patch
       mdmon-allow-takeover-when-original-was-started-with-.patch
       mdmon-fix-arg-parsing.patch
       mdmon-fix-arg-processing-for-a.path
    Install udev-md-raid-arrays.rules instead of udev-md-raid.rules,
    don't install new udev-md-raid-assembly.rules for now.
  * remove Martin F. Krafft from uploaders per his request.
    Thank you for your contributions!
  * added remove-bashism-from-makefile.patch patch to work around
    newly introduced bashism
  * remove debian/source/options, there's no need to set compression
    options for debian.tar.gz.
  * remove outdated debian/docs/md_superblock_formats.txt and
    debian/docs/md.txt (Closes: #714977, #714978)
  * ship ANNOUNCE-*, external-reshape-design.txt, mdmon-design.txt
    files as documentation (Closes: #715324)
  [ Dmitrijs Ledkovs ]
  * Properly remove 65-mdadm.vol_id.rules, instead of trying to remove a
    never-existed 65_mdadm.vol_id.rules (note the 65- vs 65_).
 -- Michael Tokarev <email address hidden> Fri, 11 Oct 2013 10:12:47 +0400

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Alberto Salvia Novella (es20490446e)]

It's estimated to have a moderate impact on a large portion of Ubuntu users.

[Dimitri John Ledkov (xnox)]

this is outside the scope of 100 papercuts projects. Also there are regressions reported in 3.3 upstream thus would also need cherrypicks from upstream git repositories.

[Scott Kitterman (kitterman)]

s-python/trunk$ rmadison mdadm
 mdadm | 2.6.7.1-1ubuntu15 | lucid | source, amd64, armel, i386, ia64, powerpc, sparc
 mdadm | 3.2.3-2ubuntu1 | precise | source, amd64, armel, armhf, i386, powerpc
 mdadm | 3.2.5-1ubuntu0.3 | precise-updates | source, amd64, armel, armhf, i386, powerpc
 mdadm | 3.2.5-5ubuntu4 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el
 mdadm | 3.2.5-5ubuntu4.1 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el
 mdadm | 3.3-2ubuntu1 | utopic | source, amd64, arm64, armhf, i386, powerpc, ppc64el
 mdadm | 3.3-2ubuntu1 | vivid | source, amd64, arm64, armhf, i386, powerpc, ppc64el