Zpool wizard - Revision history

Da-F at 07:43, 15 January 2026

2026-01-15T07:43:55Z

Da-F at 15:02, 15 January 2025

2025-01-15T15:02:22Z

@@ Line 1: / Line 1: @@
-Pools are used for grouping disks that belong to storage.
+<div>A '''zpool''' is the foundational storage construct in ZFS. It serves as a logical storage pool that combines multiple physical storage devices (disks) into '''vdevs''' (virtual devices), which collectively form the unified zpool. From this zpool, ZFS creates and manages '''datasets''' (file systems) and '''zvols''' (block storage volumes).</div><br/><div>The zpool wizard is made up of the following steps:</div><br/><div>
-.&nbsp;'''CREATE DATA GROUP'''&nbsp;- provides information of all hard drives that are connected to the storage server. To add the first Data Group to your zpool, please select disks on the list on the left, select the&nbsp; &nbsp; &nbsp;redundancy type and click the "'''Create group'''" button.
+This section provides information about all storage devices connected to the storage server. To add the first Data Group to your Zpool, follow these steps:
 [[Category:Help topics]]

Pa-P at 07:22, 18 August 2021

2021-08-18T07:22:34Z

← Older revision		Revision as of 07:22, 18 August 2021
Line 13:		Line 13:
	:*'''RAIDZ-3''' - three disks can fail per RAIDZ-3 group in order for the whole group to work correctly. A minimum of 5 disks should be used in RAIDZ-3 group.		:*'''RAIDZ-3''' - three disks can fail per RAIDZ-3 group in order for the whole group to work correctly. A minimum of 5 disks should be used in RAIDZ-3 group.

	:To learn more about RAIDZ types, check the ZFS RAID section in the following article: [https://~~blog.~~open-e.com/data-integrity-raidz/ https://~~blog.~~open-e.com/data-integrity-raidz/]		:To learn more about RAIDZ types, check the ZFS RAID section in the following article: [https://open-e.com/blog/data-integrity-raidz/ https://open-e.com/blog/data-integrity-raidz/]<br/>

	2. '''CREATE WRITE LOG''' - allows configuring 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.		2. '''CREATE WRITE LOG''' - allows configuring 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.

migrate>Ma-F at 14:56, 4 March 2021

2021-03-04T14:56:46Z

← Older revision		Revision as of 14:56, 4 March 2021
Line 6:		Line 6:

	:*'''Single''' - each disk works as a single drive.		:*'''Single''' - each disk works as a single drive.
	:**'''Mirror ~~(Single Group)~~''' - all ~~the disks~~ will be ~~assigned in~~ mirrored ~~group~~.		:*'''Mirror''' - all data that are stored on disk "A" will be automatically mirrored to the disk "B". At least two disks are needed for creating a mirror. There are two options:
	:**'''Mirror (~~Multiple Groups~~)''' - the disks will be assigned in ~~mirrors of two in multiple groups~~.		:**'''Mirror (Single Group)''' - all the disks will be assigned in one mirrored group.
	:*'''Mirror''' - ~~all data that are stored on disk "A"~~ will be ~~automatically mirrored to the disk "B". At least~~ two disks ~~are needed for creating a mirror~~.		:**'''Mirror (Multiple Groups)''' - the disks will be assigned in mirrors of two disks in multiple groups.
	:*'''RAIDZ-1''' - one disk can fail per RAIDZ-1 group in order for the whole group to work correctly. A minimum of 3 disks should be used in RAIDZ-1 group.		:*'''RAIDZ-1''' - one disk can fail per RAIDZ-1 group in order for the whole group to work correctly. A minimum of 3 disks should be used in RAIDZ-1 group.
	:*'''RAIDZ-2''' - two disks can fail per RAIDZ-2 group in order for the whole group to work correctly. A minimum of 4 disks should be used in RAIDZ-2 group.		:*'''RAIDZ-2''' - two disks can fail per RAIDZ-2 group in order for the whole group to work correctly. A minimum of 4 disks should be used in RAIDZ-2 group.

migrate>Ma-F at 14:52, 4 March 2021

2021-03-04T14:52:56Z

← Older revision		Revision as of 14:52, 4 March 2021
Line 7:		Line 7:
	:*'''Single''' - each disk works as a single drive.		:*'''Single''' - each disk works as a single drive.
	:**'''Mirror (Single Group)''' - all the disks will be assigned in mirrored group.		:**'''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~~.		:**'''Mirror (Multiple Groups)''' - the disks will be assigned in mirrors of two in multiple groups.
	:*'''Mirror''' - all data that are stored on disk "A" will be automatically mirrored to the disk "B". At least two disks are needed for creating a mirror.		:*'''Mirror''' - all data that are stored on disk "A" will be automatically mirrored to the disk "B". At least two disks are needed for creating a mirror.
	:*'''RAIDZ-1''' - one disk can fail per RAIDZ-1 group in order for the whole group to work correctly. A minimum of 3 disks should be used in RAIDZ-1 group.		:*'''RAIDZ-1''' - one disk can fail per RAIDZ-1 group in order for the whole group to work correctly. A minimum of 3 disks should be used in RAIDZ-1 group.

migrate>Ra-N at 12:25, 5 December 2019

2019-12-05T12:25:51Z

← Older revision		Revision as of 12:25, 5 December 2019
Line 1:		Line 1:
	Pools are used for grouping disks that belong to storage.		Pools are used for grouping disks that belong to storage.

	1. '''CREATE DATA GROUP''' - provides information of all hard drives that are connected to the storage server. To add the first Data Group to your zpool please select disks on the list on the left, select the redundancy type and click the "'''Create group'''" button.		1. '''CREATE DATA GROUP''' - provides information of all hard drives that are connected to the storage server. To add the first Data Group to your zpool, please select disks on the list on the left, select the     redundancy type and click the "'''Create group'''" button.

	:Available ~~redundancy~~ groups are:		:Available redundancies for groups are:

	:*'''Single''' - each disk works as a single drive		:*'''Single''' - each disk works as a single drive.
	:*'''Mirror''' - ~~All~~ data that are stored on disk "A" will be automatically mirrored to 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.
			:*'''Mirror''' - all data that are stored on disk "A" will be automatically mirrored to the disk "B". At least two disks are needed for creating a mirror.
			:*'''RAIDZ-1''' - one disk can fail per RAIDZ-1 group in order for the whole group to work correctly. A minimum of 3 disks should be used in RAIDZ-1 group.
			:*'''RAIDZ-2''' - two disks can fail per RAIDZ-2 group in order for the whole group to work correctly. A minimum of 4 disks should be used in RAIDZ-2 group.
			:*'''RAIDZ-3''' - three disks can fail per RAIDZ-3 group in order for the whole group to work correctly. A minimum of 5 disks should be used in RAIDZ-3 group.

	:- ~~'''Mirror (Single Group)'''~~ - ~~all the disks will be assigned in mirrored group~~		:To learn more about RAIDZ types, check the ZFS RAID section in the following article: [https://blog.open-e.com/data-integrity-raidz/ https://blog.open-e.com/data-integrity-raidz/]
	:- ~~'''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.		2. '''CREATE WRITE LOG''' - allows configuring 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 the 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.		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 the 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 spares for a pool. ZFS allows devices to be associated with pools as "spares". To create a pool with 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. If a pool has a shared spare that is currently being used, the pool cannot be exported since other pools may use this shared spare, which may lead to potential data corruption. Spares cannot replace log devices.		4. '''CREATE SPARE DISK''' - A special pseudo-vdev which keeps track of available spares for a pool. ZFS allows devices to be associated with pools as "spares". To create a pool with 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. If a pool has a shared spare that is currently being used, the pool cannot 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.		5. '''ZPOOL PROPERTIES''' - allows defining 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.		6. '''SUMMARY''' - sumarizes the zpool configuration: groups of disks that are used for data and other groups of disks, used for caching, spare, etc.

migrate>To-K at 14:51, 10 April 2019

2019-04-10T14:51:19Z

← Older revision		Revision as of 14:51, 10 April 2019
Line 11:		Line 11:
	:- '''Mirror (Multiple Groups)''' - the disks will be assigned in pairs of two in this 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.		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 the 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.		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 the 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 cannot be exported since other pools may use this shared spare, which may lead to potential data corruption. Spares cannot replace log devices.		4. '''CREATE SPARE DISK''' - A special pseudo-vdev which keeps track of available spares for a pool. ZFS allows devices to be associated with pools as "spares". To create a pool with 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. If a pool has a shared spare that is currently being used, the pool cannot 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.		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.		6. '''SUMMARY''' - sumarizes the zpool configuration: groups of disks that are used for data, and other groups of disks, used for caching, spare, etc.

Ma-W at 08:15, 28 March 2019

2019-03-28T08:15:17Z

← Older revision		Revision as of 08:15, 28 March 2019
Line 11:		Line 11:
	:- '''Mirror (Multiple Groups)''' - the disks will be assigned in pairs of two in this 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.		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 the 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 cannot be exported since other pools may use this shared spare, which may lead to potential data corruption. Spares cannot replace log devices.		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 the 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.
	5. '''ZPOOL PROPERTIES''' - allows to define a pool called as a " Zpool name ". This name of the zpool will be used in the system.
			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 cannot 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.		6. '''SUMMARY''' - sumarizes the zpool configuration: groups of disks that are used for data, and other groups of disks, used for caching, spare, etc.

Ma-W at 08:14, 28 March 2019

2019-03-28T08:14:29Z

← Older revision		Revision as of 08:14, 28 March 2019
Line 1:		Line 1:
	Pools are used for grouping disks that belong to storage.		Pools are used for grouping disks that belong to storage.

	#'''CREATE DATA GROUP''' - provides information of all hard drives that are connected to the storage server. To add the first Data Group to your zpool please select disks on the list on the left, select the redundancy type and click the "'''Create group'''" button.		1. '''CREATE DATA GROUP''' - provides information of all hard drives that are connected to the storage server. To add the first Data Group to your zpool please select disks on the list on the left, select the redundancy type and click the "'''Create group'''" button.

	:Available redundancy groups are:		:Available redundancy groups are:
Line 8:		Line 8:
	:*'''Mirror''' - All data that are stored on disk "A" will be automatically mirrored to the disk "B". At least two disks are needed for creating a mirror. They need to be the same size		:*'''Mirror''' - All data that are stored on disk "A" will be automatically mirrored to 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 (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		:- '''Mirror (Multiple Groups)''' - the disks will be assigned in pairs of two in this group

	#'''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.		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.
	#'''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 the 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.		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 the 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.
	#'''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 cannot be exported since other pools may use this shared spare, which may lead to potential data corruption. Spares cannot replace log devices.		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 cannot be exported since other pools may use this shared spare, which may lead to potential data corruption. Spares cannot replace log devices.
	#'''ZPOOL PROPERTIES''' - allows to define a pool called as a " Zpool name ". This name of the zpool will be used in the system.		5. '''ZPOOL PROPERTIES''' - allows to define a pool called as a " Zpool name ". This name of the zpool will be used in the system.
	#'''SUMMARY''' - sumarizes the zpool configuration: groups of disks that are used for data, and other groups of disks, used for caching, spare, etc.		6. '''SUMMARY''' - sumarizes the zpool configuration: groups of disks that are used for data, and other groups of disks, used for caching, spare, etc.

Ma-W at 08:13, 28 March 2019

2019-03-28T08:13:53Z

← Older revision		Revision as of 08:13, 28 March 2019
Line 2:		Line 2:

	#'''CREATE DATA GROUP''' - provides information of all hard drives that are connected to the storage server. To add the first Data Group to your zpool please select disks on the list on the left, select the redundancy type and click the "'''Create group'''" button.		#'''CREATE DATA GROUP''' - provides information of all hard drives that are connected to the storage server. To add the first Data Group to your zpool please select disks on the list on the left, select the redundancy type and click the "'''Create group'''" button.
	Available redundancy groups are:
	*'''Single''' - each disk works as a single drive		:Available redundancy groups are:
	*'''Mirror''' - All data that are stored on disk "A" will be automatically mirrored to 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		:*'''Single''' - each disk works as a single drive
	- '''Mirror (Multiple Groups)''' - the disks will be assigned in pairs of two in this group		:*'''Mirror''' - All data that are stored on disk "A" will be automatically mirrored to 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

	#'''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.		#'''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.
	#'''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 the 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.		#'''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 the 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.