#Install Mldonkey Freenas install#
#Install Mldonkey Freenas driver#

Install the following packages and their dependencies:.# fuse sources but that would be installed later as a zfs-fuse dependency.ĭpkg-divert -divert /etc/init.d/fuse.no-nfs -rename /etc/init.d/fuseĪpt-get install gawk make gcc linux-headers-2.6-686Īpt-get install devscripts build-essential zlib1g-dev libfuse-dev scons debhelper dpatch xsltproc docbook-xslĭpkg-source -x zfs-fuse_0.4.0~ # install fuse-utils so that can divert a file later provided by Pre-packaged versions of FUSE don’t support NFS, so compile and install FUSE from sources as follows:ĭpkg-divert -divert /lib/modules/`uname -r`/kernel/fs/fuse/fuse.ko.no-nfs -rename /lib/modules/`uname -r`/kernel/fs/fuse/fuse.ko.

other daemons: DHCP, no-ip, dynamic DNS, VMs, NTP, NIS.

filerserver daemons: NFSv3 using kernel-nfs-server with ‘noac’ to prevent ESTALE errors on all clients, Samba, iSCSI target server.

datasets: pub, home, mail, wikis, svnrepos, logs (apache2), p2p (bittorrent, mldonkey, i2p, azureus), iscsi (for VMs) all with individual snapshotting frequencies and retention periods.

FUSE+ZFS+unfs3: although this solves the ESTALE error, it causes programs to hang with waiting for NFS locks which unfs3 does not implement having clients mount with the ‘nolock’ option solves this but when I tried to run programs stored in my home on NFS then I got exec() errors.

FUSE+ZFS+kernel-nfs-server: as documented in /usr/share/doc/fuse/README.NFS, ESTALE errors with kernel NFS, this can be worked around by having clients mount with the ‘noac’ option, but, as documented in nfs(5) this triggers a massive performance hit.

rdiff-backup: storage requirements high.

LVM2: snapshotting speed rapidly degrades.

#Install Mldonkey Freenas driver#

OpenSolaris: assume same driver issues as Nextenta and Belenix.FreeNAS: easily reproducible crashes of rsyncs on ZFS, does not support NIS.Nexenta, Belenix: no driver for my SATA controller card.This procedure has been superceded by Configuring storage services generation two it remains here for reference. The hostname allocated for the system was ‘spirali’.ĭespite being extremely happy with the functionality of the products selected, I was not happy with spirali’s performance, in part due to the old hardware but mostly due to ZFS’s high CPU demands and it running in userspace via the FUSE module.Įventually it was replaced by macaroni, but this page is kept as a record of how I installed it, in the hope that it might be of use to others. This page documents my experience building a ZFS Linux fileserver.