From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from userp2120.oracle.com ([156.151.31.85]:57934 "EHLO userp2120.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752347AbeENRgO (ORCPT ); Mon, 14 May 2018 13:36:14 -0400 Date: Mon, 14 May 2018 10:36:10 -0700 From: "Darrick J. Wong" Subject: Re: xfsprogs 4.16.0 format change, GRUB error unknown filesystem Message-ID: <20180514173610.GC4933@magnolia> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Chris Murphy Cc: xfs list 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. --D > > -- > Chris Murphy > -- > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html