From: Anthony Iliopoulos <ailiop@suse.com>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: xfsprogs-6.5.0 with grub 2.12~rc1-12: unknown filesystem
Date: Sun, 19 Nov 2023 22:06:53 +0100 [thread overview]
Message-ID: <ZVp47fergtXq8CzX@technoir> (raw)
In-Reply-To: <4545292.LvFx2qVVIh@lichtvoll.de>
On Sun, Nov 19, 2023 at 09:16:20PM +0100, Martin Steigerwald wrote:
> Hi!
>
> On recovering from some crazy filesystem corruption, probably related to
> "thou shalt not resume from this hibernation image" (posts on linux-btrfs
> mailing list, I can share link if curious), gladly no loss of important
> data involved, I recreated XFS based /boot with
>
> xfsprogs-6.5.0 (12 Oct 2023)
> […]
> mkfs: enable reverse mapping by default (Darrick J. Wong)
> mkfs: enable large extent counts by default (Darrick J. Wong)
>
> After that GRUB started being funny on me:
>
> update-grub => grub-mkconfig and grub-install both told me:
>
> unknown filesystem
>
> grub-probe revealed that grub did not like to recognize new XFS based
> /boot filesystem. So /boot is Ext4 now. I don't really care.
>
> This is with grub 2.12~rc1-12 on Devuan Ceres.
>
> I read on internet that similar funny stuff happened as Ext4 gained
> features. Could this be the case here as well?
Yes this is due to enabling the large extent counts (nrext64) feature.
> Is this a known issue? I bet it needs a bug report to the GRUB developers?
See:
https://lore.kernel.org/grub-devel/20231026095339.31802-1-ailiop@suse.com/
Regards,
Anthony
next prev parent reply other threads:[~2023-11-19 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 20:16 xfsprogs-6.5.0 with grub 2.12~rc1-12: unknown filesystem Martin Steigerwald
2023-11-19 21:06 ` Anthony Iliopoulos [this message]
2023-11-19 22:28 ` Martin Steigerwald
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=ZVp47fergtXq8CzX@technoir \
--to=ailiop@suse.com \
--cc=linux-xfs@vger.kernel.org \
--cc=martin@lichtvoll.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox