This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
computing:storage:zfs [2013/02/27 10:47] gcooper |
computing:storage:zfs [2022/08/01 12:26] (current) gcooper |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== ZFS ====== | ====== ZFS ====== | ||
- | See also **[[computing: | + | See also **[[computing: |
- | See also **[[computing: | + | See also **[[computing: |
- | See also **[[computing: | + | See also **[[computing: |
- | See also **[[computing:unix:oi|OpenIndiana]]**. | + | [[http:// |
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | [[http:// | ||
[[http:// | [[http:// | ||
Line 16: | Line 28: | ||
[[http:// | [[http:// | ||
+ | |||
+ | [[https:// | ||
[[http:// | [[http:// | ||
[[http:// | [[http:// | ||
+ | |||
+ | [[http:// | ||
ZFS is a new and high-performance filesystem devised by Sun Microsystems (now Oracle) for the Solaris unix operating system. | ZFS is a new and high-performance filesystem devised by Sun Microsystems (now Oracle) for the Solaris unix operating system. | ||
Line 39: | Line 55: | ||
===== Choosing Array Configurations ===== | ===== Choosing Array Configurations ===== | ||
+ | |||
+ | **Why not RAIDZ (RAID5)?** http:// | ||
http:// | http:// | ||
Line 55: | Line 73: | ||
http:// | http:// | ||
+ | |||
+ | :!: **Always use mirrored VDEVs** for best performance, | ||
+ | |||
+ | :!: **Performance really depends on the number of spindles**. | ||
+ | |||
+ | :!: **Only for VM storage and databases do you need or want to enable sync**. | ||
+ | |||
+ | :!: **Always utilize an SLOG** for your ZIL to improve synchronous write performance. **Database applications, | ||
=== RAIDZ1 === | === RAIDZ1 === | ||
Line 116: | Line 142: | ||
http:// | http:// | ||
+ | |||
+ | ===== Scrub Your Zpools ===== | ||
+ | |||
+ | https:// | ||
+ | |||
+ | :!: 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 '' | ||
+ | |||
+ | ===== Snapshots and Clones ===== | ||
+ | |||
+ | https:// | ||
+ | |||
+ | 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. |