Actual state of FreeNAS development

Written by admin on .

Right at the moment we had some problems with systems running >= 2GB RAM. It is not possible to boot FreeNAS on this systems. To solve the problem the current workaround is to reduce RAM to 1GB. I will keep an eye on this problem.

ZFS integration has been done in 0.7, so it is possible to create pools and datasets via WebGUI. The integration of ZFS is not really seamless because of the new workflow ZFS uses, e.g. it is not necessary to mount the disks manually as it has to be done when using ‘normal’ disks/filesystems.

Till 0.69/0.7 revision 3468 the following changes has been done:
– Included access restrictions WebGUI for mount points, so it is possible to define access rights for each mount point.

– Removed ACPI in kernel, using kernel module instead. Hopefully this will fix misc problems on some systems that do not like ACPI.

– LiveCD creation scripts has been improved, maybe this will also fix some boot problems on misc systems.

– VLAN and LAGG support has been included

– WLAN WEP/WPA should work now

Actual state of FreeNAS 0.7

Written by admin on .

The migration to FreeBSD 7.0 was more easy that planned.
I’ve still one problem to solve with the circular log rotating patch, but it’s works…
Now I’m working on migrating the internal configuration of disk/geom volume: I will use the idea of Volker for storing real disk and geom drive.
Here is the actual state:

  1. Migrate to FreeBSD 7.0: 80% done (need to fix the clog problem and adapt iSCSI initiator that is now include in FreeBSD)
  2. Migrate the internal disk/geom management and config file: 40% done (lot’s of internals function to change)
  3. Review all the disk/mount point management WebGUI: 0%
  4. Adding gjournal, ZFS and gvistor: 0%

Here is an idea about the new approach of manasge disk/geom class :

  1. Disk: This mandatory step will permit to add a physical disk (ATA, SCSI and HW RAID) and to choose use it directly (by formatting or keeping existing data) or to put it in a «available pool». If the user choose to use it directly, the disk will be formatted and mounted (the mount part will be transparent to the user: no more «mount» page)
  2. Virtual disk (or other name… need to define): This optionnal step will permit to create graid5, geli,gstripe, ZFS, etc…. using the disks in the «available pool», and propose to use this new virtual disk directly or to re-put the virtual disk to the «available pool» (for creating encrypted graid5 volume, or RAID 1+0, or any combinaison you want).
  3. Share: This mandatory step will permit to create a share on a selected disk and to set user/group permission and quotas on it (this step will transparently create a directory on choosen disk).