On Fri, Dec 22, 2017 at 9:05 AM, Tomasz Pala <go...@polanet.pl> wrote: > On Thu, Dec 21, 2017 at 07:27:23 -0500, Austin S. Hemmelgarn wrote: > >> Also, it's not 'up to the filesystem', it's 'up to the underlying >> device'. LUKS, LVM, MD, and everything else that's an actual device >> layer is what systemd waits on. XFS, ext4, and any other filesystem >> except BTRFS (and possibly ZFS, but I'm not 100% sure about that) >> provides absolutely _NOTHING_ to wait on. Systemd just chose to handle > > You wait for all the devices to settle. One might have dozen of drives > including some attached via network and it might take a time to become > available. Since systemd knows nothing about underlying components, it > simply waits for the btrfs itself to announce it's ready.
I'm pretty sure degraded boot timeout policy is handled by dracut. The kernel doesn't just automatically assemble an md array as soon as it's possible (degraded) and then switch to normal operation as other devices appear. I have no idea how LVM manages the delay policy for multiple devices. I don't think the delay policy belongs in the kernel. It's pie in the sky, and unicorns, but it sure would be nice to have standardization rather than everyone rolling their own solution. The Red Hat Stratis folks will need something to do this for their solution so yet another one is about to be developed... -- Chris Murphy -- 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
