ZFS

From FnordWiki
Revision as of 18:40, 5 March 2014 by Adj (talk | contribs) (Created page with "So ZFS is all shiny and stuff. We'll be using it for disk based storage of backups for the following reasons: * All data (and metadata) can be validated with cryptographicall...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

So ZFS is all shiny and stuff. We'll be using it for disk based storage of backups for the following reasons:

  • All data (and metadata) can be validated with cryptographically strong hashes
  • Data deduplication

Released versions of ZFSonLinux do not work on the kernels I'm running (3.12.x from backports.org), so I'm playing with zfs-fuse instead.

So, here's the first annoying thing I've come across. The ZFS tools go off and automatically mount filesystems in your just-created pool. And they go and make directories to mount those filesystems on. Quite annoying. What's wrong with putting entries in /etc/fstab and typing mkdir /foo? Instead zfs pool create solarissucksballs ... will create a /solarissucksballs directory on your machine and mount the new pool's filesystem there. I'm sure this behavior comes from Solaris, but I find it quite obnoxious.