On Mon, May 14, 2018 at 11:36 AM, Darrick J. Wong <darrick.wong@xxxxxxxxxx> wrote: > On Mon, May 14, 2018 at 11:15:27AM -0600, Chris Murphy wrote: >> Downstream bug, Fedora Rawhide being a canary in the coal mine! >> https://bugzilla.redhat.com/show_bug.cgi?id=1575797 >> >> Comment 8 about the kernel warning related to freeze/thaw is curious >> but ends up being unrelated to this problem. >> >> The gist is that xfsprogs 4.16.0 formatted volumes aren't recognized >> by either GRUB user space tools, or the GRUB core.img (whether of the >> embedded BIOS variety or the grubx64.efi variety) >> >> Anyway, open question for XFS devs if this should be fixed in xfsprogs >> or GRUB. I haven't tested this with syslinux to know if it has a >> similar problem. > > mkfs.xfs 4.16 enables sparse inodes by default, which is why grub > doesn't recognise the boot fs. grub needs fixing, or $installer needs > to disable sparse inodes, I think. > Yep I just discovered this looking through 4.16.0 change log, and then tried swapping the feature: xfsprogs 4.15.1 with -i sparse=1 results in failure; and xfsprogs 4.16.0 with -i sparse=0 works. I updated the downstream bug. Historically the installer team is very reluctant to use non-default mkfs, so I suspect there needs to be a GRUB patch, or chances are the installer team will proscribe /boot on XFS rather than hold up xfsprogs 4.16.1. -- 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
