From owner-freebsd-fs@FreeBSD.ORG Thu Dec 12 23:24:26 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80BCC43E; Thu, 12 Dec 2013 23:24:26 +0000 (UTC) Received: from mail-vb0-x22d.google.com (mail-vb0-x22d.google.com [IPv6:2607:f8b0:400c:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 136411376; Thu, 12 Dec 2013 23:24:26 +0000 (UTC) Received: by mail-vb0-f45.google.com with SMTP id i12so796467vbh.18 for ; Thu, 12 Dec 2013 15:24:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=KD6b+CZv0oSRisKkgYhuwobPA5wl+NKNLO+ypJJiwX8=; b=VrFLiEFvyBgFAr8cRYIbpDQN6KnBj7X6iVxKk2PS9K719l+se5iThdjuJ4OWjSeB/f 7DNFl3/kemIPhO6cjpb8IFetTwM+pmTA2XDucUz44Xaf2iEcMd4zPsib1iOSczRrOzuW MADnyDxB/QDHZQLgTvBKe8qPJ4INgZQk2POcwioeWBokiEaFaCTm6U7nuSCpQAm1XDQt NlYtXRY1tkgcWXp8MSsp9oqWPUERZPF+aW1Zn8sUBSX5l1ytCiKpyA0uV5JubHir0Bdr QJOY9/el5u9aYOVBQYl//v1tAMLCEgLaRFlacUlFAu0ZsMH3gJNHUGvsHzJbrc4VdHnh 5BnQ== MIME-Version: 1.0 X-Received: by 10.221.60.134 with SMTP id ws6mr728955vcb.44.1386890665101; Thu, 12 Dec 2013 15:24:25 -0800 (PST) Sender: artemb@gmail.com Received: by 10.221.9.2 with HTTP; Thu, 12 Dec 2013 15:24:25 -0800 (PST) In-Reply-To: <52AA43E3.7020706@peterschmitt.fr> References: <52A6EB67.3000103@peterschmitt.fr> <52A99917.2050200@FreeBSD.org> <52A9AA45.2000907@peterschmitt.fr> <52A9ABEF.8080509@FreeBSD.org> <52AA26DA.30809@peterschmitt.fr> <52AA43E3.7020706@peterschmitt.fr> Date: Thu, 12 Dec 2013 15:24:25 -0800 X-Google-Sender-Auth: R-flaJXYaD-rgC-YUp_fdI1cGLc Message-ID: Subject: Re: 10.0-BETA4 (upgraded from 9.2-RELEASE) zpool upgrade -> boot failure From: Artem Belevich To: Florent Peterschmitt Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs , freebsd-stable stable , Andriy Gapon X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Dec 2013 23:24:26 -0000 On Thu, Dec 12, 2013 at 3:16 PM, Florent Peterschmitt wrote: > Le 12/12/2013 22:04, Artem Belevich a =E9crit : >> On Thu, Dec 12, 2013 at 1:12 PM, Florent Peterschmitt >> wrote: >>>> do "zdb -l /dev/ada0" (and all other slices on ada0) and check >>>> whether it reports anything unexpected. >>>> >>>> --Artem >>> >>> rescue-bsd# zdb -l /dev/ada0 >>> -------------------------------------------- >>> LABEL 0 >>> -------------------------------------------- >>> failed to unpack label 0 >>> -------------------------------------------- >>> LABEL 1 >>> -------------------------------------------- >>> failed to unpack label 1 >>> -------------------------------------------- >>> LABEL 2 >>> -------------------------------------------- >>> failed to unpack label 2 >>> -------------------------------------------- >>> LABEL 3 >>> -------------------------------------------- >>> failed to unpack label 3 >>> >>> >>> Well=85 this sounds bad, right? >> >> This looks the way it's supposed to -- no unwanted ZFS pool info is foun= d. >> >> Now repeat that for all ada0p? and make sure only the slice that's >> part of your pool shows ZFS labels and only for one pool. >> >> Think a bit about how bootloader figures out how your pool is built. >> All it has access to is a raw disk and partition table. So in order to >> find the pool it probes raw disk and all partitions trying to find ZFS >> labels and then uses info in those labels to figure out pool >> configuration. If bootloader finds stale ZFS labels left from a >> previous use of the disk in some other pool, it would potentially mess >> up detection of your real boot pool. >> >> --Artem >> > > rescue-bsd# zdb -l /dev/ada0p1 ...[snip]... > -------------------------------------------- > LABEL 3 > -------------------------------------------- > version: 5000 > name: 'tank' > state: 0 > txg: 1248416 > pool_guid: 14109252772653171024 > hostid: 1349238423 > hostname: 'rescue-bsd.ovh.net' > top_guid: 8826573031965252809 > guid: 8826573031965252809 > vdev_children: 1 > vdev_tree: > type: 'disk' > id: 0 > guid: 8826573031965252809 > path: '/dev/gpt/zfs-root' > phys_path: '/dev/gpt/zfs-root' > whole_disk: 1 > metaslab_array: 30 > metaslab_shift: 32 > ashift: 9 > asize: 493660405760 > is_log: 0 > create_txg: 4 > features_for_read: > > > Since freebsd-zfs is installed on ada0p3, it's normal to get that. Then, > what can you say about that? Well, you've eliminated the possibility that there may be orphaned ZFS labels messing up with the boot. --Artem