Jamie Heilman wrote:
> I wouldn't be stunned if this problem mostly stemmed from the fact
> that /scripts/init-top/udev executes prior to loading kernel modules.
> It might be interesting to see what happens if we toss
> udevadm trigger --action=add
> udevadm settle || true
> into a script in /sc
Dimitri John Ledkov wrote:
> Previously, local-top script was used to wait a little and assemble
> all arrays. Now, udev rules are used to incrementally assemble
> arrays. In the mean time local-block "main-loop" scripts are used
> to poll and activate LVM volumes. In case of incomplete arrays,
Hello,
On 11 July 2016 at 10:35, Jamie Heilman wrote:
> Package: mdadm
> Version: 3.4-2
> Severity: important
>
> With 3.4-2 my lvm on partitioned md system has stopped initializing
> correctly. For starters when upgrading from 3.4-1 to 3.4-2 I get
> this:
> W: mdadm: the array /dev/md/d0 with U
Package: mdadm
Version: 3.4-2
Severity: important
With 3.4-2 my lvm on partitioned md system has stopped initializing
correctly. For starters when upgrading from 3.4-1 to 3.4-2 I get
this:
W: mdadm: the array /dev/md/d0 with UUID 4c4bcb71:267c92fc:fe08e7ef:27569e0b
W: mdadm: is currently active,
4 matches
Mail list logo
