Development

FreeNAS 0.7: powerful and not dead

December 17, 2009

This article was contributed by Koen Vervloesem

Recently, the FreeNAS developers have released version 0.7 of their FreeBSD-based operating system for network-attached storage (NAS). This is a major release, which introduces support for the ZFS file system among other things. Around the same time, fears were expressed about the future of FreeNAS as a BSD-based NAS but, in the end, a solution has been found.

FreeNAS 0.7 is based on FreeBSD 7.2 and includes a lot of file sharing protocols. This way it can talk to all major operating systems: GNU/Linux, the BSDs, Windows, and Mac OS X. FreeNAS also supports several types of media streaming protocols and can act like an iTunes server. In addition, it supports iSCSI and different levels of software RAID. All of this can be managed from the web interface so users don't have to know the FreeBSD commands under the hood.

One of the advantages of FreeNAS is that it has very low system requirements, as it needs only 128 MB of RAM. This makes it attractive to blow the dust off an old Pentium 2 or 3 PC, put a couple of hard drives in it and make it a NAS. Of course, for high performance the machine still needs enough RAM and CPU horsepower. All of this makes FreeNAS a popular operating system for central storage and media streaming at home.

Installation

FreeNAS has downloads for 32-bit and 64-bit hardware, in a live version and an installable version. The installable version is for installation on a USB stick, hard drive, or Compact Flash card, while the live version doesn't touch the hard drive of the system but can save its configuration to a USB stick or floppy disk.

After the installer has booted, it shows the user a simple menu in the console to set up the basics. The user can assign network interfaces, set IP addresses, reset the password for the web interface or reset all settings to the factory defaults, open a shell, reboot or shutdown the system, and install or upgrade FreeNAS to a hard drive or USB stick. Most of that is just for troubleshooting, because the bulk of the settings are available in the web interface.

Configuration

Once FreeNAS has been assigned an IP address, the user can surf to the web interface in a browser and log in with the default user name and password. The first thing FreeNAS displays is some system information, such as the CPU and memory usage, the load averages and the disk space usage. The latter will show "No disk configured" first, but available disks can be added easily in the "Disks -> Management" menu by clicking on the plus icon, choosing the disk, and entering some optional settings. After this, don't forget to click on "Apply changes" on the disk management page. The next steps are formatting and choosing a mount point.

When choosing a file system for a hard drive in the "Disks -> Format" menu, FreeNAS recommends the BSD file system UFS. Other supported file systems are FAT32, NTFS, Ext2, or Ext3, but the web interface expressly warns that they can result in unpredictable results. While the web interface doesn't warn against using ZFS (which has its own menu item, because it is not only a file system but also a logical volume manager), users have to keep in mind that FreeNAS 0.7 is still based on FreeBSD 7.2 which calls ZFS support "experimental".

The goal of a NAS if of course sharing the data with users, and FreeNAS has a lot of services at its disposal to do this: FTP, TFTP, NFS, Samba, AFP (for Mac OS X users), HTTP, rsync (ideal for making backups on the NAS) and Unison (for file synchronization). It can also share a disk as an iSCSI target to another computer in the local network. But FreeNAS can also act as a streaming media server for clients that are compatible with UPnP (Universal Plug and Play) or iTunes, or it can run BitTorrent to download torrents directly on the NAS.

In general, the web interface is intuitive enough to do a lot of things without having to look up the documentation. At the same time, it is really powerful, with even the possibility to edit arbitrary files, run arbitrary commands, tune some FreeBSD kernel parameters with sysctl or add variables to rc.conf. It also shows a lot of status information. Unfortunately, documentation such as the FreeNAS Setup and User Guide is still lagging behind.

Death of a FreeBSD descendant?

During the last few months, the future of the FreeNAS project seemed in peril. The project's core developer Volker Theile announced in September that he would stop developing FreeNAS and switch his work to a new project, called CoreNAS, which would be based on Debian GNU/Linux. Some reasons he listed for this switch are:

The Debian installer is more customizable than the hand-written FreeNAS install scripts.
Wake-on-LAN for waking up the NAS automatically works in Linux.
Linux has a working sensor framework to check the temperature and fan speeds.
The system can be updated with the Debian package manager.
Linux has better driver support.

According to Volker, the current architecture of FreeNAS is not flexible enough to add the new features users have been asking him for:

Some months ago I started to upgrade FreeNAS to FBSD8.0. I also thought about how to remove all these limitations of the previous versions to make it more enhanceable. The more I thought about it the more I came to the conclusion that it will be necessary to reimplement everything to get rid of these limitations.

His eye fell quickly on the Debian infrastructure, which seemed to reduce the work to get a new FreeNAS to a minimum. A big plus of Linux is that it supports more new hardware than FreeBSD.

But of course this left FreeNAS users with a problem: what about the ZFS support that has been added in FreeNAS 0.7? A lot of the new users were attracted solely by this feature, which didn't seem to have a future in CoreNAS. Would they have to migrate their freshly installed data to another file system in the next release? Volker wrote that his FreeNAS successor would maybe have ZFS over FUSE, but the performance would of course not be the same. So the only real option users of ZFS on FreeNAS seemed to have was to migrate to an OpenSolaris-based NAS operating system such as EON or Nexenta Core Platform. However, these don't have the intuitive web interface that FreeNAS has (NexentaStor, the commercial and proprietary variant of Nexenta Core Platform, has one, and a 4 TB developer license is free as in beer).

Rumors of FreeNAS' death greatly exaggerated

