Warnings after upgrade to 9.2.0.1 - Shigawire (revision 925)

[spammeatwill]

Hi,

I have recently upgraded my system to 9.2.0.1 - Shigawire (revision 925) and now I am getting these warnings on my pools:

status: The pool is formatted using a legacy 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 software that does not support feature
flags.

Is it safe to upgrade the pool?
Or should I leave it alone?

Thanks.

[chrisf4lc0n]

You can easily upgrade the pool using the webGUI or shell and it is safe!

[alexey123]

Hi,

I have recently upgraded my system to 9.2.0.1 - Shigawire (revision 925) and now I am getting these warnings on my pools:

status: The pool is formatted using a legacy 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 software that does not support feature
flags.

Is it safe to upgrade the pool?
Or should I leave it alone?

Thanks.

Hi
Before upgrade pools check compatibility for your hardware.

[raulfg3]

Is it safe to upgrade the pool?
Or should I leave it alone?

it's safe, but you need to read about ZFS v5000 and only upgrade if you are totally sure that DO NOT need to revert to ZFS v28.

[berander]

I went from 9.1.0.1 - Sandstorm (revision 847) to 925 ad lost my JBOD. The disks were unrecognizable and suggestion was to reformat & rebuild a new JBOD. That wasn't really what I had in mind and fortunately enough a downgrade got my JBOD back and up running

I really don't have a problem scrubbing my JBOD (4 old SATA-disks) since I actually do need to swap some of them to bigger ones I gotten my hands on, but I'd like to do it when i choose to, and not because a frickin' upgrade won't recognize them :S

Yours // Johan, Sweden

[raulfg3]

I went from 9.1.0.1 - Sandstorm (revision 847) to 925 ad lost my JBOD. The disks were unrecognizable and suggestion was to reformat & rebuild a new JBOD. That wasn't really what I had in mind and fortunately enough a downgrade got my JBOD back and up running

I don't find this post, please can you post a link to study your case?, perhaps your JOBD are not a ZFS pool so not affeted by ZFS upgrade from V28 to v5000?

[spammeatwill]

Hi guys,

Thank you for sharing your thoughts. I would appreciate some pointers to documentation on ZFS v5000, particularly about the upgrade risks.
My zpools were created in N4F itself (on 9.1.0.1 - Sandstorm (revision 847)) so I was expecting a painless operation.
But now I am worried that I may loose data.. and backing it up will take ages, I still have a lot to work in front of me (thinking on replication to a remote office)

[spammeatwill]

Ok, so this was smooth and I don't see any troubles after upgrading the zpool.
I still have the reboot test to check everything is fine, bu I am comfident.
Thanks!

[RedAntz]

It's great to know that it went well for you.

Thanks for reporting back.