From owner-freebsd-stable@FreeBSD.ORG  Mon Apr  7 14:36:23 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: 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 ESMTPS id C38CD9A1
 for <stable@freebsd.org>; Mon,  7 Apr 2014 14:36:23 +0000 (UTC)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com
 [IPv6:2a00:1450:4010:c04::22a])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4FF37772
 for <stable@freebsd.org>; Mon,  7 Apr 2014 14:36:23 +0000 (UTC)
Received: by mail-lb0-f170.google.com with SMTP id s7so4848594lbd.15
 for <stable@freebsd.org>; Mon, 07 Apr 2014 07:36:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=googlemail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=mGMaFHE3J6brcIjkAXHA2Fwcn20su33t+HYqNz1fXVw=;
 b=mrFMGOWW9fidvTssPQsCorPkJqP38ObloGpsTatbUZx7lc3MU1kjlP82+wS0OdRTC/
 A9MMTkE9zIRASTV7KhJXFnfqDeTwDf9/QZnk7ubo+WJJf8DTp9a6tJZF0bc/U/w/rsb2
 TtOboVchjLeGQxGJoelWOxfD/yQyCP3/mEdCEshHB2QwfeKtS0TT3O1tZe6NkiVFVbJJ
 Lavb7Ur8K/kp2++eQrkaLVLwm3bSopuTmWHUO4LuMPH4RtkTvTNvkoZoxU66aHzxmhju
 4ofziKDzEeh3YLokJiQEymj9K0JESUjZFVoMToDdGwPslOjJ0TSvpRgS8SmKCqGA4qKY
 9sKw==
MIME-Version: 1.0
X-Received: by 10.112.222.225 with SMTP id qp1mr574805lbc.59.1396881381063;
 Mon, 07 Apr 2014 07:36:21 -0700 (PDT)
Received: by 10.112.129.164 with HTTP; Mon, 7 Apr 2014 07:36:21 -0700 (PDT)
In-Reply-To: <20140407135421.GA16385@behemoth>
References: <20140407135421.GA16385@behemoth>
Date: Mon, 7 Apr 2014 15:36:21 +0100
Message-ID: <CAFHbX1+Cerhdfo-VB4dj_JZAkp79b_KD7T0TCxFWTLGFsu-Mpw@mail.gmail.com>
Subject: Re: Note for those pulling in new ZFS feature flags
From: Tom Evans <tevans.uk@googlemail.com>
To: Chris Nehren <cnehren+freebsd-stable@pobox.com>
Content-Type: text/plain; charset=UTF-8
Cc: FreeBSD Stable <stable@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 14:36:23 -0000

On Mon, Apr 7, 2014 at 2:54 PM, Chris Nehren
<cnehren+freebsd-stable@pobox.com> wrote:
> Not too long ago I upgraded my FreeBSD workstation to 10-STABLE
> from 10-RELEASE in order to try newcons.  After I upgraded to
> 10-STABLE, I saw in `zpool status` that my pools could be
> upgraded to a new version of ZFS.  I did this, and then needed to
> reboot the machine for unrelated reasons.  When it came back up,
> it refused to boot because gptzfsboot couldn't import the pools.
>
> I solved this by re-running `gpart bootcode` for the afflicted
> drives.  This was a bit trying, though, as my workstation is the
> only FreeBSD machine I have readily available.  So, for those
> upgrading their zpools, be careful and remember to fix the
> bootcode if you're using ZFS for the root filesystem.

ISTR that "zpool upgrade" will also remind you to do this if bootfs is
true for the pool you upgraded.

Also, it is always worth having around a bootable memstick available
with the zfs code you are actually running in order to use as a
recovery disk in circumstances like this.

Cheers

Tom