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. Chris Murphy _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
