This wasn't supposed to happen, but we fixed so many issues in RC4 that we
really wanted to push something out to the community. That being said we
really wanted this to happen before the weekend, but stuff came up, last
minute bugs, squeezing in that last little bit, and suddenly it's Monday
This image is being handed over to QA for the final run-through. In a perfect
world the release will be this image with polishing work.
Two major bits that are new are volume drive replacement in the GUI, and the
ability to add to ZFS volumes, which also doubles as the ability to create
stacked ZFS volumes, such as a stripe of RAIDZs (RAID 50) or a stripe of
mirrors (RAID 10)
Documentation lags behind the functionality, we'll get it updated shortly.
The release notes have the quick howto.
We've also renamed the images and added a pair of images.
The iso is the same, useful for doing new installs or upgrades when the system
has a optical drive. The old GUI upgrade image has been renamed, and a full
install image has been added, which saves the step of downloading the iso and
extracting it by hand.
Release Notes for FreeNAS 8.0 Release Candidate 5
Release Candidate 5 contains both bug fixes and new functionality over
previous release candidates and betas.
This release candidate is the result of a flurry of bug fixes for issues
noticed by people using RC4, as well as some added functionality. This image
will be handed over to QA to begin preparations for 8.0-Release.
FreeNAS 8 should be installed to a USB stick or Compact Flash device. It
requires a device of at least 1 GB in size. In a departure from FreeNAS 0.7
releases, the OS drive can not be used as a component for a volume, nor can
it be partitioned for sharing.
New in 8.0-RC5:
The ability to create "stacked" ZFS configurations is now present in the GUI.
This also goes hand in hand with the ability to add devices to ZFS volumes.
For ZFS the volume wizard will now accept an existing volume name when adding
volumes. If an existing volume name is specified, the volume being created
will be added to the existing volume as a stripe. In this manner one can
create complex volumes such as RAID 10, RAIDZ+0, RAIDZ2+0, RAIDZ3+0 in the
same manner as conventional RAID controllers build complex volumes. Simply
start with the subgroups and build up from there. The top level group is
implicitly a stripe, there is no provision to build a mirror of mirrors, or a
RAIDZ of mirrors, or a mirror of RAIDZs
Under settings -> config there are now buttons to save, restore, or reset to
defaults for configuration. If you are intending to recreate volumes and wish
to reset to defaults delete the volumes before resetting to factory defaults.
The email settings now contains a "Send Test Email" button. This uses the
saved email settings, it can't be used to test new settings before they are
The GUI contains functionality to replace components in volumes. Mainly
useful for replacing failed drives in arrays, it can handle replacing devices
in place or migrating devices depending on is the new device has the same or a
different device name in it. Due to a bug in FreeBSD's ZFS implementation,
occasionally ZFS will attempt to hold on to the old device. The GUI contains
a detach button for such cases.
Spare, Cache, and Log devices can now be added to ZFS volumes at any time
through the GUI.
Notable bug fixes:
AFP has received more attention. In particular shares are browseable, and
time machine works.
The GUI to select users and groups are far friendlier when the system has
access to large numbers of users and groups.
The email backend supports SSL/TLS properly, and several errors were fixed in
the backend that creates the config file it uses.
Multiple VLANs with the same parent were not being started properly, in
addition using a lagg device as a VLAN parent was not not working properly.
Active Directory now starts up properly after rebooting the system.
Setting the GUI to HTTPS now persists on reboot.
The iSCSI Target software does not properly present multiple LUNs per target
to initiators. For the best results use one target per LUN.
Disks with certain configs can get get probed by geom and become essentially
unwritable without manual intervention. For instance, if you use disks that
have previously had a geom_mirror on them the system may pick that up and
the disks will be unavailable until the existing gmirror is stopped and
UPGRADES FROM FREENAS 0.7x ARE UNSUPPORTED
The system has no way to import configuration settings from 0.7 versions
of FreeNAS, but the volume importer should handle volumes created with FreeNAS
0.7. Please note that zpool upgrade is a one way street, and upgraded volumes
will not be usable with FreeNAS 0.7.x
Usability of this Release Candidate:
At this point the feature set of FreeNAS 8 is complete enough to perform file
sharing tasks via NFS or Samba, using local users, AD, or LDAP, as well as
allowing the system to operate as an iSCSI target. The base technology of
FreeBSD, ZFS, Samba, and NFS is very stable and very well tested. While there
isn't an upgrade path from other storage solutions, including previous FreeNAS
0.7 releases, the system is suitable for new deployments provided the
feature set is a good match for the requirements.
A note about versions:
There's been a huge jump in version numbers. The intention is to have the
version number reflect the base version of FreeBSD used. This RC is based
on FreeBSD 8.2, but this version of FreeNAS is called 8.0 as there are future
plans to add functionality that will get the versions caught up. Once
FreeNAS 8.2 is out, a suffix will be added, such as 8.2.1, 8.2.2, etc.
A note about filesystem technologies:
While this system does support UFS based volumes, such as gmirror, gstripe,
graid3, the primary focus is on ZFS. Many of the features are provided via
ZFS datasets, such as the ability to share subsets of volumes via CIFS.
This delta is likely to increase over time, the compelling reasons to use
ZFS are likely to increase as well. It is highly recommended to use ZFS
for new volumes, even if the underlying device is a volume exported by a
hardware RAID controller.
The following two upgrade images are available for versions of FreeNAS 8 that
have GUI upgrade capability.
New installs can be done by using a bootable ISO or by writing an image to a
bootable device directly.
Director of IT, iXsystems
Servers For Open Source http://www.ixsystems.com