From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: xfs list <linux-xfs@vger.kernel.org>
Subject: Re: xfsprogs 4.16.0 format change, GRUB error unknown filesystem
Date: Mon, 14 May 2018 10:36:10 -0700 [thread overview]
Message-ID: <20180514173610.GC4933@magnolia> (raw)
In-Reply-To: <CAJCQCtQbns7bbE=mWvYuWMi+R5wdphfEjF1F995PVBsoUovnpg@mail.gmail.com>
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
next prev parent reply other threads:[~2018-05-14 17:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 17:15 xfsprogs 4.16.0 format change, GRUB error unknown filesystem Chris Murphy
2018-05-14 17:36 ` Darrick J. Wong [this message]
2018-05-14 17:44 ` Chris Murphy
2018-05-14 17:52 ` Chris Murphy
2018-05-14 18:34 ` Eric Sandeen
2018-05-14 19:08 ` Chris Murphy
2018-05-14 19:11 ` Darrick J. Wong
2018-05-14 19:13 ` Chris Murphy
2018-05-15 12:20 ` Christoph Hellwig
2018-05-15 13:08 ` Darrick J. Wong
2018-05-15 7:50 ` Christoph Hellwig
2018-05-16 6:19 ` Chris Murphy
2018-05-16 14:55 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2018-05-14 19:12 Chris Murphy
2018-05-15 12:33 ` Daniel Kiper
2018-05-15 22:09 ` Chris Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180514173610.GC4933@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.