But then in the beginning of December, FreeNAS founder Olivier Cochard-Labbé appeared deus ex machina. He agreed with Volker that a full rewrite of the FreeNAS base is needed, and he clarified that this will happen along two different paths. On the one hand, Volker will develop his Linux-based CoreNAS idea in a new project, OpenMediaVault (the website is empty at the moment). On the other hand, the company iXsystems will take on FreeNAS development and rewrite it. As part of this, Olivier will work on upgrading it to the FreeBSD 8.0 code base, which will introduce production-ready ZFS support.

Matt Olander, the Chief Technology Officer at iXsystems and also a member of the FreeBSD and PC-BSD projects, officially joined the FreeNAS project with some explanation on the forum:

We have been using FreeNAS at iX for quite some time and we're really happy with it! We just had a developer meeting with our FreeBSD development team and everyone can't wait to get started digging into the next version! We are very interested in improving the embedded platform with continued development of FreeNAS and ZFS. We're considering package management and GUI enhancements so that the product only shows the functionality desired and needed while allowing the user to extend as necessary both through the UI and via the backend.

Matt added that iXsystems will start digging through the forums and search some low hanging fruit to implement in the first future release of FreeNAS, an upgrade to FreeBSD 8.

So, in the end, a crisis has been averted and, with luck, everyone will be happy. The users that have been attracted to FreeNAS because of ZFS can keep using it and will get an update. In addition, they get commercial backing by iXsystems. The users that have been asking for features such as Wake-on-LAN, a sensor framework, and more hardware support get their rewrite to Linux, done by Volker in his spare time. Let's hope that FreeNAS and OpenMediaVault keep working together to share their efforts.

Comments (14 posted)

The Free Firewire Audio Drivers reach version 2.0

By Forrest Cook
December 22, 2009

The FFADO (Free FireWire Audio Drivers) project supports the connection of FireWire-based audio devices to Linux systems:

The FFADO project aims to provide a generic, open-source solution for the support of FireWire based audio devices for the Linux platform. It is the successor of the FreeBoB project. FFADO is a volunteer-based community effort, trying to provide Linux with at least the same level of functionality that is present on the other operating systems.

The About FFADO document describes the wide goals of the project:

We try to support any FireWire device available out there. The FFADO codebase is a framework that has been built with this in mind. This however doesn't mean that all FireWire devices work with FFADO. In order to support a device, we need cooperation from manufacturers, or somebody that want's to reverse engineer the protocol. Luckily we have support from the manufacturers of the three major platforms vendors build their devices around (BridgeCo, TC Applied Technologies and ECHO). The exact devices supported (or not supported) can be found on our device list.

The online FFADO Manual and FAQ are somewhat out of date, the documentation recommends visiting the wiki for the most recent information. FFADO's roots can be traced to this paper [PDF] entitled FireWire (Pro-)Audio for Linux which was presented at the 2007 Linux Audio Conference by Pieter Palmers.

Digging through the documentation reveals some of the FFADO features including:

Supports FireWire audio interfaces, MIDI devices, control surfaces and more.
The Device List and Usage By Device documents show many supported devices.
Works together with the JACK audio connection kit and the Ardour multi-track audio workstation.
Requires the Linux kernel version 2.6.21 or later.
Uses the raw1394 kernel module.
Supports up to four devices per IEEE-1394 controller.

FFADO support is relatively new, it showed up in the Ubuntu Studio 9.04 distribution (April, 2009) and first worked with JACK 0.109.0 and QjackCtl 0.3.2.

Version 2.0 of FFADO was announced on December 19, 2009, this version of the software has been in the release candidate state for over a year with FFADO 2.0 release candidate 2 arriving on May 17, 2009 and FFADO 2.0 release candidate 1 arriving on November 23, 2008.

From the release announcement:

As the release candidates have been around for almost one year now without a significant amount of bug reports we feel confident that the current code-base has matured. Around the end of november the 1000-th device was registered as being used with FFADO, which seemed to be a nice number to triggered the release. Furthermore on December 2 the Linux kernel version 2.6.32 has been released. This version fixes the new kernel FireWire drivers such that they are compatible with FFADO. So once the distributions pick up this kernel the old/new kernel stack confusion should be history.

The announcement also hints at what's to come in upcoming FFADO releases:

Looking ahead to the 2.1 release we can announce that we have implemented (basic) support for additional devices from Focusrite, Behringer, Stanton and TC Electronic. We plan to move to beta-testing 2.1 fairly soon as development on it has been ongoing for more than a year now. Additionally, work is being done on the RME devices, but its not yet known when that will be finished. Support for some other vendors is in the pipeline, so stay tuned for more announcements. A second major development is the move of the streaming infrastructure to kernel space. A kernel-space implementation will bring significant improvements with respect to reliability and efficiency. Furthermore it will allow to expose an ALSA interface, meaning that the scope of FireWire audio on Linux is extended significantly.

Through its relatively short history, FFADO seems to be evolving, becoming more generic and including support for an ever-growing list of FireWire devices. FFADO will allow Linux users to tap into a wide range of useful devices, increasing the functionality of Linux-powered audio workstations. Congratulations go out to the developers for their hard work.

Comments (none posted)

System Applications

Audio Projects

ALSA 1.0.22 released

Version 1.0.22 of ALSA has been announced. "The changes are listed in this URL: http://www.alsa-project.org/main/index.php/Changes_v1.0.2..."

Development

Installation

Configuration

Death of a FreeBSD descendant?

Rumors of FreeNAS' death greatly exaggerated

System Applications

Audio Projects

Database Software

Networking Tools

Virtualization Software

Web Site Development

Miscellaneous

Desktop Applications

Audio Applications

Desktop Environments

Encryption Software

Interoperability

Mail Clients

Music Applications

Office Applications

Office Suites

Digital Photography

Video Applications

Languages and Tools

Caml

Perl

PHP

Python

Debuggers

Version Control

Miscellaneous