From: "Darrick J. Wong" <djwong@kernel.org>
To: Anthony Iliopoulos <ailiop@suse.com>
Cc: 1054644@bugs.debian.org, Philip Hands <phil@hands.com>
Subject: Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices
Date: Fri, 27 Oct 2023 09:25:42 -0700 [thread overview]
Message-ID: <20231027162542.GI11424@frogsfrogsfrogs> (raw)
In-Reply-To: <ZTvjFZPn7KH6euyT@technoir>
On Fri, Oct 27, 2023 at 06:19:33PM +0200, Anthony Iliopoulos wrote:
> On Fri, Oct 27, 2023 at 08:45:05AM -0700, Darrick J. Wong wrote:
> >
> > mkfs.xfs in xfsprogs 6.5 turned on both the large extent counts and
> > reverse mapping btree features by default. My guess is that grub hasn't
> > caught up with those changes to the ondisk format yet.
> >
> > Ah, yeah, upstream grub hasn't picked up large extent counts (internally
> > called nrext64) yet.
> > https://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/fs/xfs.c#n83
>
> Yeap it is due to nrext64, I've submitted a patch to grub (should have
> cc'ed linux-xfs..)
>
> https://lore.kernel.org/grub-devel/20231026095339.31802-1-ailiop@suse.com/
FWIW the patch turning on nrext64 by default was intended for xfsprogs
6.6, but the maintainer decided to merge it early. No complaints here,
but that was a little sooner than I had intended.
--D
> Regards,
> Anthony
next prev parent reply other threads:[~2023-10-27 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871qdgccs5.fsf@nimble.hk.hands.com>
[not found] ` <20231027154505.GL3195650@frogsfrogsfrogs>
2023-10-27 19:18 ` Bug#1054644: xfsprogs-udeb: causes D-I to fail, reporting errors about missing partition devices Philip Hands
[not found] ` <169839498168.1174073.11485737048739628391.reportbug@nimble.hk.hands.com>
[not found] ` <ZTvjFZPn7KH6euyT@technoir>
2023-10-27 16:25 ` Darrick J. Wong [this message]
2023-10-27 22:27 ` Philip Hands
2023-10-27 22:38 ` Bastian Germann
2023-10-27 22:42 ` Processed: " Debian Bug Tracking System
2023-12-25 8:18 ` Debian Bug Tracking System
2023-12-25 8:54 ` Debian Bug Tracking System
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=20231027162542.GI11424@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=1054644@bugs.debian.org \
--cc=ailiop@suse.com \
--cc=phil@hands.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox