Storage pools store data and can be created during or after initial configuration. Pools can contain data drives, and log, read cache, and meta devices. The following task assumes that initial configuration has been completed. Creating and configuring a storage pool is a two-step process. First, the storage devices are verified for presence and minimum functionality, and you assign drives or even entire disk shelves to the pool. Second, you select a profile for the drives based on your storage needs. If for some reason a pool is unconfigured, you can import it as described in Importing an Existing Storage Pool (CLI).
To reduce redundant data, which can be especially prevalent in replication workloads, consider the benefits of using deduplication. Allocate meta devices if deduplication will be enabled for projects or shares in this pool. For more information, see Data Deduplication. There is also an all-flash storage pool, which utilizes SSDs as data devices and optional log devices, but does not contain read cache or meta devices. See Configuring an All-Flash Storage Pool (CLI).
Before You Begin
For recommendations on how many drives to select per pool, see Number of Devices per Pool.
To understand the different data profiles, see Data Profiles for Storage Pools.
Do not perform a pool configuration operation while a disk firmware upgrade is occurring. To check if an upgrade is in progress, navigate to maintenance system updates.
To use the enhanced data depulication feature in a storage pool, upgrade to software release OS8.7.0 or later and accept all deferred updates, including Data Deduplication v2. See Data Deduplication v2 Deferred Update in Oracle ZFS Storage Appliance Customer Service Manual.
hostname: configuration storage> config pool0 hostname: configuration storage (pool0) verify>
hostname:configuration storage (pool0) verify> show ID STATUS ALLOCATION DATA LOG CACHE META RPM 0 ok custom 0 0 0/4 0/4 1.86T 1 ok custom 0 0/2 34G 0 0 15000 2 ok custom 0 0/2 34G 0 0 15000
For more information on log, cache, and meta devices, see Data Profiles for Storage Pools.
Caution - Once a data disk has been added to a pool, it cannot be removed without destroying the pool entirely and losing all data. |
ID "0" is the controller, and the remaining IDs are the disk shelves. In the following example, 1-data=8 allocates eight data drives from the first disk shelf.
hostname:configuration storage (pool1) verify> set 1-data=8 1-data = 8
This example allocates one cache device from the controller:
hostname:configuration storage (pool1) verify> set 0-cache=1 0-cache = 1
This example allocates one meta device from the controller:
hostname:configuration storage (pool1) verify> set 0-meta=1 0-meta = 1
hostname:configuration storage (pool1) verify> done
hostname:configuration storage (pool1) config> show PROFILE CAPCITY NSPF DESCRIPTION log_profile = log_stripe 17G no Striped log
Caution - A double failure can cause loss of data from a log in a striped configuration. It is highly recommended to configure a mirrored log profile for added redundancy. For more information, see Data Profiles for Storage Pools. |
hostname:configuration storage (pool1)> set log_profile=log_mirror
hostname:configuration storage (pool1)> set meta_profile=meta_mirror
hostname:configuration storage (pool1)> done