From owner-freebsd-fs@FreeBSD.ORG  Sun Sep 21 18:27:40 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 5A44CC81
 for <freebsd-fs@FreeBSD.org>; Sun, 21 Sep 2014 18:27:40 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4054788E
 for <freebsd-fs@FreeBSD.org>; Sun, 21 Sep 2014 18:27:40 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8LIReaM098902
 for <freebsd-fs@FreeBSD.org>; Sun, 21 Sep 2014 18:27:40 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 188328] [zfs] UPDATING should provide caveats for running
 `zpool upgrade`
Date: Sun, 21 Sep 2014 18:27:39 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jan.kokemueller@gmail.com
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-188328-3630-unKflxk9Cn@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-188328-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-188328-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Sep 2014 18:27:40 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188328

Jan Kokem=C3=BCller <jan.kokemueller@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jan.kokemueller@gmail.com

--- Comment #3 from Jan Kokem=C3=BCller <jan.kokemueller@gmail.com> ---
Created attachment 147531
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D147531&action=
=3Dedit
Untested patch that adds the missing bootcode upgrade warning

I've just had the same problem after upgrading my bootpool on 10-stable. I =
used
"zpool upgrade -a". I was already on pool version 5000; only some feature f=
lags
were added. The problematic feature flags not recognized by the bootloader =
were
"com.delphix:hole_birth" and "com.delphix:embedded_data".

I was aware of the "gpart bootcode" dance but "zpool upgrade -a" definitely
showed no message so I assumed it was safe to reboot without upgrading the
bootloader. I've looked at the zpool code and it seems that in the case of
"zpool upgrade -a" the bootcode upgrade warning may not be displayed. I've
attached a patch that should fix it (untested, but it compiles).

--=20
You are receiving this mail because:
You are the assignee for the bug.=