On Sat, Jan 27, 2018 at 13:26:13 +0300, Andrei Borzenkov wrote: >> I just tested to boot with a single drive (raid1 degraded), even with >> degraded option in fstab and grub, unable to boot ! The boot process stop on >> initramfs. >> >> Is there a solution to boot with systemd and degraded array ? > > No. It is finger pointing. Both btrfs and systemd developers say > everything is fine from their point of view.
Treating btrfs volume as ready by systemd would open a window of opportunity when volume would be mounted degraded _despite_ all the components are (meaning: "would soon") be ready - just like Chris Murphy wrote; provided there is -o degraded somewhere. This is not a systemd issue, but apparently btrfs design choice to allow using any single component device name also as volume name itself. IF a volume has degraded flag, then it is btrfs job to mark is as ready: >>>>>> ... and it still does not work even if I change it to root=/dev/sda1 >>>>>> explicitly because sda1 will *not* be announced as "present" to >>>>>> systemd> until all devices have been seen once ... ...so this scenario would obviously and magically start working. As for the regular by-UUID mounts: these links are created by udev WHEN underlying devices appear. Does btrfs volume appear? No. If btrfs pretends to be device manager it should expose more states, especially "ready to be mounted, but not fully populated" (i.e. "degraded mount possible"). Then systemd could _fallback_ after timing out to degraded mount automatically according to some systemd-level option. Unless there is *some* signalling from btrfs, there is really not much systemd can *safely* do. -- Tomasz Pala <go...@pld-linux.org> -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
