On Sun, Jan 28, 2018 at 01:00:16 +0100, Tomasz Pala wrote: > It can't mount degraded, because the "missing" device might go online a > few seconds ago. s/ago/after/ >> The central problem is the lack of a timer and time out. > > You got mdadm-last-resort@.timer/service above, if btrfs doesn't lack > anything, as you all state here, this should be easy to make this work. > Go ahead please. And just to make it even easier - this is how you can react to events inside udev (this is to eliminane btrfs-scan tool being required as it sux): https://github.com/systemd/systemd/commit/0e8856d25ab71764a279c2377ae593c0f2460d8f One could even try to trick systemd by SETTING (note the single '=') ENV{ID_BTRFS_READY}="0" - which would probably break as soon as btrfs.ko emits next 'changed' event. -- Tomasz Pala <gotar@xxxxxxxxxxxxx> -- 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
