From: Chris Murphy <lists@colorremedies.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Goffredo Baroncelli <kreijack@inwind.it>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: GRUB bug with Btrfs multiple devices
Date: Sat, 30 Nov 2019 10:14:47 -0700 [thread overview]
Message-ID: <CAJCQCtRsjA=TTY8XY3QLO_uJVsGD1-E7k3OvnOdTnOJ76pezVw@mail.gmail.com> (raw)
In-Reply-To: <8a86c7ef-39ab-7c35-f39b-e05ab7543a11@gmail.com>
On Sat, Nov 30, 2019 at 10:02 AM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
>
> GRUB is normally using hints - grub-install (and grub-mkconfig) tries to
> guess firmware device name. At boot time grub tries to access hinted
> device first, if it succeeds, it does not try anything else. With second
> btrfs partition grub needs to find second device at boot time so it now
> probes everything and hits those vendor media devices.
>
> At least this explains what you see as well as ...
>
> > Last time this
> > happened, all I did was remove the 2nd device and the problem went
> > away.
>
> ... this.
Ahhh, that makes complete sense. So it is Btrfs multiple device
related, but not a bug in btrfs.c per se.
>
> If you go in grub shell in this state (without errors), do you see those
> ghost devices?
Uncertain. My vague memory recall is that yes they are there, because
I found their existence strange and different compared to pre-GRUB
2.02 where on this same system I'd see only either hd0 or hd1 (one
without the other), along with cd0. But something changed either with
a firmware update from Apple, or GRUB, that resulted in additional
GRUB devices, hd2, hd3, hd4, hd5.
> > I'm ready to try that again (remove the 2nd device) and see if
> > the problem goes away, but has enough information been collected about
> > the present state?
> >
> >
>
> If you are reasonably sure that all errors are related to those phantom
> devices - I would say yes, the reason for these phantom devices to exist
> is already clear.
I'll give it a shot in a bit.
--
Chris Murphy
next prev parent reply other threads:[~2019-11-30 17:15 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
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 [this message]
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='CAJCQCtRsjA=TTY8XY3QLO_uJVsGD1-E7k3OvnOdTnOJ76pezVw@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=arvidjaar@gmail.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).