On Mon, May 22, 2017 at 2:46 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > Second, I have only been able to reproduce this problem with grubby + > XFS. OK so this is just on Fedora/RH systems, which is the example case I have. The kernel RPM is running a script called new-kernel-pkg which is part of grubby. It's found here: https://github.com/rhinstaller/grubby/blob/master/new-kernel-pkg # make sure changes make it to the disk. # if /boot is a mountpoint, force the meta data on disk # to by-pass writeback delay. # PPC64LE-only to deal with Petitboot issues if [ "$ARCH" = "ppc64le" ]; then sync && mountpoint -q /boot && fsfreeze -f /boot && fsfreeze -u /boot fi So why only Petitboot on ppc64 is considered to need this? Also I put zipl in the bootloader category that doesn't need to be totally reinstalled, which is incorrect it's more like lilo. I guess I was thinking of yaboot. In any case the main point remains that the common bootloaders being used these days depend only on modification of a bootloader configuration file via the file system that file is located on. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
