I wrote up a guide: https://github.com/hughobrien/zfs-remote-mirror
I wrote up a guide: https://github.com/hughobrien/zfs-remote-mirror
1GB is the recommended conf for ZFS on FreeBSD, it will benefit from more (and may need some tuning below 2GB) but even that's not a requirement, the FreeBSD wiki's ZFS tuning page quotes "ZFS running nicely on a laptop with 768 Megs of physical RAM" with tuning (and provides configuration values).
Sooner or later you will trash your data unless you're using ECC memory (which the Raspberry Pi RAM chips are not): http://louwrentius.com/please-use-zfs-with-ecc-memory.html
For the record, I also think it's cool to get this compiled and running on RasPi; just wanted to add the ECC info for anyone now thinking of doing something with this in production :-D.
There's nothing special about ZFS that requires/encourages the use
of ECC RAM more so than any other filesystem. [...] I would simply
say: if you love your data, use ECC RAM. Additionally, use a
filesystem that checksums your data, such as ZFS.
[0] http://arstechnica.com/civis/viewtopic.php?f=2&t=1235679&p=2...Since I had difficulties compiling the zfs (and one other, which I don't recall) module, I'm wondering if you'd care to share your experience in your guide?
Kudos to your very well thoughtout and thorough guide.
It compiled with zfs and all fine though :)
You're probably thinking of the opensolaris module. There's a small patch to apply and some KERNCONF to trigger the module build but otherwise its straightforward -- once you know where to look!