From owner-freebsd-stable@FreeBSD.ORG Wed Jul 31 16:12:16 2013 Return-Path: Delivered-To: freebsd-stable@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 ESMTP id EA2B92C5 for ; Wed, 31 Jul 2013 16:12:16 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B438829E6 for ; Wed, 31 Jul 2013 16:12:16 +0000 (UTC) Received: by mail-oa0-f44.google.com with SMTP id l20so1928137oag.31 for ; Wed, 31 Jul 2013 09:12:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=8m487Fn8mOHOIJu0lI6i4V7KS9/f9kHqhv6aCa3GdRU=; b=kfYApHCZmbnXiyPRSlQKjn133rplHKNUGBHlOLLgtiOFUF696f2uSNPaCkDz2vH/8p eBdHYz2hSptsW4OGLclHUSQjmgP+ftCbmMW1HsK0T8yjQQb+BsIRfq+kvUoqGZzXnBdl q1Z4g9CaEO+tHbW0MJ52XxXHSuothLKxBZdniEMsWnWsB97eRYTsHcZP4hGFmpMPXccB E6fSXSAaCohCN8Y2DN6Zl9dJoc7roe/bH4QbaerVofND6j9KmSdV5MUVOlZmgGqRsgMS 7xx0sli2zML/kcMDBk3xoD73ky8pDoaJo7HCjvPnJuIcj+yenwnjCA1sPEaxcgG+W6H7 U1Fg== MIME-Version: 1.0 X-Received: by 10.42.215.11 with SMTP id hc11mr709405icb.9.1375287136089; Wed, 31 Jul 2013 09:12:16 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.42.114.73 with HTTP; Wed, 31 Jul 2013 09:12:16 -0700 (PDT) In-Reply-To: References: Date: Wed, 31 Jul 2013 12:12:16 -0400 X-Google-Sender-Auth: b-JqC5gDDMvTW1QSDtCHTRgk8B4 Message-ID: Subject: Re: Problem with zfsloader on 9.2-BETA2 From: J David To: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org 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: Wed, 31 Jul 2013 16:12:17 -0000 On Wed, Jul 31, 2013 at 5:20 AM, Trond Endrest=F8l wrote: > I'm curious as to why you use da?p1 as the freebsd-zfs partitions. Those are whole-disk partitions. > Where does the freebsd-boot partition reside? da?p2? Only the log and cache disks have boot and swap partitions. > What does the "gpart show" command tell you? $ gpart show =3D> 34 63078333 da0 GPT (30G) 34 128 1 freebsd-boot (64k) 162 4194304 2 freebsd-swap (2.0G) 4194466 58883901 3 freebsd-zfs (28G) =3D> 34 62499933 da1 GPT (29G) 34 128 1 freebsd-boot (64k) 162 4194304 2 freebsd-swap (2.0G) 4194466 58305501 3 freebsd-zfs (27G) =3D> 34 1953525101 da2 GPT (931G) 34 222 - free - (111k) 256 1953508495 1 freebsd-zfs (931G) 1953508751 16384 9 !6a945a3b-1dd2-11b2-99a6-080020736631 (8.0M= ) da3 - da7 are identical to da2. So maybe it's a little weird that our boot blocks are on our ZLOG/L2ARC devices, rather than our data devices? But since gptloader (and the old zfsloader) handle this just fine. > I'll let you know how well I fared. Thanks!