On Tue, 20 May 2014 18:26:59 -0600 Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > That ought to be true, but at least on a systemd 212-4 system, it > assumes the system root needs to be fsck'd before mounting it. Since > the fs isn't mounted, fstab isn't available. And the fstab.empty file > I found in the initramfs is in fact empty. So even with fs_passno set > to 0, systemd is trying to run fsck.btrfs, which it fails to find, > warns about, then moves on. > > I filed that bug here: > https://bugzilla.redhat.com/show_bug.cgi?id=1098799 [@ Chris M, I sent this to you only first. So this one's to the list only, but it'll have a different message-id, so you'll probably get it as two different messages, one to the list, one direct to you.] Hmm... it isn't doing so here. dracut-037, systemd-212-r4 (the -r4 indicating four gentoo package level revision bumps since the initial in-tree release of the upstream 037 version). But I have an install-customized dracut config (tho I no longer use host-only as explained in my last post, to the degraded boot and systemd thread), all kernel modules built-in, etc. If you're running a generic everything-including-the-kitchen-sink dracut, that might explain it, since I guess on most filesystems (not reiserfs/xfs/btrfs, however) it would need to be run. -- Duncan - No HTML messages please, as they are filtered as spam. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
