Surbhi, you actually have an ubuntu system on raid installed and the mapfile is 
carried over?
Then please state the exact version and details and say it works for you.
If not please leave the bug filed as it was, documenting a bug in the ubuntu 
mdadm package.

** Changed in: mdadm (Ubuntu)
       Status: Incomplete => Confirmed

** Description changed:

  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 by:
- 
- * creating /var/run/mdadm in the initramfs *before* the udevd is started
- in init-premount/udev (either during creation of the initramfs image, or
- dynamicly (boot time consuming) in mdadm's initramfs-tools init-
- top/mdadm script).
- 
- * copying initramfs' /var/run the real /var/run as part of the boot
- process so /var/run/mdadm/map carries on the valid --incremental state.
+ This can be fixed as explained by Jools in the comments, and as he did
+ in his package.

-- 
initramfs missing /var/run/mdadm/ dir (loosing state, race, misconfig)
https://bugs.launchpad.net/bugs/550131
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to