From owner-freebsd-stable@FreeBSD.ORG Mon Dec 24 13:27:39 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A5B7E6B; Mon, 24 Dec 2012 13:27:39 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-wg0-x22a.google.com (wg-in-x022a.1e100.net [IPv6:2a00:1450:400c:c00::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 7C61F8FC0A; Mon, 24 Dec 2012 13:27:38 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id dr1so2623138wgb.5 for ; Mon, 24 Dec 2012 05:27:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YRIlK9VqdWvMLcDxEsIZchxkWPzUjTcbf/RK2Id9+MI=; b=C7xkjetrwTBbNKuYDBRhBegxYEnLMIUgTNvrf6549CDR1YuXLIF28mdpXRZOPbe0tl KDE+GUNfJOVQlNNgvXidq9LdNEq/c4oeWaUyNFZUDYB4BF8RWzyiHv7UlWSlasIPG3p2 8gJjOxlgk5bb9wBRWjDEQ6tjJRvUhTvXzDG/g10PGeLVjVxOPf22fUgmlhX43Kcd018I 64gvwQsE7U4SzJmf67NylFaEHen/P1R0+Q1Wa8pmHtkEIuyAmyhsucJV/qmg85dqOHpu 5JTn2/LU9V0TlvlTwZfkVwI61qXsmnbZDNx/7TTxlS+w9s/hQY2tc5XkO7BYMeKfNsip vZqQ== MIME-Version: 1.0 Received: by 10.180.81.39 with SMTP id w7mr35005102wix.15.1356355657157; Mon, 24 Dec 2012 05:27:37 -0800 (PST) Received: by 10.216.172.197 with HTTP; Mon, 24 Dec 2012 05:27:36 -0800 (PST) In-Reply-To: <50D6FDBD.6000401@FreeBSD.org> References: <50B6598B.20200@FreeBSD.org> <50D6F901.7050206@FreeBSD.org> <50D6FDBD.6000401@FreeBSD.org> Date: Mon, 24 Dec 2012 15:27:36 +0200 Message-ID: Subject: Re: [HEADSUP] zfs root pool mounting From: Kimmo Paasiala To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2012 13:27:39 -0000 On Sun, Dec 23, 2012 at 2:49 PM, Andriy Gapon wrote: > on 23/12/2012 14:34 Kimmo Paasiala said the following: >> On Sun, Dec 23, 2012 at 2:28 PM, Andriy Gapon wrote: >>> >>> I have MFCed the following change, so please double-check if you might be >>> affected. Preferably before upgrading :-) >>> >>> on 28/11/2012 20:35 Andriy Gapon said the following: >>>> >>>> Recently some changes were made to how a root pool is opened for root filesystem >>>> mounting. Previously the root pool had to be present in zpool.cache. Now it is >>>> automatically discovered by probing available GEOM providers. >>>> The new scheme is believed to be more flexible. For example, it allows to prepare >>>> a new root pool at one system, then export it and then boot from it on a new >>>> system without doing any extra/magical steps with zpool.cache. It could also be >>>> convenient after zpool split and in some other situations. >>>> >>>> The change was introduced via multiple commits, the latest relevant revision in >>>> head is r243502. The changes are partially MFC-ed, the remaining parts are >>>> scheduled to be MFC-ed soon. >>>> >>>> I have received a report that the change caused a problem with booting on at least >>>> one system. The problem has been identified as an issue in local environment and >>>> has been fixed. Please read on to see if you might be affected when you upgrade, >>>> so that you can avoid any unnecessary surprises. >>>> >>>> You might be affected if you ever had a pool named the same as your current root >>>> pool. And you still have any disks connected to your system that belonged to that >>>> pool (in whole or via some partitions). And that pool was never properly >>>> destroyed using zpool destroy, but merely abandoned (its disks >>>> re-purposed/re-partitioned/reused). >>>> >>>> If all of the above are true, then I recommend that you run 'zdb -l ' for >>>> all suspect disks and their partitions (or just all disks and partitions). If >>>> this command reports at least one valid ZFS label for a disk or a partition that >>>> do not belong to any current pool, then the problem may affect you. >>>> >>>> The best course is to remove the offending labels. >>>> >>>> If you are affected, please follow up to this email. >> >> Much appreciated! >> >> I have verified that my system is not affected. >> >> One question, do I have to rewrite the zfs gpt boot loader >> (/boot/gptzfsboot) onto the freebsd-boot partition to make use of this >> change? > > This change is kernel-level only. There is no interaction with boot blocks. > > -- > Andriy Gapon I can happily report that booting from the ZFS pool works on my 9-STABLE system without the zpool.cache file. Thanks, merry christmas and happy new year! -Kimmo