On Sun, Aug 31, 2014 at 10:14:18AM +0200, Michael Prokop wrote:
> Hi,
>
> f'up to our recent discussion we had on IRC
>
> * Goswin von Brederlow [Sat Jun 23, 2012 at 09:25:28PM +0200]:
>
> > the attached patch adds an event based loop for block devices to the
> > init script. New blockdevices are recorded in
> > /run/initramfs/block-events by an udev rule as they appear. The init
> > script repeadately waits for that and then calls
> > /scripts/local-block/* with a list of new devices storedin NEWDEVS
> > until $ROOT and $resume (if set) exists or a timeout is reached.
>
> > This fixes the problem that USB devices take too long to be
> > discovered and crypto, raid, lvm or multipath can't be started on
> > them. It also adds support for arbitrary nestings of them, e.g. raid5
> > over raid1.
> [...]
>
> First of all thanks again for the patch and your helpful feedback on
> IRC.
>
> I've tested your patch based on top of current i-t git master
> (v0.116) with a setup like:
>
> BOOT_IMAGE=/boot/vmlinuz-3.14-2-amd64 root=/dev/mapper/vg0-root ro quiet
>
> but it sadly fails to work as intended (it boots but doesn't find
> the block devices until the timeout is kicking in). I didn't
> investigate closer yet, but AFAICS it seems to be related to the
> fact that /dev/mapper/vg0-root doesn't exist at that time yet.
If it boots after the timeout then the device must exist. So either
the test for it is wrong or the device only gets created after the
timeout.
> If you or someones else finds time to try and possibly further
> investigate I'd very much welcome and appreciate that.
>
> regards,
> -mika-
Questions:
Does your system boot without the patch? If not then you also need the
lvm patch to provide the hook script that scans for a VG when new
block devices are detected.
Do you see any messages about vg0 being activated before the timeout
or after?
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
