On 22 September 2014 12:57, Michael Biebl <[email protected]> wrote: > Am 22.09.2014 um 13:27 schrieb M G Berberich: >> Hello, >> >> Am Montag, den 22. September schrieb Michael Biebl: >>> Am 21.09.2014 um 22:04 schrieb M G Berberich: >>>> Package: systemd >>>> Version: 208-8 >>>> Severity: normal >>>> >>>> Dear Maintainer, >>>> >>>> systemd is not able to boot a system that has btrfs-volumes in >>>> /etc/fstab and does not use a initramfs. That is because ‘btrfs device >>>> scan’ has to be executed bevor mounting btrfs-volumes and systemd does >>>> not do this. >>>> >>> >>> I see >>> >>> btrfs-tools: /lib/udev/rules.d/70-btrfs.rules >>> btrfs-tools: /lib/udev/rules.d/80-btrfs-lvm.rules >>> >>> 70-btrfs.rules:RUN+="/sbin/btrfs device scan $env{DEVNAME}" >>> 80-btrfs-lvm.rules:RUN+="/sbin/btrfs device scan $env{DEVNAME}" >>> >>> Can you investigate why that is not sufficient. >> >> A first guess: local filesystems are mounted bevor udev is working. > > Well, no. udev is started well before the file systems are mounted. > Actually, udev is responsible for local file systems to be mounted since > the mounting is event based and systemd relies on udev to trigger those > events. > > I'm bringing Dimitri into the loop here, as this sounds like a bug in > btrfs-tools to me. >
It is my understanding that udev rules should be sufficient. Could you please provide your /etc/fstab to reproduce this failure to boot? Are you attempting to do initramfs-less boot with rootfs on btrfs? -- Regards, Dimitri. _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
