[Bug 550131] Re: maps file not getting copied from initramfs to real rootfs (loosing state, race, misconfig)

[Steve Langasek]

Surbhi,

I'm afraid I don't understand the fix for this bug in
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/+attachment/2139759/+files/mdadm_lp_bug_fixes.debdiff.
The changelog comments say that the map will be rebuilt - but isn't this
bug about needing to preserve the *state* from /var/run in the
initramfs?  How does rebuilding the map accomplish this?

I understand that this is a backport from mdadm 3.1.4; I just am not
sure how this change addresses the issue reported here.

A test case for this particular bug would also be helpful for the SRU
process, if someone can describe how to reproduce the original error
(presumably in a test environment).

-- 
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/550131

Title:
  maps file not getting copied from initramfs to real rootfs (loosing
  state, race, misconfig)

Status in “mdadm” package in Ubuntu:
  In Progress
Status in “mdadm” source package in Lucid:
  In Progress
Status in “mdadm” source package in Maverick:
  In Progress

Bug description:
  Binary package hint: mdadm

  "mdadm --incremental" will save state in a map file under
  /var/run/mdadm/map.

  But in initramfs and early boot this directory does not exist.

  The state is then saved in /var/run/mdadm.map.new (man page
  incorrectly says /var/run/mdadm.map) and carried into the main system
  later on. This means hotplug devices showing up later can not be
  matched by --incremental correctly. (with a strange device busy
  failure)

  This can be fixed as explained by Jools in the comments, and as he did
  in his package.