Date: Mon, 7 Apr 2014 13:01:06 -0400 From: Paul Mather <pmather@vt.edu> 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: <4C688889-96C0-4B8C-82E7-ACC3FB729FAB@gromit.dlib.vt.edu> In-Reply-To: <20140407153040.GA17668@behemoth> References: <20140407135421.GA16385@behemoth> <CAFHbX1%2BCerhdfo-VB4dj_JZAkp79b_KD7T0TCxFWTLGFsu-Mpw@mail.gmail.com> <20140407145511.GA16747@behemoth> <alpine.BSF.2.00.1404071656540.9102@mail.fig.ol.no> <20140407153040.GA17668@behemoth>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 7, 2014, at 11:30 AM, Chris Nehren = <cnehren+freebsd-stable@pobox.com> wrote: > On Mon, Apr 07, 2014 at 17:05:32 +0200, Trond Endrest=F8l wrote: >> See: >>=20 >> = http://svnweb.freebsd.org/base/stable/10/cddl/contrib/opensolaris/cmd/zpoo= l/zpool_main.c?view=3Dmarkup#l4992 >>=20 >> Consider this a lesson learned. Yes, I too was bitten by this once,=20= >> but never again. ;-) Luckily, I recovered using a snapshot image. >=20 > 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=20 thing happen. I upgraded a pool and was struck by the fact that I=20 *wasn't* urged to update the boot code and so, after pondering "maybe=20 this means I don't have to" decided not to. Of course, the system=20 wouldn't boot and I had to rescue it via a memstick. I prefer the unconditional warning. :-) Cheers, Paul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C688889-96C0-4B8C-82E7-ACC3FB729FAB>