From owner-freebsd-stable@FreeBSD.ORG Wed Apr 9 03:29:58 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 6FD39FB2 for ; Wed, 9 Apr 2014 03:29:58 +0000 (UTC) Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) (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 3D5611FB1 for ; Wed, 9 Apr 2014 03:29:58 +0000 (UTC) Received: by mail-pb0-f50.google.com with SMTP id md12so1920177pbc.37 for ; Tue, 08 Apr 2014 20:29:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=wc2VUcgtBxgz92Pq5oyl7DLzUWVGxgrKQQJimiTGN6U=; b=IvNNbBdKvKVUirriQHV4pKQSeqxF18oWy5br7RqMpHSP7W4D8gH7PwKiT9ThnmOX/W yzpizCuj60Wose6VmtheJm6uWxPJFbyifVgVXosbRRQJ1yCbb9kh/6ZSPyy27IfoJyQw OpFgOKzhPSWvPPBlF9Vx1mNHoxnhUi5WFE3Te1wyEVI1Ll3CsJgGrgUIj7dpthVuguPJ dP8j1nAsINOAlR7XRhF1ohJDtQCf9F2RyuaXC8xushaJZPX7N+/mooGMNO2rppGR2jfg cesiWVs91V/e1XaTJHTyqEatLuicjaPrw48prb4n7HVTwH64KtlZeico3ZRQ3B9uFI06 mOPw== X-Received: by 10.66.171.76 with SMTP id as12mr8937783pac.52.1397014197872; Tue, 08 Apr 2014 20:29:57 -0700 (PDT) Received: from [192.168.1.7] (ppp59-167-128-11.static.internode.on.net. [59.167.128.11]) by mx.google.com with ESMTPSA id jd5sm7949947pbb.18.2014.04.08.20.29.55 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 Apr 2014 20:29:57 -0700 (PDT) Message-ID: <5344BEAF.1030206@FreeBSD.org> Date: Wed, 09 Apr 2014 13:29:51 +1000 From: Kubilay Kocak User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Thunderbird/28.0 MIME-Version: 1.0 To: Paul Mather , Chris Nehren Subject: Re: Note for those pulling in new ZFS feature flags References: <20140407135421.GA16385@behemoth> <20140407145511.GA16747@behemoth> <20140407153040.GA17668@behemoth> <4C688889-96C0-4B8C-82E7-ACC3FB729FAB@gromit.dlib.vt.edu> In-Reply-To: <4C688889-96C0-4B8C-82E7-ACC3FB729FAB@gromit.dlib.vt.edu> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: FreeBSD stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: koobs@FreeBSD.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2014 03:29:58 -0000 On 8/04/2014 3:01 AM, Paul Mather wrote: > On Apr 7, 2014, at 11:30 AM, Chris Nehren wrote: > >> On Mon, Apr 07, 2014 at 17:05:32 +0200, Trond Endrestøl wrote: >>> See: >>> >>> http://svnweb.freebsd.org/base/stable/10/cddl/contrib/opensolaris/cmd/zpool/zpool_main.c?view=markup#l4992 >>> >>> Consider this a lesson learned. Yes, I too was bitten by this once, >>> but never again. ;-) Luckily, I recovered using a snapshot image. >> >> That's funny, because I *specifically* noted the absence of that >> message when I upgraded my pool and spent about 5 minutes >> wondering if it was needed or not. Either way, I think I'll opt >> to doing the bootcode thing every time as well. > > Oddly enough, I was bitten by this recently, too, and had the same > thing happen. I upgraded a pool and was struck by the fact that I > *wasn't* urged to update the boot code and so, after pondering "maybe > this means I don't have to" decided not to. Of course, the system > wouldn't boot and I had to rescue it via a memstick. > > I prefer the unconditional warning. :-) > > Cheers, > > Paul. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Makes me wonder: What might the issues be with upgrading the bootcode for users post-upgrade?