From: Theodore Ts'o <tytso@mit.edu>
To: Felipe A Rodriguez <far@illumenos.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
Christian Hesse <list@eworm.de>,
linux-ext4@vger.kernel.org
Subject: Re: Possible regression in e2fsprogs-1.43.4 [RESOLVED]
Date: Mon, 26 Jun 2017 21:53:38 -0400 [thread overview]
Message-ID: <20170627015338.5heipzrsmp4dwsmd@thunk.org> (raw)
In-Reply-To: <53DF6A08-AA60-4A9C-BD29-46475DAB528A@illumenos.com>
On Mon, Jun 26, 2017 at 08:46:48AM +0200, Felipe A Rodriguez wrote:
> > So when you say that enabling the 64-bit file system feature causes a
> > regression by causing Grub to fail to be able to read the root file
> > system, I have to respectfully disagree. I do it all the time when I
> > reboot my kernel, and it Works For Me...
>
> Huh ??? I indicated GRUB 2.00 stopped working with the upgrade to 1.43.4, but GRUB 2.02 works fine.
You originally said:
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.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In your follow up, you didn't bother line wrapping your message, so I
misparsed the sentence where you stated "Grub 2.02 does resolve the
problem" because it was burried in a several hundred character long
line. My apologies.
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: Theodore Ts'o <tytso@mit.edu>
To: Felipe A Rodriguez <far@illumenos.com>
Cc: Christian Hesse <list@eworm.de>,
The development of GNU GRUB <grub-devel@gnu.org>,
linux-ext4@vger.kernel.org
Subject: Re: Possible regression in e2fsprogs-1.43.4 [RESOLVED]
Date: Mon, 26 Jun 2017 21:53:38 -0400 [thread overview]
Message-ID: <20170627015338.5heipzrsmp4dwsmd@thunk.org> (raw)
In-Reply-To: <53DF6A08-AA60-4A9C-BD29-46475DAB528A@illumenos.com>
On Mon, Jun 26, 2017 at 08:46:48AM +0200, Felipe A Rodriguez wrote:
> > So when you say that enabling the 64-bit file system feature causes a
> > regression by causing Grub to fail to be able to read the root file
> > system, I have to respectfully disagree. I do it all the time when I
> > reboot my kernel, and it Works For Me...
>
> Huh ??? I indicated GRUB 2.00 stopped working with the upgrade to 1.43.4, but GRUB 2.02 works fine.
You originally said:
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.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In your follow up, you didn't bother line wrapping your message, so I
misparsed the sentence where you stated "Grub 2.02 does resolve the
problem" because it was burried in a several hundred character long
line. My apologies.
- Ted
next prev parent reply other threads:[~2017-06-27 1:53 UTC|newest]
Thread overview: 15+ 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
2017-06-23 21:29 ` Christian Hesse
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-24 21:31 ` Vladimir 'phcoder' Serbinenko
2017-06-25 18:16 ` Possible regression in e2fsprogs-1.43.4 [RESOLVED] Felipe A Rodriguez
2017-06-25 18:16 ` Felipe A Rodriguez
2017-06-26 2:40 ` Theodore Ts'o
2017-06-26 6:46 ` Felipe A Rodriguez
2017-06-26 9:06 ` Colin Watson
2017-06-27 1:53 ` Theodore Ts'o [this message]
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=20170627015338.5heipzrsmp4dwsmd@thunk.org \
--to=tytso@mit.edu \
--cc=far@illumenos.com \
--cc=grub-devel@gnu.org \
--cc=linux-ext4@vger.kernel.org \
--cc=list@eworm.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 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.