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)
@ceg, @Jools Wills, I will love to help to solve this bug. For that I
need to know what the problem is. The summary says that the maps file
cant be created and thus it leads to loosing state, race, misconfig? If
there is an example for it, then I can get a better understanding of
what really is
@ceg, @Jools Wills, I see what you are saying! I will try to fix this up
soon and post updates here :) Thanks a tonnes!
--
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
@ceg, when /var/run/mdadm is not present, mdadm creates a map in
/var/run/. Please refer to man mdadm for more information (or
mapfile.c::map_read()/map_write() in mdadm code). Can you please explain
why this is causing a problem? Ideally it should not cause a problem.
** Changed in: mdadm
Why has this been set to incomplete? The initial explanation is quite
clear. /var/run doesn't exist at the initramfs stage and it will fail.
If you updated to a new mdadm, this will use /dev/.mdadm folder for the
map file - this exists throughout the initramfs and is carried over once
root is
I explained slightly wrong, since my memory was vague. The old mdadm
2.7.1 in ubuntu probably makes the map file ok, but it won't get carried
across onto the rootfs. mdadm 3.1.2 wanted to place the map file in a
different location and failed. my solution at the time was to change the
location, and
@Jools Will, 2.7.1, creates the map file in /var/run/ instead of
/var/run/mdadm as /var/run/mdadm is not found in the initramfs. However
/var/run is found in initramfs and so the map file should be created
fine. This is why I have marked the bug as Invalid. Current Ubuntu is
still at 2.7.1 Can you
Please demonstrate to me where the map file created in initramfs is then
copied to the root filesystem so it is available for mdadm at that
stage. It isn't! I'm not going to play the game setting the bug to
confirmed/invalid back and forth.
to fix this you need to either copy the map file to the
** 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
** Summary changed:
- initramfs missing /var/run/mdadm dir (loosing state)
+ initramfs missing /var/run/mdadm/ dir (loosing state, race, misconfig)
--
initramfs missing /var/run/mdadm/ dir (loosing state, race, misconfig)
https://bugs.launchpad.net/bugs/550131
You received this bug notification
** Summary changed:
- boot: initramfs missing dir /var/run/mdadm
+ initramfs missing /var/run/mdadm dir (loosing state)
--
initramfs missing /var/run/mdadm dir (loosing state)
https://bugs.launchpad.net/bugs/550131
You received this bug notification because you are a member of Ubuntu
Bugs,
this issue can be identified from the initramfs by checking the current
md devices. Only one of the disks in the array is active and incremental
adding fails with error, /dev/md/d0 device already exists.
one time workaround is to stop the existing array and manually assemble
the array without
confirmed from Bug #541058 and #136252
** 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
13 matches
Mail list logo
