From owner-freebsd-current@FreeBSD.ORG Wed Dec 19 22:34:14 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8A4603B9; Wed, 19 Dec 2012 22:34:14 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) by mx1.freebsd.org (Postfix) with ESMTP id BA6008FC0C; Wed, 19 Dec 2012 22:34:12 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id hm6so3922765wib.3 for ; Wed, 19 Dec 2012 14:34:11 -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=/zSWCbGOnCf6sTEZPWoRVtLZMNZSioB1F/IyerX/OIs=; b=lAgzeLCoJBtEkcMQsmql1AuKSbCByUn+z2Q+cKNKSuuUfRZDXookbjVBs2N9Rxloqd aj+Apih/Xi/2QXFzS+WcKjlAPciBl1zMfqp15QlMoDLD7bhb7XaKB9HTPK5ZwvBrDygr q9GYXHl1jV+rjFQVqyiEsCgSpCwVKYsn6Yj9NJerxbOebspGcjMwI7kixr4MjrqGQsmC Gs/tceQ0veL+8fmhOkQKNNKeAVhC1NlC0hlbabWJwCeAoWXWf1znvTB8/bkEUYOfKRC1 i6e8Lbc307tQjHHF6cMBmRfS6ca4HIUVhFyUzCE0EvxwuVFZGQ2g4wR0V1dNDytHbk/w cChA== MIME-Version: 1.0 Received: by 10.180.81.39 with SMTP id w7mr13868580wix.15.1355956451397; Wed, 19 Dec 2012 14:34:11 -0800 (PST) Received: by 10.216.172.197 with HTTP; Wed, 19 Dec 2012 14:34:11 -0800 (PST) In-Reply-To: <50B6598B.20200@FreeBSD.org> References: <50B6598B.20200@FreeBSD.org> Date: Thu, 20 Dec 2012 00:34:11 +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 current , FreeBSD Stable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2012 22:34:14 -0000 On Wed, Nov 28, 2012 at 8:35 PM, Andriy Gapon wrote: > > 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. > > -- > Andriy Gapon > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Hello, What is the status of the MFC process to 9-STABLE? I'm on 9-STABLE r244407, should I be able to boot from this ZFS pool without zpool.cache? zpool status pool: zwhitezone state: ONLINE scan: scrub repaired 0 in 0h53m with 0 errors on Sat Dec 15 23:41:09 2012 config: NAME STATE READ WRITE CKSUM zwhitezone ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 label/wzdisk0 ONLINE 0 0 0 label/wzdisk1 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 label/wzdisk2 ONLINE 0 0 0 label/wzdisk3 ONLINE 0 0 0 errors: No known data errors