From: Chris Murphy <lists@colorremedies.com>
To: Goffredo Baroncelli <kreijack@inwind.it>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: GRUB bug with Btrfs multiple devices
Date: Sat, 30 Nov 2019 09:38:52 -0700 [thread overview]
Message-ID: <CAJCQCtQSpHLzb8qDDh8eMidoyC5OwyD1aDn=GT0PxYcAoJFmXw@mail.gmail.com> (raw)
In-Reply-To: <7aed9b06-b6e9-abef-0241-f542ffffdfc7@inwind.it>
On Sat, Nov 30, 2019 at 1:12 AM Goffredo Baroncelli <kreijack@inwind.it> wrote:
>
> On 29/11/2019 22.17, Chris Murphy wrote:
> > On Fri, Nov 29, 2019 at 12:54 PM Goffredo Baroncelli <kreijack@inwind.it> wrote:
> >> Could you be so kindly to share the picture of the loading of the kernel/initramdisk ? Something like:
> >>
> >> grub> set debug=all
> >> grub> initrd /boot/initrd....
> >>
> >> I hope that the errors come quickly. I don't think that we need the pictuers of all the download. It would be sufficient the pictures until the first (or better second) error....
> >
> > I paged through it for minutes, hundreds of pages and never found any
> > errors. But these are the first pages. This might actually be some
> > kind of search, not load of the kernel, because I pressed tab to
> > autocomplete. But it didn't autocomplete it immediately started
> > spitting out debug pages.
> >
> > https://photos.app.goo.gl/kpa7dJ9spAy29yj26
> >
> > Is it possible to redirect grub debug output to a FAT file?
>
> It is possible to redirect to a serial console ..
> Did the machine has a serial port ?
USB and wired ethernet.
So far I'm unable to reproduce in a VM with 2 partitions used for 2
device Btrfs. It might be a multi-layer bug where the 1st bug must
happen before the 2nd one has a chance of being revealed. The 1st bug
being the issue of phantom devices, which *are* present when the Btrfs
is a single device volume, but none of the errors show up in the
GRUB/pre-boot environment until the 2nd device was added (and new
kernel installed).
It's too bad GRUB doesn't have a debug option to write a file to a FAT
file system. The btrfs debug output is extremely long.
--
Chris Murphy
next prev parent reply other threads:[~2019-11-30 16:39 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 [this message]
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='CAJCQCtQSpHLzb8qDDh8eMidoyC5OwyD1aDn=GT0PxYcAoJFmXw@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).