]> git.ipfire.org Git - people/pmueller/ipfire-2.x.git/commit - src/pakfire/lib/functions.sh
Pakfire: call "sync" in function.sh after having extracted archives
authorPeter Müller <peter.mueller@ipfire.org>
Wed, 7 Jul 2021 17:27:14 +0000 (19:27 +0200)
committerMichael Tremer <michael.tremer@ipfire.org>
Fri, 9 Jul 2021 13:54:39 +0000 (13:54 +0000)
commitd0ba077ed3851346b1dd6d82867103df8446aea8
treef810fac263632db49428de6eb2b1ad837ce7a5b6
parenta26986a3b059beeb3f9c37867575dd932f1aa23e
Pakfire: call "sync" in function.sh after having extracted archives

After upgrading to Core Update 157, a few number of users reported their
systems to be unworkable after a reboot. Most of them (the systems, not
the users) were apparently missing the new Linux kernel in their Grub
configuration, causing a non-functional bootloader written to disk.

While we seem to be able to rule out issues related to poor storage
(SDDs, flash cards, etc.) or very high I/O load, it occurred to me we
are not calling "sync" after having extracted a Core Update's .tar.gz
file.

This patch therefore proposes to do so. It is a somewhat homeopathic
approach, though, but might ensure all parts of the system to have
properly processed the contents of an extracted archive. While we cannot
even reasonably guess it will solve the problem(s) mentioned initially,
doing so cannot hurt either.

See also:
https://community.ipfire.org/t/after-update-ipfire-to-157-no-boot/5641/45

Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
src/pakfire/lib/functions.sh