Log in

No account? Create an account

Fri, Jun. 5th, 2009, 01:46 am

So let's see if I have this straight:

Solaris: ZFS. Less power management. UPnP media servers act weird. Power draw with one spun-down hard drive: 50 W. Needs 2 GB of memory for ZFS not to do weird things (like pause rsyncs while writing).

Linux: No ZFS. 35 W power draw, one hard drive spun down. 512 MB of memory is probably sufficient.

FreeBSD: ZFS, but it's experimental.

ESXi, Linux + Solaris: 46 W power draw (no hard drive spindown capability, so that 46 W is with one spinning platter, and my full setup would probably be at least 62 W). Needs more memory (= more power consumed).

Linux + Solaris in VMware Server: No idea how it cooperates with power management, because you can't export raw devices in VMware Server.


Fri, Jun. 5th, 2009 06:50 pm (UTC)

Why no ZFS in Linux? Shit is like four years old.

Fri, Jun. 5th, 2009 10:28 pm (UTC)

Licensing issues. The Linux kernel is under the GPL while ZFS is under Sun's CDDL, and the two licenses are incompatible. So you can't just copy the code over. There is a project to port ZFS to Linux FUSE (userspace filesystem driver, basically), but it seems to be in limbo now.

There's a filesystem in development for Linux called btrfs. It's supposed to copy or reimplement many (but not all) of ZFS's features. But it seems to be a long way off still.