From: Chris Murphy <lists@colorremedies.com>
To: Goffredo Baroncelli <kreijack@inwind.it>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: GRUB bug with Btrfs multiple devices
Date: Tue, 26 Nov 2019 18:35:40 -0700 [thread overview]
Message-ID: <CAJCQCtS2CP75JTT4a6y=rzqVtkMTqTRoCvJK9z3mMwLRfKo9Xw@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtR6zMNKnhL7OZ8ZGCDwPfjC9a1cBOg+wt2VqoJTA_NbCQ@mail.gmail.com>
On Tue, Nov 26, 2019 at 4:53 PM Chris Murphy <lists@colorremedies.com> wrote:
>
> On Tue, Nov 26, 2019 at 2:11 PM Goffredo Baroncelli <kreijack@libero.it> wrote:
> >
> > I think that the errors is due to the "rescan" logic (see grub commit [1]). Could you try a more recent grub (2.04 instead of 2.02) ?
>
> Yes Fedora Rawhide has 2.04 in it, so I'll give that a shot next time
> I rebuild this particular laptop, which should be relatively soon; or
> even maybe I can reproduce this problem in a VM with two virtio
> devices.
I was able to just update to the Fedora 2.04-4.fc32 packages. It's not
upstream's but it's a quick and dirty way to give it a shot. Turns
out, the same errors happen, although the line number for efidisk.c
has changed:
https://photos.app.goo.gl/aKWRYhJkkJRDtC1W7
For grins, I dropped to a grub prompt, and issued ls and get a different result:
https://photos.app.goo.gl/MvL9QZa6zGsiktAf9
Also for what it's worth, the Btrfs in question is on hd5,gpt4 and
hd5gpt5 - same physical device, different partitions.
--
Chris Murphy
next prev parent reply other threads:[~2019-11-27 1:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 4:05 GRUB bug with Btrfs multiple devices Chris Murphy
2019-11-26 21:11 ` Goffredo Baroncelli
2019-11-26 23:53 ` Chris Murphy
2019-11-27 1:35 ` Chris Murphy [this message]
2019-11-27 6:07 ` Goffredo Baroncelli
2019-11-28 0:42 ` Chris Murphy
2019-11-28 17:58 ` Goffredo Baroncelli
2019-11-28 20:05 ` Chris Murphy
2019-11-28 21:57 ` Goffredo Baroncelli
2019-11-29 17:57 ` Chris Murphy
2019-11-29 19:54 ` Goffredo Baroncelli
2019-11-29 21:17 ` Chris Murphy
2019-11-30 7:33 ` Andrei Borzenkov
2019-11-30 8:12 ` Goffredo Baroncelli
2019-11-30 16:38 ` Chris Murphy
2019-11-27 6:09 ` Goffredo Baroncelli
2019-11-29 20:50 ` Andrei Borzenkov
2019-11-29 21:11 ` Chris Murphy
2019-11-30 7:31 ` Andrei Borzenkov
2019-11-30 16:31 ` Chris Murphy
2019-11-30 17:02 ` Andrei Borzenkov
2019-11-30 17:14 ` Chris Murphy
2019-11-30 17:34 ` 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='CAJCQCtS2CP75JTT4a6y=rzqVtkMTqTRoCvJK9z3mMwLRfKo9Xw@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).