Date: Mon, 7 Apr 2014 17:05:32 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: Chris Nehren <cnehren+freebsd-stable@pobox.com> Cc: FreeBSD stable <freebsd-stable@freebsd.org> Subject: Re: Note for those pulling in new ZFS feature flags Message-ID: <alpine.BSF.2.00.1404071656540.9102@mail.fig.ol.no> In-Reply-To: <20140407145511.GA16747@behemoth> References: <20140407135421.GA16385@behemoth> <CAFHbX1%2BCerhdfo-VB4dj_JZAkp79b_KD7T0TCxFWTLGFsu-Mpw@mail.gmail.com> <20140407145511.GA16747@behemoth>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 7 Apr 2014 10:55-0400, Chris Nehren wrote: > On Mon, Apr 07, 2014 at 15:36:21 +0100, Tom Evans wrote: > > > 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. > > I'm fairly certain there was no such message, or I would have > dutifully done what it said. I definitely do know there is a > message of that kind when attaching a disk to a mirror, and I've > followed through there without issue. 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. Whenever I upgrade a ZFS system which has a ZFS boot pool, I always upgrade the bootblocks even if I don't upgrade the boot pool to include some new cool zpool feature. Nevertheless, it's still handy to have a recent snapshot available on physical media or as an image file at least. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-stable@FreeBSD.ORG Mon Apr 7 15:29:21 2014 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> 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 EB4F48CD; Mon, 7 Apr 2014 15:29:21 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E7BBD2C; Mon, 7 Apr 2014 15:29:21 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.8/8.14.8) with ESMTP id s37FTDES036598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 7 Apr 2014 09:29:13 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.8/8.14.8/Submit) with ESMTP id s37FTDMR036595; Mon, 7 Apr 2014 09:29:13 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 7 Apr 2014 09:29:13 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Matthew Seaman <matthew@FreeBSD.org> Subject: Re: How to remove X11 support and all ports options depend on X11 In-Reply-To: <5342402D.6070306@FreeBSD.org> Message-ID: <alpine.BSF.2.00.1404070928350.36062@wonkity.com> References: <CAOwMmupogu4xXRL64iGf6Ck_7mHsO=UN5oSr5=G8D6GigXD6Xw@mail.gmail.com> <CAHHBGko+crukS25yQu-z4j=Cp4wQ0ZJDrNThfwd6=sZyc4TbCg@mail.gmail.com> <5342402D.6070306@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 07 Apr 2014 09:29:13 -0600 (MDT) Cc: freebsd-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 15:29:22 -0000 On Mon, 7 Apr 2014, Matthew Seaman wrote: > > 'WITHOUT_X11' is obsolete. What > you want nowadays is: > > OPTIONS_UNSET+= x11 Shouldn't that be uppercase X11?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1404071656540.9102>