Bug#762395: systemd is not abel to boot systems with btrfs and without initramfs

Michael Biebl biebl at debian.org
Sat Oct 11 20:14:22 BST 2014


Am 11.10.2014 um 20:58 schrieb Dimitri John Ledkov:
> So what needs doing? Because to mount btrfs /dev/sdb,
> systemd-udev-trigger is needed to generate "block" "add" event and
> thus execute btrfs scan, in the initramfs-less case.
> And ate the moment systemd-udev-trigger is only called after local-fs.

How did you come to that conclusion that this is happening? At least the
timestamps in the systemdadm dump do not confirm what you are suggesting:

-> Unit systemd-udev-trigger.service:
	Description: udev Coldplug all Devices
	Instance: n/a
	Unit Load State: loaded
	Unit Active State: active
	Inactive Exit Timestamp: Sun 2014-09-21 21:51:55 CEST
	Active Enter Timestamp: Sun 2014-09-21 21:51:55 CEST

	
-> Unit local-fs.target:
	Description: Local File Systems
	Instance: n/a
	Unit Load State: loaded
	Unit Active State: active
	Inactive Exit Timestamp: Sun 2014-09-21 21:51:57 CEST
	Active Enter Timestamp: Sun 2014-09-21 21:51:57 CEST


To me it rather looks like "btrfs scan" is not triggered at all.




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141011/1b7432be/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list