Date: Mon, 5 Aug 2013 12:20:15 -0700 From: Tim Gustafson <tjg@ucsc.edu> To: freebsd-fs@freebsd.org Subject: Re: ZFS: unsupported ZFS version 5000 (should be 28) Message-ID: <CAPyBAS4%2BdGcff9%2BcZyC=eN2dQCCVidr-TD4KFcFn%2Bah62M_U8w@mail.gmail.com> In-Reply-To: <CA%2B7WWSetkTX8rujzcSucZH%2B5utUh168rA-nACLP_bNH8Fr6rMQ@mail.gmail.com> References: <CAPyBAS6Sf-5-HF%2BVGGZN1bp2Q2YebF5=Aw_Qj0OTED8oppk6SA@mail.gmail.com> <CAOFF%2BZ2ff8%2BwPQBR6YM2n9vX8qsZoq_VWXVHFKXB5qWp11Hddg@mail.gmail.com> <CAPyBAS4ELa_w7Zm3JKcrqH9EvohRP6%2BMOuqDc3p9i=i1gdPpjg@mail.gmail.com> <CAPyBAS5ekywBiTdoANt4pCLMknURKFp3mLK2e5tXNpW5FQejSQ@mail.gmail.com> <51FBC806.3070500@egr.msu.edu> <CAPyBAS7QVfTdB1WwyQZDy_v1MYfiF8eRHzjzHJeAL6AVNFuAMA@mail.gmail.com> <CAFHbX1%2Bgnunh=gWrvyqiyvchfJVM-7heWhhRKHas-9hYaZ8vwg@mail.gmail.com> <CAPyBAS7E%2B6fxat6kARcYka1CQX-yCU=Y87K-03H%2Bwp_nhpXv7w@mail.gmail.com> <CA%2B7WWSetkTX8rujzcSucZH%2B5utUh168rA-nACLP_bNH8Fr6rMQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I wanted to report back to the group about how I was able to get past this problem. A quick re-cap of what happened: - A few weeks ago, we upgraded from 8.2 to 8.4 using the Subversion repository at http://svn.freebsd.org/base/releng/8.4 - On Thursday last week, I fat-fingered a command that caused /usr to be dismounted - I rebooted into single-user mode, fixed /usr, and rebooted successfully back into multi-user mode - Just to make sure that nothing in /usr got clobbered, I did a "make buildworld buildkernel installkernel installworld" - Upon rebooting after the buildworld procedure, the system reported that the zpool version (5000/28) was too new So, somehow among all that, the zpool got upgraded to a new version. I'm not sure how that's possible, given that at no time were we running a beta version of any OS up to this point. Reinstalling the bootcode (ala "gpart bootcode") from either the compiled sources or a 9.2-BETA CD didn't help because /boot/loader did not support the newer version. I actually needed to upgrade the box to 9.2-BETA in order to get a version of /boot/loader that could see the zpool correctly. So I'm running on 9.2-BETA now, and everything seems OK. I'm not thrilled that we're running a beta OS version on a production machine, but I see no other way unless I rebuild the zpool, which I don't want to do. This is several terabytes of data and includes a lot of snapshots that have to be preserved, and therefore rsync won't do, and zfs send/receive would preserve the incorrect zpool version (if I understand things correctly). So, is there *any* way at all that someone accidentally committed something to releng/8.4 that should have been committed to stable/8 instead? -- Tim Gustafson tjg@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyBAS4%2BdGcff9%2BcZyC=eN2dQCCVidr-TD4KFcFn%2Bah62M_U8w>