On Tue, May 15, 2018 at 6:33 AM, Daniel Kiper <dki...@net-space.pl> wrote: > Hi, > > On Mon, May 14, 2018 at 01:12:27PM -0600, Chris Murphy wrote: >> Hi, >> >> xfsprogs 4.16.0 defaults to enabling "sparse inode" which is not >> compatible with GRUB. >> >> Downstream bug in Fedora, grub-probe fails so grub-install can't work; >> and on systems with an already properly installed core.img with XFS >> support, it can't read an XFS file system with this feature set. >> https://bugzilla.redhat.com/show_bug.cgi?id=1575797 >> >> Make them default >> https://www.spinics.net/lists/linux-xfs/msg16598.html >> >> Change description, page 48 >> https://mirrors.edge.kernel.org/pub/linux/utils/fs/xfs/docs/xfs_filesystem_structure.pdf >> >> It'd be helpful to know the approximate time frame for getting this >> fixed, to know whether for Fedora 29 /boot on XFS should be inhibited >> until a proper tested patch for GRUB exists. > > Sorry, I do not have resources right now to do that. However, > if somebody will post the patches I am happy to review them.
OK thanks for the update. We appear to have a near term work around for the installer: if /boot is XFS, then format with '-i sparse=0' which will avoid the problem. Meanwhile / or /home still use the new default of sparse=1. -- Chris Murphy _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
