From owner-freebsd-stable@FreeBSD.ORG Mon Apr 7 13:59:28 2014 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 ESMTPS id 7A0B47D9 for ; Mon, 7 Apr 2014 13:59:28 +0000 (UTC) Received: from mail.feld.me (mail.feld.me [66.170.3.6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.feld.me", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09A9A139 for ; Mon, 7 Apr 2014 13:59:27 +0000 (UTC) Received: from mail.feld.me (mail.feld.me [66.170.3.6]); by mail.feld.me (OpenSMTPD) with ESMTP id 5052b8bc; for ; Mon, 7 Apr 2014 08:59:24 -0500 (CDT) Received: from feld@feld.me by mail.feld.me (Archiveopteryx 3.2.0) with esmtpsa id 1396879163-54438-54435/5/2; Mon, 7 Apr 2014 13:59:23 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Date: Mon, 7 Apr 2014 08:59:23 -0500 From: Mark Felder To: freebsd-stable@freebsd.org Subject: Re: Note for those pulling in new ZFS feature flags In-Reply-To: <20140407135421.GA16385@behemoth> References: <20140407135421.GA16385@behemoth> Message-Id: X-Sender: feld@FreeBSD.org User-Agent: Roundcube Webmail/0.9.5 Sender: feld@feld.me X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 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, 07 Apr 2014 13:59:28 -0000 On 2014-04-07 08:54, Chris Nehren 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. > > I have also filed a PR to note that situations like these should > be noted in UPDATING, kern/188328. Hopefully this post saves > someone else a few hours. I also created this little handy script to more easily update my bootcode... https://feld.me/freebsd/bootcode-update.sh