Lines 50-56
endif::[]
Link Here
|
50 |
|
50 |
|
51 |
ZFS is an advanced file system designed to solve major problems found in previous storage subsystem software. |
51 |
ZFS is an advanced file system designed to solve major problems found in previous storage subsystem software. |
52 |
|
52 |
|
53 |
Originally developed at Sun(TM), ongoing open source ZFS development has moved to the http://open-zfs.org[OpenZFS Project]. |
53 |
Originally developed at Sun(TM), ongoing open source ZFS development has moved to the http://openzfs.org[OpenZFS Project]. |
54 |
|
54 |
|
55 |
ZFS has three major design goals: |
55 |
ZFS has three major design goals: |
56 |
|
56 |
|
Lines 488-494
The <<zfs-zfs,`zfs`>> utility allows creating, destroying, and managing datasets
Link Here
|
488 |
[[zfs-zpool-create]] |
488 |
[[zfs-zpool-create]] |
489 |
=== Creating and Destroying Storage Pools |
489 |
=== Creating and Destroying Storage Pools |
490 |
|
490 |
|
491 |
Creating a ZFS storage pool (_zpool_) requires permanent decisions, as the pool structure cannot change after creation. |
491 |
Creating a ZFS storage pool requires permanent decisions, as the pool structure cannot change after creation. |
492 |
The most important decision is which types of vdevs to group the physical disks into. |
492 |
The most important decision is which types of vdevs to group the physical disks into. |
493 |
See the list of <<zfs-term-vdev,vdev types>> for details about the possible options. |
493 |
See the list of <<zfs-term-vdev,vdev types>> for details about the possible options. |
494 |
After creating the pool, most vdev types do not allow adding disks to the vdev. |
494 |
After creating the pool, most vdev types do not allow adding disks to the vdev. |
Lines 580-586
This can cause undefined behavior in applications which had open files on those
Link Here
|
580 |
[[zfs-zpool-attach]] |
580 |
[[zfs-zpool-attach]] |
581 |
=== Adding and Removing Devices |
581 |
=== Adding and Removing Devices |
582 |
|
582 |
|
583 |
Two ways exist for adding disks to a zpool: attaching a disk to an existing vdev with `zpool attach`, or adding vdevs to the pool with `zpool add`. |
583 |
Two ways exist for adding disks to a pool: attaching a disk to an existing vdev with `zpool attach`, or adding vdevs to the pool with `zpool add`. |
584 |
Some <<zfs-term-vdev,vdev types>> allow adding disks to the vdev after creation. |
584 |
Some <<zfs-term-vdev,vdev types>> allow adding disks to the vdev after creation. |
585 |
|
585 |
|
586 |
A pool created with a single disk lacks redundancy. |
586 |
A pool created with a single disk lacks redundancy. |
Lines 2692-2700
For a more detailed list of recommendations for ZFS-related tuning, see https://
Link Here
|
2692 |
[[zfs-links]] |
2692 |
[[zfs-links]] |
2693 |
== Further Resources |
2693 |
== Further Resources |
2694 |
|
2694 |
|
2695 |
* http://open-zfs.org[OpenZFS] |
2695 |
* http://openzfs.org[OpenZFS] |
2696 |
* https://wiki.freebsd.org/ZFSTuningGuide[FreeBSD Wiki - ZFS Tuning] |
2696 |
* https://wiki.freebsd.org/ZFSTuningGuide[FreeBSD Wiki - ZFS Tuning] |
2697 |
* http://docs.oracle.com/cd/E19253-01/819-5461/index.html[Oracle Solaris ZFS Administration Guide] |
|
|
2698 |
* https://calomel.org/zfs_raid_speed_capacity.html[Calomel Blog - ZFS Raidz Performance, Capacity and Integrity] |
2697 |
* https://calomel.org/zfs_raid_speed_capacity.html[Calomel Blog - ZFS Raidz Performance, Capacity and Integrity] |
2699 |
|
2698 |
|
2700 |
[[zfs-term]] |
2699 |
[[zfs-term]] |