Received: by 2002:a05:7412:e794:b0:fa:551:50a7 with SMTP id o20csp1583588rdd; Thu, 11 Jan 2024 03:46:12 -0800 (PST) X-Google-Smtp-Source: AGHT+IE+p9IpuB1AUDgWFtjnkL2mtrN+b7phB3CnFffnlEHmKY8o2Yzyih3rqe7WzER8nWlTE5yq X-Received: by 2002:a25:2d17:0:b0:dbc:e058:ae9c with SMTP id t23-20020a252d17000000b00dbce058ae9cmr968143ybt.110.1704973571765; Thu, 11 Jan 2024 03:46:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1704973571; cv=none; d=google.com; s=arc-20160816; b=wLv0HTmkEafcgqdapf90unxBRsxK1dDcD1n8a/IeTqKEhh/I06EPg4ZDxaJdMfg68K aN/5b9+zIYSd4+L3mpMHXeFOCxUwqBs2nlsltqiwyyOp2DjWJpk8rosHQ6YeW4R5LGes R0K5tW4TGtQZqKHADvQ51EO7OFi4pUMLJHQTnvTIfUYxU2lgEALC6LcIj+ETg45H5PST xf+B+39xjYhreQgVbfgc9kcMU0F0WvJM4jxrYNSb5Te5rFg+4GKgiSAqsLHkgRl2OwA2 /49XArymt28oB3s9WApIkn22qbq9iqaDlqKMaHSbO6Tvifgtkwf8NqZhE6B8QKPEEXl5 WYiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:in-reply-to:cc:from:references:to :content-language:subject:user-agent:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:date:message-id; bh=b2ptTQgzxihExDJI2SI5G2h0OdV+YlE+iQi8/r8jhYM=; fh=cvf+2vRM9CTkODQQWzUfq/W2YSOCqcPj4f5ZDS5kZig=; b=hWCjUX7TNDS33fQ/yY748DJVvt4fK85EAKsbowX+FOsw9ykHJgIqgeTg1smG1jSAbZ r22QZNT02xXaWpLC9jEKwluiUum6Ws5szeXd+DX5pxWD5KzO76RsbMon1AY9+MLw+QFJ 7G1gbum7DdzqELpyP6bZqVH64sF5NVVXR45LXtljKwWNm2EJLkctOqWeBCQ3hOtOet6i GnoJdUT4GT0Dr4DryvGuirf+VeMP5lqi/iuV9dBEMpW3sGHaLSItPFjSRtxt5MswEL8v KOYwOeWn3Ao2R89UlCkzii+vqWCaKyvJEju6F6aDPGit2TM6vg7gsMvADoQn1L18OeHB GH+w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel+bounces-23507-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-23507-linux.lists.archive=gmail.com@vger.kernel.org" Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [2604:1380:45d1:ec00::1]) by mx.google.com with ESMTPS id m11-20020a05622a054b00b00428405c062csi753291qtx.635.2024.01.11.03.46.11 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 11 Jan 2024 03:46:11 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-23507-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel+bounces-23507-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-23507-linux.lists.archive=gmail.com@vger.kernel.org" Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 816941C216BE for ; Thu, 11 Jan 2024 11:46:11 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 9DF36154AC; Thu, 11 Jan 2024 11:46:03 +0000 (UTC) Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1ADDC14F9D; Thu, 11 Jan 2024 11:46:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=leemhuis.info Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=leemhuis.info Received: from [2a02:8108:8980:2478:8cde:aa2c:f324:937e]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1rNtVP-0007Bi-K4; Thu, 11 Jan 2024 12:45:51 +0100 Message-ID: <39e3a4fe-d456-4de4-b481-51aabfa02b8d@leemhuis.info> Date: Thu, 11 Jan 2024 12:45:50 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [btrfs] commit bc27d6f0aa0e4de184b617aceeaf25818cc646de breaks update-grub Content-Language: en-US, de-DE To: Anand Jain References: From: Thorsten Leemhuis Cc: linux-btrfs , Linux kernel regressions list , linux-kernel@vger.kernel.org, Alex Romosan , Chris Mason , Josef Bacik , David Sterba In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1704973561;f3cf3eb7; X-HE-SMSGID: 1rNtVP-0007Bi-K4 [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 This isn't a regression? This issue or a fix for it are already discussed somewhere else? It was fixed already? You want to clarify when the regression started to happen? Or point out I got the title or something else totally wrong? Then just reply and tell me -- ideally while also telling regzbot about it, as explained by the page listed in the footer of this mail. Developers: When fixing the issue, remember to add 'Link:' tags pointing to the report (the parent of this mail). See page linked in footer for details. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.