Hello, from reading the upstream bug, it's unclear if the systemd commit actually did fix this; it seems like a kernel and/or util-linux patch is needed.
>From your description, it sounds like you're not able to reliably reproduce >this (only randomly), right? Have you tried the upstream reproducer? It >would help a lot if we had a reliable way to reproduce and verify this. https://github.com/systemd/systemd/issues/10872#issuecomment-523399087 ** Bug watch added: github.com/systemd/systemd/issues #10872 https://github.com/systemd/systemd/issues/10872 ** Also affects: systemd via https://github.com/systemd/systemd/issues/10872 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837227 Title: Random mount units sometimes fail, while file system is correctly mounted Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode with a failed mount unit (ext4 file system), while the corresponding file system is in fact correctly mounted. It happens roughly once every 1000 reboots. It seems to be related with this bug : https://github.com/systemd/systemd/issues/10872 Is it possible to apply the fix (https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21) in Ubuntu 18.04 ? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
