ZFS - Revision history

Adj: /* Some useful tidbits */

2016-02-06T22:39:52Z

Some useful tidbits

← Older revision		Revision as of 22:39, 6 February 2016
Line 14:		Line 14:
	* <code>zfs set dedup=sha256,verify ''poolname''</code> # enable dedupe, use SHA256 hashes as keys, but also do a bit-by-bit comparison before deciding two blocks are the same		* <code>zfs set dedup=sha256,verify ''poolname''</code> # enable dedupe, use SHA256 hashes as keys, but also do a bit-by-bit comparison before deciding two blocks are the same
	* <code>zfs set canmount=noauto ''poolname_OR_fsname''</code> # gets rid of the obnoxious /etc/fstab-less mounting behaviour at ZFS start time.		* <code>zfs set canmount=noauto ''poolname_OR_fsname''</code> # gets rid of the obnoxious /etc/fstab-less mounting behaviour at ZFS start time.
			* <code>zfs set mountpoint=legacy ''poolname_OR_fsname''</code> # indicates that mounting based /etc/fstab entries is preferred for this one

Adj at 16:24, 7 August 2014

2014-08-07T16:24:56Z

← Older revision		Revision as of 16:24, 7 August 2014
Line 3:		Line 3:
	* Data deduplication		* Data deduplication

	Released versions of [http://www.zfsonlinux.org ZFSonLinux] do not work on the kernels I'm running (3.12.x from backports.org), so I'm playing with [https://packages.debian.org/search?keywords=zfs-fuse zfs-fuse] instead.		Released versions of [http://www.zfsonlinux.org ZFSonLinux] do not work on the kernels I'm running (3.12.x from backports.org), so I'm playing with [https://packages.debian.org/search?keywords=zfs-fuse zfs-fuse] instead. ''[This is out of date. The ZFSonLinux packages have been working for a few months as this update is written.]''

	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 <code>/etc/fstab</code> and typing '''<code>mkdir /foo</code>'''? Instead '''<code>zfs pool create solarissucksballs ...</code>''' will create a <code>/solarissucksballs</code> directory on your machine and mount the new pool's filesystem there. ZFS on Solaris works this way, too. It's quite obnoxious.		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 <code>/etc/fstab</code> and typing '''<code>mkdir /foo</code>'''? Instead '''<code>zfs pool create solarissucksballs ...</code>''' will create a <code>/solarissucksballs</code> directory on your machine and mount the new pool's filesystem there. ZFS on Solaris works this way, too. It's quite obnoxious.

Adj at 20:09, 6 August 2014

2014-08-06T20:09:46Z

← Older revision		Revision as of 20:09, 6 August 2014
Line 5:		Line 5:
	Released versions of [http://www.zfsonlinux.org ZFSonLinux] do not work on the kernels I'm running (3.12.x from backports.org), so I'm playing with [https://packages.debian.org/search?keywords=zfs-fuse zfs-fuse] instead.		Released versions of [http://www.zfsonlinux.org ZFSonLinux] do not work on the kernels I'm running (3.12.x from backports.org), so I'm playing with [https://packages.debian.org/search?keywords=zfs-fuse 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 <code>/etc/fstab</code> and typing '''<code>mkdir /foo</code>'''? Instead '''<code>zfs pool create solarissucksballs ...</code>''' will create a <code>/solarissucksballs</code> 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.		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 <code>/etc/fstab</code> and typing '''<code>mkdir /foo</code>'''? Instead '''<code>zfs pool create solarissucksballs ...</code>''' will create a <code>/solarissucksballs</code> directory on your machine and mount the new pool's filesystem there. ZFS on Solaris works this way, too. It's quite obnoxious.

			== Getting ZFSonLinux on Debian wheezy with backport kernels ==
			Follow the directions at http://zfsonlinux.org/debian.html and bam, you're done.

	== Some useful tidbits ==		== Some useful tidbits ==

Adj at 21:56, 5 March 2014

2014-03-05T21:56:39Z

← Older revision		Revision as of 21:56, 5 March 2014
Line 6:		Line 6:

	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 <code>/etc/fstab</code> and typing '''<code>mkdir /foo</code>'''? Instead '''<code>zfs pool create solarissucksballs ...</code>''' will create a <code>/solarissucksballs</code> 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.		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 <code>/etc/fstab</code> and typing '''<code>mkdir /foo</code>'''? Instead '''<code>zfs pool create solarissucksballs ...</code>''' will create a <code>/solarissucksballs</code> 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.

			== Some useful tidbits ==
			* <code>zfs set checksum=sha256 ''poolname''</code> # changes a filesystem's data integrity check algorithm from the default Fletcher4 to SHA256.
			* <code>zfs set dedup=sha256,verify ''poolname''</code> # enable dedupe, use SHA256 hashes as keys, but also do a bit-by-bit comparison before deciding two blocks are the same
			* <code>zfs set canmount=noauto ''poolname_OR_fsname''</code> # gets rid of the obnoxious /etc/fstab-less mounting behaviour at ZFS start time.

Adj: 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..."

2014-03-05T18:40:58Z

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..."

New page

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 [http://www.zfsonlinux.org ZFSonLinux] do not work on the kernels I'm running (3.12.x from backports.org), so I'm playing with [https://packages.debian.org/search?keywords=zfs-fuse 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 <code>/etc/fstab</code> and typing '''<code>mkdir /foo</code>'''? Instead '''<code>zfs pool create solarissucksballs ...</code>''' will create a <code>/solarissucksballs</code> 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.