Differences

This shows you the differences between two versions of the page.

--- computing:storage:zfs [2015/12/25 13:59]
gcooper
+++ computing:storage:zfs [2022/08/01 12:26] (current)
gcooper
@@ Line 1: / Line 1: @@
 ====== ZFS ======
-See also **[[computing:storage:zfs_cmds|ZFS - Basic Commands]]**.
+See also **[[computing:storage:zfs_cmds|ZFS - Basic Commands]]**
-See also **[[computing:storage:shared_storage|Shared Storage System]]**.
+See also **[[computing:storage:napp-it|napp-it]]**
-See also **[[computing:storage:napp-it|napp-it]]**.
+See also **[[computing:unix:oi|OpenIndiana]]**
-See also **[[computing:unix:oi|OpenIndiana]]**.
+[[http://constantin.glez.de/blog/2011/02/frequently-asked-questions-about-flash-memory-ssds-and-zfs|ZFS and SSDs]]
 [[http://jrs-s.net/2015/02/06/zfs-you-should-use-mirror-vdevs-not-raidz/|Mirrored vs. Striped]]
@@ Line 73: / Line 73: @@
 http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide
+:!: **Always use mirrored VDEVs** for best performance, reasonable protection, best degraded performance and fastest recovery from a failed disk.
+:!: **Performance really depends on the number of spindles**.
+:!: **Only for VM storage and databases do you need or want to enable sync**.  If you simply use ZFS without foreign filesystems on it (VMs), ZFS will never corrupt on a crash due Copy On Write. So for regular filer use, disable sync unless you want a maximal security for small files like on a mailserver.
+:!: **Always utilize an SLOG** for your ZIL to improve synchronous write performance. **Database applications, NFS environments, particularly for virtualization, as well as backups are known use cases with heavy synchronous writes.**
 === RAIDZ1 ===
@@ Line 141: / Line 149: @@
 :!: Scrubs are I/O intensive and can negatively impact performance. They should be scheduled for evenings or weekends to minimize the impact to users.
-  * Napp-IT has an 'auto-service' to facilitate scrub job scheduling and creation
+  * Napp-IT has an ''auto-service'' to facilitate scrub job scheduling and creation
 ===== Snapshots and Clones =====
@@ Line 147: / Line 155: @@
 https://www.howtoforge.com/tutorial/how-to-use-snapshots-clones-and-replication-in-zfs-on-linux/
-A **snapshot** provides a read-only, point-in-time copy of a file system or volume that does not consume extra space in the ZFS pool. The snapshot uses only space when the block references are changed. Snapshots preserve disk space by recording only the differences between the current dataset and a previous version.
+A **snapshot** provides a read-only, point-in-time copy of a file system or volume that does not consume extra space in the ZFS pool. The snapshot only uses space when the block references are changed. Snapshots preserve disk space by recording only the differences between the current dataset and a previous version.
 :!: A typical example use for a snapshot is to have a quick way of backing up the current state of the file system when a risky action like a software installation or a system upgrade is performed.
 A **clone** is a writable volume or file system whose initial contents are the same as the dataset from which it was created.

Virtual Architects Support Wiki

User Tools

Site Tools

Differences

Page Tools