[systemd-devel] more verbose debug info than systemd.log_level=debug?

Mantas Mikul─Śnas grawity at gmail.com
Mon Mar 27 19:27:16 UTC 2017


On Mon, Mar 27, 2017 at 10:20 PM, Chris Murphy <lists at colorremedies.com>
wrote:

> Ok so the dirty file system problem always happens with all pk offline
> updates on Fedora using either ext4 or XFS with any layout; and it's
> easy to reproduce.
>
> 1. Clean install any version of Fedora, defaults.
> 2. Once Gnome Software gives notification of updates, Restart & Install
> 3. System reboots, updates are applied, system reboots again.
> 4. Now check the journal filtering for 'fsck' and you'll see it
> replayed the journals; if using XFS check the filter for "XFS" and
> you'll see the kernel did journal replace at mount time.
>
> Basically systemd is rebooting even though the remoun-ro fails
> multiple times, due to plymouth running off root fs and being exempt
> from being killed, and then reboots anyway, leaving the file system
> dirty. So it seems like a flaw to me to allow an indefinite exemption
> from killing a process that's holding a volume rw, preventing
> remount-ro before reboot.
>
> So there's a risk that in other configurations this makes either ext4
> and XFS systems unbootable following an offline update.


So on the one hand it's probably a Plymouth bug or misconfiguration (it
shouldn't mark itself exempt unless it runs off an in-memory initramfs).

But on the other hand, are filesystems really so fragile? Even though it's
after a system upgrade (which updated many files), I was sure systemd at
least tries to *sync* all remaining filesystems before reboot, doesn't it?

-- 
Mantas Mikul─Śnas <grawity at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20170327/0f776b1c/attachment.html>


More information about the systemd-devel mailing list