Earlier, I suggested a data-collection exercise involving udevd
--verbgose, but this didn't do much good because the race went away
when testing in this way.
I think this was probably due to udev writing to the console. I have
now prepared a version of udev which can be made not to write to the
c
Perhaps is it another bug on my particular system...
I have written about it in previous comments, when trying to assemble /dev/md0
I have three different results:
* all devices of the array are available: /dev/md0 is created and working
* a device is missing (and --no-degraded is _not_ specified)
How can it be assembled too early if --no-degraded is given?
Surely with that option, mdadm doesn't assemble the array if some
devices are missing, instead of part-assembling it in degraded mode?
--
initramfs script: race condition between sata and md
https://launchpad.net/bugs/75681
--
ubuntu
With the --no-degraded option that has been added, it IS harmless for
the array itself, but it can still block the boot.
If an array has been assembled too early, it should be stopped (running
"mdadm -S /dev/md0" by hand worked for me) BEFORE trying to assemble it
again, an other race may be prese
The problem here is clearly that mdadm is being run too early, and is
trying to assemble RAIDs that are not yet complete.
Either mdadm needs to be fixed so that doing this is possible, and
harmless; like it is for lvm, etc. or the script that calls mdadm needs
to check whether it is safe to call
Ian Jackson <[EMAIL PROTECTED]> writes:
> Could you please boot with break=premount, and do this:
> udevd --verbose >/tmp/udev-output 2>&1 &
> udevtrigger
> At this point I think you will find that your mds and lvms
> are not activated properly; check with
> cat /proc/partitions
OK, here are the result of some more tests with mdadm_2.5.6-7ubuntu4:
* my first boot went fine, allowing me to get your advice.
* the second boot hanged, so I waited for a while. All my devices were here,
both in /dev and in /proc/partitions
The RAID array was assemble with 3 devices (out of 4)
Reinhard Tartler writes ("Re: [Bug 75681] Re: initramfs script: race condition
between sata and md"):
> Ian Jackson <[EMAIL PROTECTED]> writes:
> > 2. Run
> > /scripts/local-top/mdadm from-udev
> >(NB `from-udev' is an argument you mus
Ian Jackson <[EMAIL PROTECTED]> writes:
> 1. Check that
> cat /proc/partitions
>lists all of the components of your array. If not, then we need to
>understand why not. What are those components ? You will probably
>find that it does not list the array itself. If it does then we
Aurelien Naldi writes ("[Bug 75681] Re: initramfs script: race condition
between sata and md"):
> The array should _not_ be started _at_all_ unless all needed devices
> have been detected (including spare ones) OR when all device
> detection is done.
Unfortunately, in Linux 2
Aurelien Naldi writes ("[Bug 75681] Re: initramfs script: race condition
between sata and md"):
> The first boot went fine. The next one hanged. And the next one went
> also fine. For all of them, I get the message "no devices listed in
> cinf file were found" but
>From the changelog of mdadm 2.5.6-7ubuntu4:
Specify --no-degraded argument to mdadm in initramfs; this
can be overridden by setting MD_DEGRADED_ARGS to some nonempty value
(eg, a single space). This ought to fix race problems where RAIDs are
assembled in degraded mode far too
The first boot went fine. The next one hanged. And the next one went also fine.
For all of them, I get the message "no devices listed in cinf file were found"
but it looks harmless.
I do not know were the second one hanged so it may be unrelated, but it was
before mounting /
--
initramfs script
this fixes the issue for me
--
initramfs script: race condition between sata and md
https://launchpad.net/bugs/75681
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I think I have fixed this in mdadm_2.5.6-7ubuntu4. Please could you
install this, which I have just uploaded, and check if it works.
** Changed in: mdadm (Ubuntu)
Assignee: (unassigned) => Ian Jackson
Status: Confirmed => Fix Committed
--
initramfs script: race condition between sat
I've been hit with the same problem with a fresh feisty install (10 feb install
cd),
booting often doesn't work and always results in incomplete raid arrays.
This is with 2x 80gb sata, and 7 raid1 devices. The current mdadm
initramfs script is unsuitable for release.
--
initramfs script: race
There is still a race condition here. I does not attempt to start the
array before detecting devices but it often starts it too early. My 4
devices RAID5 is, most of the time, either not assembled (i.e. 1 or 2
devices out of 4 is not enough) or assembled in degraded mode. An array
should be assembl
status update: udev does start one raid device on bootup, but not all.
After starting the raid devices manually using /scripts/local-top/mdadm,
the vg still don't get up, I need to do manually 'lvm vgscan ; lvm
vgchange -a y'
** Also affects: lvm2 (Ubuntu)
Importance: Undecided
Status: U
subscribing Ian and Scott, since they have done some uploads regarding
udev and lvm2 in the past which improved the situation a bit.
--
initramfs script: race condition between sata and md
https://launchpad.net/bugs/75681
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
Aurelien Naldi <[EMAIL PROTECTED]> writes:
> It looks like it was fixed by recent updates, but at the expense of
> breaking LVM (my initramfs does not contain (/scripts/local-top/lvm
> anymore).
I can confirm. Latest updates changed the behavior, now the raid is
activated but not lvm. booting with
It looks like a race condition is still here: the initramfs tryes to
assemble my RAID upon detection of /dev/sda. Obviously with 3 drives
missing out of 4, it fails... Then, /dev/md0 is not here but inactive
and not correctly created when the other drives are detected.
Is it possible to get and ud
It looks like it was fixed by recent updates, but at the expense of
breaking LVM (my initramfs does not contain (/scripts/local-top/lvm
anymore).
--
initramfs script: race condition between sata and md
https://launchpad.net/bugs/75681
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
I can confirm this bug, ajmitch is suffering as well from this.
** Changed in: mdadm (Ubuntu)
Importance: Undecided => High
Status: Unconfirmed => Confirmed
--
initramfs script: race condition between sata and md
https://launchpad.net/bugs/75681
--
ubuntu-bugs mailing list
ubuntu-bug
Here is a patch that stalls the mdadm initramfs script until the desired
devices are available. I set the timeout to 30 seconds.
** Summary changed:
- race condition between sata and md
+ initramfs script: race condition between sata and md
** Attachment added: "wait for devices"
http://libr
24 matches
Mail list logo
