zfs discuss - Sep 2009 - pkg image-update to snv 121 -> shouldn''t ZFS version be upgraded on /rpool

When I check 
--
# pfexec zpool status rpool
  pool: rpool
 state: ONLINE
status: The pool is formatted using an older on-disk format.  The pool can
        still be used, but some features are unavailable.
action: Upgrade the pool using ''zpool upgrade''.  Once this is
done, the
        pool will no longer be accessible on older software versions.
 scrub: none requested
config:

        NAME        STATE     READ WRITE CKSUM
        rpool       ONLINE       0     0     0
          c8t0d0s0  ONLINE       0     0     0

errors: No known data errors
--
Shouldn''t the image-update take care of that ?
And is it safe to do an upgrade ?

/Per
-- 
This message posted from opensolaris.org

>When I check 
>--
># pfexec zpool status rpool
>  pool: rpool
> state: ONLINE
>status: The pool is formatted using an older on-disk format.  The pool can
>        still be used, but some features are unavailable.
>action: Upgrade the pool using ''zpool upgrade''.  Once this
is done, the
>        pool will no longer be accessible on older software versions.
> scrub: none requested
>config:
>
>        NAME        STATE     READ WRITE CKSUM
>        rpool       ONLINE       0     0     0
>          c8t0d0s0  ONLINE       0     0     0
>
>errors: No known data errors
>--
>Shouldn''t the image-update take care of that ?
>And is it safe to do an upgrade ?

No, that would make your other BEs unbootable.

This should really be "automatic"; there needs to be a way where some 
utility can determine what the minimal ZFS version is.

Casper

Per ?berg wrote:
> When I check 
> --
> # pfexec zpool status rpool
>   pool: rpool
>  state: ONLINE
> status: The pool is formatted using an older on-disk format.  The pool can
>         still be used, but some features are unavailable.
> action: Upgrade the pool using ''zpool upgrade''.  Once
this is done, the
>         pool will no longer be accessible on older software versions.
>  scrub: none requested
> config:
> 
>         NAME        STATE     READ WRITE CKSUM
>         rpool       ONLINE       0     0     0
>           c8t0d0s0  ONLINE       0     0     0
> 
> errors: No known data errors
> --
> Shouldn''t the image-update take care of that ?
No. The ''issue'' here is that if you find that the new boot
environment
does not work for you for whatever reason you will need to revert to
the previous environment. However if  you have upgraded the pool
then this will not be possible as the older version of the software
will have no knowledge about the new version.
> And is it safe to do an upgrade ?
As long as you are happy with the new environment.

Thanks
pete
> 
> /Per

Per ?berg wrote:
> When I check 
> --
> # pfexec zpool status rpool
>   pool: rpool
>  state: ONLINE
> status: The pool is formatted using an older on-disk format.  The pool can
>         still be used, but some features are unavailable.
> action: Upgrade the pool using ''zpool upgrade''.  Once
this is done, the
>         pool will no longer be accessible on older software versions.
>  scrub: none requested
> config:
> 
>         NAME        STATE     READ WRITE CKSUM
>         rpool       ONLINE       0     0     0
>           c8t0d0s0  ONLINE       0     0     0
> 
> errors: No known data errors
> --
> Shouldn''t the image-update take care of that ?
Most definitely not.  Upgrading the pool could actually mean you can''t 
boot back into your older BE.
> And is it safe to do an upgrade ?
That depends.

1) Do you actually need to use the features (you get the bug fixes 
regardless) of the newer pool version

2) You have no older BE''s left that you may wish to boot into that
don''t
support the pool version you will be running if you do the upgrade.



-- 
Darren J Moffat

Thanks for all the answers, I''ve now cleared out the old BEs and
upgraded the pools and everything just works as expected.

/Per
-- 
This message posted from opensolaris.org