[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensolaris-discuss
Subject:    Re: [osol-discuss] Cannot import a zpool created with zfs-fuse -
From:       Lenz Grimmer <lenz () grimmer ! com>
Date:       2010-07-26 10:37:49
Message-ID: 4C4D657D.6080009 () grimmer ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi Brian,

thanks for your detailed answer! Much appreciated.

On 07/22/10 11:28, Brian Ruthven - Solaris Network Sustaining - Oracle UK wrote:

> What do the outputs of "zpool upgrade" and "zpool upgrade -v" show on
> the opensolaris host?
> 
> The first will give you the current version of the pool on-disk, and the
> second will list what b134 is capable of.

On the Linux box with zfs-fuse I get:

thebe% sudo zpool upgrade mypool
This system is currently running ZFS pool version 23.
thebe% sudo zpool upgrade -v | grep currently
This system is currently running ZFS pool version 23.

On the OpenSolaris box (snv_134):

lenz@kallisto:~> pfexec zpool import mypool
cannot import 'mypool': pool is formatted using a newer ZFS version
lenz@kallisto:~> pfexec zpool import
  pool: mypool
    id: 4510346300987862165
 state: UNAVAIL
status: The pool is formatted using an incompatible version.
action: The pool cannot be imported.  Access the pool on a system running newer
        software, or recreate the pool from backup.
   see: http://www.sun.com/msg/ZFS-8000-A5
config:

        mypool         UNAVAIL  newer version
          mirror-0     ONLINE
            c13t0d0p0  ONLINE
            c12t0d0p0  ONLINE
lenz@kallisto:~> pfexec zpool upgrade -v | grep currently
This system is currently running ZFS pool version 22.

> "zfs upgrade" and "zfs upgrade -v" will do the same for the zfs
> filesystem version, although this seems to change less frequently than
> the zpool version.
> 
> 
> Assuming your problem is truly that the on-disk version is higher than
> that supported by your current snv_134 kernel, and given that zpool and
> zfs versions cannot be downgraded, you're left with 2 options:
>     1) Recreate the pool and restore from backup (you've already said
> you don't want to do this, so...)

I guess that's what I'm going to do, using Mike's suggestions with breaking
the mirror.

>     2) Upgrade OpenSolaris to a later build using the /dev branch.
> 
> However, no dev packages have been released to the IPS repo beyond b134,
> so you have a couple of options  that I can think of:

Right, a "pkg image-update" just tells me that "No updates available for this
image."

>     a) Build the ON gate from source, then use "onu" to upgrade a new BE
> with the freshly built binaries. I believe the Developer's Reference
> Guide gives details on this (see
> http://hub.opensolaris.org/bin/view/Community+Group+on/devref_toc ).
>     b) Upgrade from pre-built packages. http://genunix.org/ may help
> here - I see a note on Jun 14th that Rich Lowe has posted a package
> depot of onnv_142, but your mileage may vary with this.

Thanks! Good to know that these options exist, but I think I will shy away
from them for now - building from source sounds too time-consuming and
error-prone (if you haven't done it before) in comparison to rebuilding the
zpool using an older on-disk format...

Bye,
	LenZ
-- 
  Lenz Grimmer <lenz@grimmer.com> - http://www.lenzg.net/


["signature.asc" (application/pgp-signature)]

_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

[prev in list] [next in list] [prev in thread] [next in thread]