From: Theodore Ts'o <tytso@mit.edu>
To: Felipe A Rodriguez <far@illumenos.com>
Cc: linux-ext4@vger.kernel.org, grub-devel@gnu.org
Subject: Re: Possible regression in e2fsprogs-1.43.4
Date: Fri, 23 Jun 2017 15:53:18 -0400 [thread overview]
Message-ID: <20170623195318.cfs4ftpmy5nhcccy@thunk.org> (raw)
In-Reply-To: <B2DFC17F-1CFC-410E-9449-2393D51C700B@illumenos.com>
+grub-devel
On Sat, Jun 10, 2017 at 04:00:20PM +0200, Felipe A Rodriguez wrote:
> Upgrading from e2fsprogs-1.42.13 to e2fsprogs-1.43.4 causes the boot
> loader to fail (unknown filesystem error) on the x86_64 VM I use for
> initial testing. I traced the problem to changes in the e2fsprogs
> configuration file which now sets 64 bit flags. I tried upgrading
> to GRUB 2.02 but that did not resolve the problem. Reverting the
> changes per the patch below fixes the problem.
Hmm, my laptop has been using a file system with the 64-bit feature
enabled for quite some time, and my Debian Stretch system has been
using Grub 2.02 to boot my system without any difficulties.
I've done a quick check of the Debian patches and none of them seem to
modify Grub's ext2/ext4 file system implementation. So I don't know
what to tell you. Are you sure you properly reinstalled grub on the
boot device after you upgraded to grub 2.02?
Cheers,
- Ted
next prev parent reply other threads:[~2017-06-23 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 14:00 Possible regression in e2fsprogs-1.43.4 Felipe A Rodriguez
2017-06-23 19:53 ` Theodore Ts'o [this message]
2017-06-23 21:29 ` Christian Hesse
2017-06-24 19:08 ` Felipe A Rodriguez
2017-06-24 21:31 ` Vladimir 'phcoder' Serbinenko
2017-06-25 18:16 ` Possible regression in e2fsprogs-1.43.4 [RESOLVED] Felipe A Rodriguez
2017-06-26 2:40 ` Theodore Ts'o
2017-06-26 6:46 ` Felipe A Rodriguez
2017-06-27 1:53 ` Theodore Ts'o
2017-06-27 11:58 ` Felipe A Rodriguez
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=20170623195318.cfs4ftpmy5nhcccy@thunk.org \
--to=tytso@mit.edu \
--cc=far@illumenos.com \
--cc=grub-devel@gnu.org \
--cc=linux-ext4@vger.kernel.org \
/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