1. Oracle Solaris ZFS File System (Introduction)
Splitting a Mirrored ZFS Storage Pool (zpool split)
Changes to the zpool list Command
ZFS Device Replacement Enhancements
ZFS and Flash Installation Support
ZFS ACL Pass Through Inheritance for Execute Permission
Using Cache Devices in Your ZFS Storage Pool
Zone Migration in a ZFS Environment
ZFS Installation and Boot Support
Rolling Back a Dataset Without Unmounting
Enhancements to the zfs send Command
ZFS Quotas and Reservations for File System Data Only
ZFS Command History Enhancements (zpool history)
Upgrading ZFS File Systems (zfs upgrade)
Setting Up Separate ZFS Log Devices
Creating Intermediate ZFS Datasets
Recursively Renaming ZFS Snapshots (zfs rename -r)
gzip Compression Is Available for ZFS
Storing Multiple Copies of ZFS User Data
ZFS and Solaris iSCSI Improvements
ZFS Command History (zpool history)
Setting Properties When Creating ZFS File Systems
Displaying All ZFS File System Information
Hot Spares for ZFS Storage Pool Devices
Replacing a ZFS File System With a ZFS Clone (zfs promote)
Upgrading ZFS Storage Pools (zpool upgrade)
ZFS Backup and Restore Commands Are Renamed
Recovering Destroyed Storage Pools
ZFS Is Integrated With Fault Manager
File System Monitoring Tool (fsstat)
Checksums and Self-Healing Data
ZFS Component Naming Requirements
2. Getting Started With Oracle Solaris ZFS
3. Oracle Solaris ZFS and Traditional File System Differences
4. Managing Oracle Solaris ZFS Storage Pools
5. Installing and Booting an Oracle Solaris ZFS Root File System
6. Managing Oracle Solaris ZFS File Systems
7. Working With Oracle Solaris ZFS Snapshots and Clones
8. Using ACLs to Protect Oracle Solaris ZFS Files
9. Oracle Solaris ZFS Delegated Administration
10. Oracle Solaris ZFS Advanced Topics
11. Oracle Solaris ZFS Troubleshooting and Pool Recovery
This section describes the basic terminology used throughout this book:
A boot environment that is created by the lucreate command and possibly updated by the luupgrade command, but it is not the active or primary boot environment. The alternate boot environment can become the primary boot environment by running the luactivate command.
A 256-bit hash of the data in a file system block. The checksum capability can range from the simple and fast fletcher4 (the default) to cryptographically strong hashes such as SHA256.
A file system whose initial contents are identical to the contents of a snapshot.
For information about clones, see Overview of ZFS Clones.
A generic name for the following ZFS components: clones, file systems, snapshots, and volumes.
Each dataset is identified by a unique name in the ZFS namespace. Datasets are identified using the following format:
pool/path[@snapshot]
Identifies the name of the storage pool that contains the dataset
Is a slash-delimited path name for the dataset component
Is an optional component that identifies a snapshot of a dataset
For more information about datasets, see Chapter 6, Managing Oracle Solaris ZFS File Systems.
A ZFS dataset of type filesystem that is mounted within the standard system namespace and behaves like other file systems.
For more information about file systems, see Chapter 6, Managing Oracle Solaris ZFS File Systems.
A virtual device that stores identical copies of data on two or more disks. If any disk in a mirror fails, any other disk in that mirror can provide the same data.
A logical group of devices describing the layout and physical characteristics of the available storage. Disk space for datasets is allocated from a pool.
For more information about storage pools, see Chapter 4, Managing Oracle Solaris ZFS Storage Pools.
A boot environment that is used by the lucreate command to build the alternate boot environment. By default, the primary boot environment is the current boot environment. This default can be overridden by using the lucreate -s option.
A virtual device that stores data and parity on multiple disks. For more information about RAID-Z, see RAID-Z Storage Pool Configuration.
The process of copying data from one device to another device is known as resilvering. For example, if a mirror device is replaced or taken offline, the data from an up-to-date mirror device is copied to the newly restored mirror device. This process is referred to as mirror resynchronization in traditional volume management products.
For more information about ZFS resilvering, see Viewing Resilvering Status.
A read-only copy of a file system or volume at a given point in time.
For more information about snapshots, see Overview of ZFS Snapshots.
A logical device in a pool, which can be a physical device, a file, or a collection of devices.
For more information about virtual devices, see Displaying Storage Pool Virtual Device Information.
A dataset that represents a block device. For example, you can create a ZFS volume as a swap device.
For more information about ZFS volumes, see ZFS Volumes.