Skip to Content
Last modified by Drunk Monkey on 2024-09-01 12:46
From version 3.1
edited by Drunk Monkey
on 2024-09-01 11:39
Change comment: There is no comment for this version
To version 4.1
edited by Drunk Monkey
on 2024-09-01 12:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,7 +5,7 @@
5 5  * Always enable compression. There is almost certainly no reason to keep it disabled. It hardly touches the CPU and hardly touches throughput to the drive, yet the benefits are amazing.
6 6  * Unless you have the RAM, avoid using deduplication. Unlike compression, deduplication is very costly on the system. The deduplication table consumes massive amounts of RAM.
7 7  * Avoid running a ZFS root filesystem on GNU/Linux for the time being. It's a bit too experimental for /boot and GRUB. However, do create datasets for /home/, /var/log/ and /var/cache/.
8 -* Snapshot frequently and regularly. Snapshots are cheap, and can keep a plethora of file versions over time. Consider using something like the [[zfs-auto-snapshot script>>url:https://web.archive.org/web/20210316181746/https://github.com/zfsonlinux/zfs-auto-snapshot]].
8 +* Snapshot frequently and regularly. Snapshots are cheap, and can keep a plethora of file versions over time. Consider using something like the [[zfs-auto-snapshot script>>https://github.com/zfsonlinux/zfs-auto-snapshot]].
9 9  * Snapshots are not a backup. Use "zfs send" and "zfs receive" to send your ZFS snapshots to an external storage.
10 10  * If using NFS, use ZFS NFS rather than your native exports. This can ensure that the dataset is mounted and online before NFS clients begin sending data to the mountpoint.
11 11  * Don't mix NFS kernel exports and ZFS NFS exports. This is difficult to administer and maintain.
... ... @@ -24,7 +24,6 @@
24 24  * When creating ZVOLs, make sure to set the block size as the same, or a multiple, of the block size that you will be formatting the ZVOL with. If the block sizes do not align, performance issues could arise.
25 25  * When loading the "zfs" kernel module, make sure to set a maximum number for the ARC. Doing a lot of "zfs send" or snapshot operations will cache the data. If not set, RAM will slowly fill until the kernel invokes OOM killer, and the system becomes responsive. I have set in my /etc/modprobe.d/zfs.conf file "options zfs zfs_arc_max=2147483648", which is a 2 GB limit for the ARC.
26 26  
27 -
28 28  ----
29 29  
30 30  (% style="text-align: center;" %)