From: David Sterba <dsterba@suse.cz>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Anand Jain <anand.jain@oracle.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>,
linux-kernel@vger.kernel.org, Alex Romosan <aromosan@gmail.com>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Subject: Re: [btrfs] commit bc27d6f0aa0e4de184b617aceeaf25818cc646de breaks update-grub
Date: Thu, 11 Jan 2024 16:50:56 +0100 [thread overview]
Message-ID: <20240111155056.GG31555@twin.jikos.cz> (raw)
In-Reply-To: <39e3a4fe-d456-4de4-b481-51aabfa02b8d@leemhuis.info>
On Thu, Jan 11, 2024 at 12:45:50PM +0100, Thorsten Leemhuis wrote:
> [Adding Anand Jain, the author of the culprit to the list of recipients;
> furthermore CCing the the Btrfs maintainers and the btrfs list; also
> CCing regression list, as it should be in the loop for regressions:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>
> On 08.01.24 15:11, Alex Romosan wrote:
> > Please Cc me as I am not subscribed to the list.
> >
> > Running my own compiled kernel without initramfs on a lenovo thinkpad
> > x1 carbon gen 7.
> >
> > Since version 6.7-rc1 i haven't been able to to a grub-update,
> >
> > instead i get this error:
> >
> > grub-probe: error: cannot find a device for / (is /dev mounted?) solid
> > state drive
> >
> > 6.6 was the last version that worked.
> >
> > Today I did a git-bisect between these two versions which identified
> > commit bc27d6f0aa0e4de184b617aceeaf25818cc646de btrfs: scan but don't
> > register device on single device filesystem as the culprit. reverting
> > this commit from 6.7 final allowed me to run update-grub again.
> >
> > not sure if this is the intended behavior or if i'm missing some other
> > kernel options. any help/fixes would be appreciated.
> >
> > thank you.
>
> Thanks for the report. To be sure the issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
> tracking bot:
>
> #regzbot ^introduced bc27d6f0aa0e4de184b617aceeaf25818cc646de
> #regzbot title btrfs: update-grub broken (cannot find a device for / (is
> /dev mounted?))
> #regzbot ignore-activity
The bug is also tracked at https://bugzilla.kernel.org/show_bug.cgi?id=218353 .
next prev parent reply other threads:[~2024-01-11 15:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 14:11 Alex Romosan
2024-01-11 11:45 ` Thorsten Leemhuis
2024-01-11 15:50 ` David Sterba [this message]
2024-01-11 17:06 ` David Sterba
2024-01-11 23:24 ` Anand Jain
2024-01-22 0:07 ` Alex Romosan
2024-01-22 1:35 ` Anand Jain
2024-01-22 1:46 ` Alex Romosan
2024-02-01 10:25 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-03 22:03 ` David Sterba
[not found] ` <CAKLYgeLhcE5+Td9eGKAi0xeXSsom381RxuJgKiQ0+oHDNS_DJA@mail.gmail.com>
2024-02-04 18:29 ` Alex Romosan
2024-02-05 11:26 ` David Sterba
2024-02-05 12:38 ` Alex Romosan
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=20240111155056.GG31555@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=aromosan@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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
all inboxes | Powered by JetHome®