FreeNAS 8.3.0-BETA1 is now available

[jpaetzel]

The FreeNAS development team is pleased to announce the availability
of FreeNAS 8.3.0-BETA1. This is the first public release of the
8.3.0 branch of FreeNAS, which upgrades the underlying base system
of FreeNAS to FreeBSD 8.3-RELEASE-p7. This update brings with it
Version 28 of the ZFS filesystem, as well as a number of updates to
the drivers and utilities in the base system.

FreeNAS 8.3.0-BETA1 can be downloaded from the following location:

https://sourceforge.net/projects/freenas/files/FreeNAS-8.3.0/BETA1/

FreeNAS 8.2.0 brought with it the ability to install plugins, this
functionality is present in FreeNAS 8.3.0 as well. At the moment upgrading
the plugin jail to the version included with FreeNAS 8.3.0-BETA1 will cause
plugins to stop working and will require reinstallation and reconfiguration
of all plugins to resume normal operation. Our recommendation at this time
is to avoid upgrading working components of the plugin system.

ZFS Version 28 includes several features such as the ability to detach a
dedicated ZIL device, triple parity RAIDZ, and deduplication. There are
numerous caveats to using deduplication, please do some research into the
possible caveats of using dedup before enabling it.

Upgrading an existing ZFS pool is a one way street, once the upgrade is
done it is not possible to use older versions of FreeNAS, nor is it possible
to downgrade your pool. This upgrade can be done by running zpool upgrade
from the CLI, it is not done automatically via the upgrader, nor is there a
way to do the upgrade from the GUI.

 

[eltoro]

Nice work!

 

[noee]

... to FreeBSD 8.3-RELEASE-p7.

Did you mean P4? 12061-x64, dmesg shows:

 

[Daisuke]

Thank you for your great work guys, much appreciated.
It is unfortunate that we do not have the ability to increment the number of disks into an existing vdev. It would make ZFS the ultimate solution. Thinking out loud, when my current 8TB vdev will be full (already half way there), I will have to build a new system from scratch instead of adding extra disks to current setup and increase the size of current array. May goal is not to have multiple vdev's, but rather extend the the existing one.

Are there any plans to implement a solution for the above mentioned setup?

 

[ben]

Thank you for your great work guys, much appreciated.
It is unfortunate that we do not have the ability to increment the number of disks into an existing vdev. It would make ZFS the ultimate solution.

This is something that would have to happen far above the FreeNAS level, probably a project in collaboration between Illumos/OpenIndiana and FreeBSD.

 

[Ismael Duarte]

Working OK here.
Just a small and perhaps not new idea! Why not an auto-update for freenas?

 

[Daisuke]

One simple tweak I would suggest for 8.3.0: implement a redirect to https, if SSL is enabled into FreeNAS. This is extremely easy to achieve with Nginx. :)
So if I use http://192.168.1.2/, it should automatically redirect me to https://192.168.1.2/

 

[Brand]

One simple tweak I would suggest for 8.3.0: implement a redirect to https, if SSL is enabled into FreeNAS. This is extremely easy to achieve with Nginx. :)
So if I use http://192.168.1.2/, it should automatically redirect me to https://192.168.1.2/

Already asked for over a year ago. It would appear that this simple request is not considered important enough to the developers.

Auto redirect HTTP to HTTPS

 

[noee]

Is there a request ticket for that mod?

 

[cyberjock]

Working OK here.
Just a small and perhaps not new idea! Why not an auto-update for freenas?

One of the oldest FreeNAS tickets currently open asks for this exact feature. It would be very nice to have, but is probably difficult to implement easily. My guess is it's backburnered right now to due to other higher priority items.

 

[Daisuke]

Already asked for over a year ago. It would appear that this simple request is not considered important enough to the developers.

That's like 3 lines of code in Nginx configuration, really.

 

[paleoN]

That's like 3 lines of code in Nginx configuration, really.

TECK can you open a ticket and submit the 3 lines of code? Maybe that will be enough of a push to get them to include it.

 

[freshfeesh]

Will 8.2 be maintained (bug & security fixes, backporting new features where possible, etc.)? jpaetzel mentioned ealier that zfs v28 FreeNAS 8.3) will be slower than zfs v14 (FreeNAS 8.2). My FreeNAS system uses hand-me-down hardware as I that's all I can afford, and is slow enough as it is.

 

[Stephens]

You don't have to upgrade your ZFS pool to v28 to upgrade to FreeNAS 8.3. The ZFS v28 upgrade is something you have to manually (and consciously) do from the shell.

 

[freshfeesh]

Good to know, thanks. I know that the focus of freenas has tilted in a more serious direction from people tinkering in their garage with spare parts, like me (although I use it seriously), but thinking about the next pool I'll need to make, it would be great to get more insight into the nature of the performance hit (or would I be able to create v14 pools in 8.3 as well? My box has a relative glut of processor power and a dearth of RAM, so if it's just extra computation thats required, I'm all in.

 

[Joshua Parker Ruehlig]

thanks guys, excited to see if my raid card works natively in 8.3 (without having to add a driver).

 

[Daisuke]

TECK can you open a ticket and submit the 3 lines of code? Maybe that will be enough of a push to get them to include it.

Done. Can we change the link color into forums? I don't see any difference from the "Done" link I just made and regular text next to it. Is funny, you created your own underline to make it visible as link... Maybe FreeNAS forum mods should test those things before deploying some unreadable theme?

 

[Daisuke]

thanks guys, excited to see if my raid card works natively in 8.3 (without having to add a driver).

What model is that? Is important to post those things, a list with working hardware is maintained on forums. Visit the thread and post your info.

 

[Daisuke]

TECK can you open a ticket and submit the 3 lines of code? Maybe that will be enough of a push to get them to include it.

Wow, the fix I proposed was accepted and implemented, hats off to devs!
http://support.freenas.org/ticket/1718

 

[freibuis]

ok Panic when I boot from the ISO.
panic: m_getzone: m_get jcl: invalid cluster type

I think its the intel IGB driver thats included.

I really was hoping this would work to get this dam intel dual I-350T to work :(

Pull the card out and the machine boots the cd all ok...


just lettting ppl know not to upgrade if they have the new intel I-350T's I have tested this on a few machines and they all panic: m_getzone: m_get jcl: invalid cluster type