Beta 2?

[Steiner-SE]

So it's out and me being brand new to TrueNAS (or FreeNAS) not sure I dare applying it yet (got it downloaded).
How safe is the GUI update process? How many have done it yet for this update?
I'm slightly hesitant due to my surprise that there isn't a single mention anywhere about this beta update?

 

[elorimer]

I updated from b1 this morning with no issue.

 

[Alecmascot]

So it's out and me being brand new to TrueNAS (or FreeNAS) not sure I dare applying it yet (got it downloaded).
How safe is the GUI update process? How many have done it yet for this update?
I'm slightly hesitant due to my surprise that there isn't a single mention anywhere about this beta update?

This Beta is only for testing purposes

 

[Kris Moore]

Its announced now, you just caught us in between doing the release stuff :)

 

[Yorick]

Can you speak to edonr? It looks like the feature flag is now in Beta2, and the man page says: "FreeBSD does not support the edonr feature."

So - a pool created elseOS with edonr (for whatever reason) is or is not readable on TrueNAS?

 

[mav@]

As I see, edonr support is still commented out in sources. IIRC there was just no respective algorithm ported to FreeBSD.

 

[Steiner-SE]

Ugh, I ran the update and all seems to have gone well. But now have warning notification for each pool about upgrading each pool due to new feature flags. But I can't find the documentation it refers to.
Anyone have the exact link?

 

[mav@]

If you run `zpool upgrade` without pool specification in command line, it will list you new features that are not enabled for each pool. After that see `man zpool-features` for the description. But I would not recommend you to upgrade pools yet (at least before official release) if there is anything important on the pool, since it is irreversible operation.

 

[Steiner-SE]

If you run `zpool upgrade` without pool specification in command line, it will list you new features that are not enabled for each pool. After that see `man zpool-features` for the description. But I would not recommend you to upgrade pools yet (at least before official release) if there is anything important on the pool, since it is irreversible operation.

As everything works right now I guess I should just ignore those notifications and leave it well alone.
This is all I got:

Some supported features are not enabled on the following pools. Once a
feature is enabled the pool may become incompatible with software
that does not support the feature. See zpool-features(5) for details.

POOL FEATURE
---------------
boot-pool
device_rebuild
pool-a
device_rebuild
pool-b
device_rebuild

 

[Yorick]

Device_rebuild, if I am reading the man page right, is for pools without raidz but with SMR or zoned NVMe. It allows completely sequential (in-LBA-order) resilver, followed by a scrub to fix checksums. It takes longer than a regular healing resilver on “regular” disks, but would be a lot faster on disks that love sequential write (SMR, NVMe).

 

[Steiner-SE]

Device_rebuild, if I am reading the man page right, is for pools without raidz but with SMR or zoned NVMe. It allows completely sequential (in-LBA-order) resilver, followed by a scrub to fix checksums. It takes longer than a regular healing resilver on “regular” disks, but would be a lot faster on disks that love sequential write (SMR, NVMe).

Having neither SMR drives or NVMe I guess I can live without that feature for now. :)