Blame SOURCES/0201-ppc64le-has-no-separate-boot-mount-1261926.patch

a85e8e
From 17a76a878a6843cbd5d62477caa93b0628d222cd Mon Sep 17 00:00:00 2001
a85e8e
From: Robert Marshall <rmarshall@redhat.com>
a85e8e
Date: Fri, 17 Jun 2016 11:47:34 -0400
a85e8e
Subject: [PATCH 201/260] ppc64le has no separate /boot mount (#1261926)
a85e8e
a85e8e
The patch for rhbz#1212114 ensures that ppc64le systems sync grub config
a85e8e
changes to disk prior to grub-mkconfig completion and a reboot.
a85e8e
a85e8e
This patch required checking for /boot as its own mount point because
a85e8e
issuing fsfreeze to a root partition is unwise. For administrators who
a85e8e
configured a ppc64le system with no separate /boot partition, the failed
a85e8e
check results in an error message. The file is written and would work
a85e8e
most of the time, however, it also introduces a corner case where the
a85e8e
behavior manifested in rhbz#1212114 could re-appear on these systems.
a85e8e
a85e8e
The system call issued by fsfreeeze is being issued by methods within
a85e8e
the anaconda installer and can be removed from GRUB proper.
a85e8e
a85e8e
Related: rhbz#1315468
a85e8e
Resolves: rhbz#1261926
a85e8e
---
a85e8e
 util/grub-mkconfig.in | 9 ---------
a85e8e
 1 file changed, 9 deletions(-)
a85e8e
a85e8e
diff --git a/util/grub-mkconfig.in b/util/grub-mkconfig.in
a85e8e
index 7db894999..0cfe60475 100644
a85e8e
--- a/util/grub-mkconfig.in
a85e8e
+++ b/util/grub-mkconfig.in
a85e8e
@@ -291,12 +291,3 @@ fi
a85e8e
 
a85e8e
 gettext "done" >&2
a85e8e
 echo >&2
a85e8e
-
a85e8e
-# make sure changes make it to the disk.
a85e8e
-# if /boot is a mountpoint, force the meta data on disk
a85e8e
-# to by-pass writeback delay.
a85e8e
-# PPC64LE-only to deal with Petitboot issues
a85e8e
-ARCH=$(uname -m)
a85e8e
-if [ "${ARCH}" = "ppc64le" ]; then
a85e8e
-    sync && mountpoint -q /boot &&fsfreeze -f /boot && fsfreeze -u /boot
a85e8e
-fi
a85e8e
-- 
a85e8e
2.13.0
a85e8e