Known Issues

Before installing FreeNAS™ you should be aware of the following known caveats and issues:

• UPGRADES FROM FREENAS™ 0.7x ARE UNSUPPORTED. The system has no way to import configuration settings from 0.7x versions of FreeNAS™, but the volume importer should be able to handle volumes created with FreeNAS™ 0.7x.

• In a departure from FreeNAS™ 0.7x, the operating system drive can not be used as a component for a volume, nor can it be partitioned for sharing.

• The ZFS upgrade procedure is non-reversible. Do not upgrade your pools unless you are absolutely sure that you'll never want to go back to other systems. There is no reversing a zpool upgrade, and there is no way for a system with an older version of ZFS to access pools that have been upgraded.

• The available space reported in the parent zpool doesn't necessarily reflect reality and can be confusing because the available space represented by datasets or zvols can exceed that of the parent zpool.

• Disks with certain configs can get probed by GEOM and become essentially unwritable without manual intervention. For instance, if you use disks that previously had a gmirror on them, the system may pick that up and the disks will be unavailable until the existing gmirror is stopped and destroyed.

• Some Atom-based systems with Realtek GigE interfaces have functional and performance issues with FreeBSD 8.2.

• USB 3.0 support is disabled by default as it panics some motherboards. To enable support, create a tunable with a variable of xhci_load and a value of YES.

• Hot plugging disks is not supported at this time. Support will be added once FreeBSD commits zfsd.