I have the same problem too.
Using git bisect, I get the same commit:
319767b85c2b16d80c235195329470c46d4547b3 is the first bad commit
commit 319767b85c2b16d80c235195329470c46d4547b3
Author: NeilBrown
Date: Mon Feb 8 14:33:31 2010 +1100
mapfile: use ALT_RUN as alternate place to store map
On Mon, 26 Jul 2010 21:37:47 +0200
Jan Echternach wrote:
> On Mon, Jul 26, 2010 at 06:44:25PM +1000, Neil Brown wrote:
> > If you are up to compiling and installing your own mdadm, could you try
> > reverting
> >
> > http://neil.brown.name/git?p=mdadm;a=commitdiff;h=319767b85c2b16d80c23519532947
On Mon, Jul 26, 2010 at 06:44:25PM +1000, Neil Brown wrote:
> If you are up to compiling and installing your own mdadm, could you try
> reverting
>
> http://neil.brown.name/git?p=mdadm;a=commitdiff;h=319767b85c2b16d80c235195329470c46d4547b3
>
> from 3.1.2 and see if the makes the difference?
It
On Sun, 25 Jul 2010 22:08:12 +0200
Jan Echternach wrote:
> Package: mdadm
> Version: 3.1.2-2
> Severity: normal
>
> I get an udevadm settle timeout during boot after upgrading mdadm from
> version 3.1.1-1 to 3.1.2-2:
If you are up to compiling and installing your own mdadm, could you try
revert
Package: mdadm
Version: 3.1.2-2
Severity: normal
I get an udevadm settle timeout during boot after upgrading mdadm from
version 3.1.1-1 to 3.1.2-2:
> Success: assembled all arrays.
> done.
> [ 12.509710] device-mapper: uevent: version 1.0.3
> [ 12.523034] device-mapper: ioctl: 4.15.0-ioctl (2
5 matches
Mail list logo