[Bug 1262151] [NEW] mdadm generates incorrect config if array name contains whitespace

[Gordon Ball]

Public bug reported:

System: Acer S5-391
Contains two flash drives configured as (Intel) fakeraid. mdadm correctly detects that this array exists, and shows (apparently) correct metadata for both the overall array and the individual disks.

However, the name of the raid array contains spaces, and the
/etc/mdadm/mdadm.conf generated (presumably by postinst scripts) does
not quote or escape the spaces, resulting in an invalid config file.

I assume it uses the output of something like `mdadm --examine --scan`, which yields
ARRAY metadata=imsm UUID=<uuid>
ARRAY /dev/md/Aspire S5-391 container=<uuid> member=0 UUID=<uuid>

Subsequently attempting to assemble the array then gives an error that
the second ARRAY line is invalid (treating /dev/md/Aspire and S5-391 as
separate arguments).

This can be corrected manually by adding quotation marks around
"/dev/md/Aspire S5-391" in /etc/mdadm/mdadm.conf, after which the array
works correctly, but a check should probably be added for this syntax.
I'm not sure if this can be fixed just in the debian/ubuntu packaging or
needs to be sent upstream.

** Affects: mdadm (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: saucy

** Tags added: saucy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/1262151

Title:
  mdadm generates incorrect config if array name contains whitespace

Status in “mdadm” package in Ubuntu:
  New

Bug description:
  System: Acer S5-391
  Contains two flash drives configured as (Intel) fakeraid. mdadm correctly detects that this array exists, and shows (apparently) correct metadata for both the overall array and the individual disks.

  However, the name of the raid array contains spaces, and the
  /etc/mdadm/mdadm.conf generated (presumably by postinst scripts) does
  not quote or escape the spaces, resulting in an invalid config file.

  I assume it uses the output of something like `mdadm --examine --scan`, which yields
  ARRAY metadata=imsm UUID=<uuid>
  ARRAY /dev/md/Aspire S5-391 container=<uuid> member=0 UUID=<uuid>

  Subsequently attempting to assemble the array then gives an error that
  the second ARRAY line is invalid (treating /dev/md/Aspire and S5-391
  as separate arguments).

  This can be corrected manually by adding quotation marks around
  "/dev/md/Aspire S5-391" in /etc/mdadm/mdadm.conf, after which the
  array works correctly, but a check should probably be added for this
  syntax. I'm not sure if this can be fixed just in the debian/ubuntu
  packaging or needs to be sent upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1262151/+subscriptions