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

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