Virtual Architects Support Wiki

User Tools

Site Tools

You are here: start » computing » storage » zfs
Trace:
computing:storage:zfs

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
computing:storage:zfs [2020/05/07 11:56]
gcooper 		computing:storage:zfs [2022/08/01 12:26] (current)
gcooper
Line 78: Line 78:
 :!: **Performance really depends on the number of spindles**. :!: **Performance really depends on the number of spindles**.
  
-:!: **Only for VM storage and databases do you need or want to enable sync**.+:!: **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.** :!: **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.**
Line 155: Line 155:
 https://www.howtoforge.com/tutorial/how-to-use-snapshots-clones-and-replication-in-zfs-on-linux/ 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 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. A **clone** is a writable volume or file system whose initial contents are the same as the dataset from which it was created.
computing/storage/zfs.1588874164.txt.gz · Last modified: 2020/05/07 11:56 by gcooper

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki