[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#678696: Event based block device handling (fixes USB and nested devices problem)



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 you or someones else finds time to try and possibly further
investigate I'd very much welcome and appreciate that.

regards,
-mika-

Attachment: signature.asc
Description: Digital signature


Reply to: