16.10.2020 18:51, Lennart Poettering пишет: >> >> Ths btrfs udev rule file appears to be missing in the initrd. The >> block devices with the btrfs file systems on them will thus be marked >> ready in systemd instantly instead of being delayed until all other >> devices of the same btrfs fs have shown up in udev too. >> >> Fix your initrd. > > So my educated guess is that this is a dracut bug: it excludes the > btrfs udev rule file from the initrd unless the root fs is btrfs. > > But this doesn't work, because the absence of that file means that all > btrfs file systems will be marked as ready instantly as they appear, > which then blows up later if during later boot btrfs file systems that > are backed by multiple devices shall be mounted. > > It's basically a race: if yor block devices appear in the initrd > already, then you lost,
It is unmanageable. It means we now have to include half of kernel and user space because god knows what could be required by udev rules. How should dracut even supposed to know what to include? initrd is needed to mount root. Period. If you broke it by carrying over incomplete udev database state from initrd, it is up to *you* to fix it, not forcing copy of root system into initrd. > because all such devices will be instantly be > marked "ready to be mounted" because the udev rule file is missing > there. However, if the block devices take longer to appear, and are > thus first seen after the initrd→host transition, then all will be > good, as the udev rules file for it exists there, and the devices are > not marked ready until all necessary devices have shown up in udev. > > Fix is: dracut should just include the file unconditionally. It's > tiny. > > If it really really insist to not include it on systems where btrfs isn't > used, then it should scan the host for any btrfs use at all. it's not > sufficient to determine whether the rootfs is btrfs or not. > > Anyway, please report to dracut. > > Lennart > > -- > Lennart Poettering, Berlin > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel > _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
