Zpool wizard: Difference between revisions
migrate>Ad-B No edit summary |
migrate>To-K No edit summary |
||
| Line 1: | Line 1: | ||
<span style="font-size:small | <span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif">Pools are used for grouping disks that belong to storages.</span></span> | ||
<span style="font-family: arial, helvetica, sans-serif; font-size: small | <span style="font-family: arial, helvetica, sans-serif; font-size: small">1. </span>'''CREATE DATA GROUP '''<span style="font-family: arial, helvetica, sans-serif; font-size: small">- provides information of all hard drives that are connected to the storage server. To add first Data Group to your zpool please select disks on the list on the left, select redundancy type and click "'''Create group'''" button.</span> | ||
<span style="font-size:small | <span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif"> Available redundancy groups are :</span></span> | ||
*<span style="font-family: arial, helvetica, sans-serif; font-size: small | *<span style="font-family: arial, helvetica, sans-serif; font-size: small">'''Single '''- each disks works as a single drive</span> | ||
*<span style="font-family: arial, helvetica, sans-serif; font-size: small | *<span style="font-family: arial, helvetica, sans-serif; font-size: small">'''Mirror '''- All data that are stored on disk "A" will be automatically mirrored on the disk "B". At least two disks are needed for creating a mirror. They need to be the same size</span> | ||
- '''Mirror (Single Group) '''- all the disks will be assigned in mirrored group | |||
- '''Mirror (''''''Multiple Groups) - '''the disks will be assigned in pairs of two in this group | |||
<span style="font-size:small | <span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif">2. '''CREATE WRITE LOG''' - allows to configure the write log function, using a redundancy level (mirror or single drive). A separate-intent log device. If more than one log device is specified, then writes are load-balanced between devices. Log devices can be mirrored. However, raidz vdev types are not supported for the intent log.</span></span> | ||
<span style="font-size:small | <span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif">3.'''CREATE READ CACHE '''- A device used to cache storage pool data. A cache device cannot be configured as a mirror or raidz group.These devices provide an additional layer of caching between main memory and disk. For read-heavy workload,where the working set size is much larger than what can be cached in main memory, using cache devices allow much more of this working set to be served from low latency media. Using cache devices provides the greatest performance improvement for random read-workloads of mostly static content.</span></span> | ||
<span style="font-family: arial, helvetica, sans-serif; font-size: small;">6. </span>'''SUMMARY'''<span style="font-family: arial, helvetica, sans-serif; font-size: small | <span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif">4. '''CREATE SPARE DISK''' - A special pseudo-vdev which keeps track of available hot spares for a pool.ZFS allows devices to be associated with pools as "hot spares". These devices are not actively used in the pool, but when an active device fails, it is automatically replaced by a hot spare. To create a pool with hot spares, specify a "spare" vdev with any number of devices.Once a spare replacement is initiated, a new "spare" vdev is created within the configuration that will remain there until the original device is replaced. At this point, the hot spare becomes available again if another device fails.If a pool has a shared spare that is currently being used, the pool can not be exported since other pools may use this shared spare, which may lead to potential data corruption.Spares cannot replace log devices.</span></span> | ||
<span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif">5. '''ZPOOL PROPERTIES''' - allows to define a pool called as a " Zpool name ". This name of the zpool will be used in the system.</span></span> | |||
<span style="font-family: arial, helvetica, sans-serif; font-size: small">6. </span>'''SUMMARY'''<span style="font-family: arial, helvetica, sans-serif; font-size: small">- sumarizes the zpool configuration : groups of disks that are used for data, and other groups of disks, used for caching, spare, etc.</span> | |||
Revision as of 12:11, 24 September 2014
Pools are used for grouping disks that belong to storages.
1. CREATE DATA GROUP - provides information of all hard drives that are connected to the storage server. To add first Data Group to your zpool please select disks on the list on the left, select redundancy type and click "Create group" button.
Available redundancy groups are :
- Single - each disks works as a single drive
- Mirror - All data that are stored on disk "A" will be automatically mirrored on the disk "B". At least two disks are needed for creating a mirror. They need to be the same size
- Mirror (Single Group) - all the disks will be assigned in mirrored group
- 'Mirror ('Multiple Groups) - the disks will be assigned in pairs of two in this group
2. CREATE WRITE LOG - allows to configure the write log function, using a redundancy level (mirror or single drive). A separate-intent log device. If more than one log device is specified, then writes are load-balanced between devices. Log devices can be mirrored. However, raidz vdev types are not supported for the intent log.
3.CREATE READ CACHE - A device used to cache storage pool data. A cache device cannot be configured as a mirror or raidz group.These devices provide an additional layer of caching between main memory and disk. For read-heavy workload,where the working set size is much larger than what can be cached in main memory, using cache devices allow much more of this working set to be served from low latency media. Using cache devices provides the greatest performance improvement for random read-workloads of mostly static content.
4. CREATE SPARE DISK - A special pseudo-vdev which keeps track of available hot spares for a pool.ZFS allows devices to be associated with pools as "hot spares". These devices are not actively used in the pool, but when an active device fails, it is automatically replaced by a hot spare. To create a pool with hot spares, specify a "spare" vdev with any number of devices.Once a spare replacement is initiated, a new "spare" vdev is created within the configuration that will remain there until the original device is replaced. At this point, the hot spare becomes available again if another device fails.If a pool has a shared spare that is currently being used, the pool can not be exported since other pools may use this shared spare, which may lead to potential data corruption.Spares cannot replace log devices.
5. ZPOOL PROPERTIES - allows to define a pool called as a " Zpool name ". This name of the zpool will be used in the system.
6. SUMMARY- sumarizes the zpool configuration : groups of disks that are used for data, and other groups of disks, used for caching, spare, etc.