Add new zvol - Revision history

Da-F at 08:09, 15 January 2026

2026-01-15T08:09:27Z

← Older revision		Revision as of 08:09, 15 January 2026
Line 1:		Line 1:
	__NOTOC__<onlyinclude>A zvol is a ZFS block device created inside a ZFS pool (zpool). In this documentation, the term zvol refers to a block-type resource that is typically exported as a LUN to hosts over iSCSI, Fibre Channel, or NVMe-oF. Zvols are usually used to:		__NOTOC__<onlyinclude>
			A zvol is a ZFS block device created inside a ZFS pool (zpool). In this documentation, the term zvol refers to a block-type resource that is typically exported as a LUN to hosts over iSCSI, Fibre Channel, or NVMe-oF. Zvols are usually used to:

	* Provide block storage for virtual machines, databases, or other applications that expect a disk device.		* Provide block storage for virtual machines, databases, or other applications that expect a disk device.
Line 6:		Line 7:

	You first create a zvol, and then (optionally) attach it to a target to make it available to hosts.		You first create a zvol, and then (optionally) attach it to a target to make it available to hosts.
			<onlyinclude>
	<onlyinclude>== Creating a zvol ==		== Creating a zvol ==

	# Go to the zpool management view in the GUI.		# Go to the zpool management view in the GUI.

Da-F at 08:02, 15 January 2026

2026-01-15T08:02:53Z

← Older revision		Revision as of 08:02, 15 January 2026
Line 1:		Line 1:
	~~__NOTOC__A~~ zvol is a ZFS block device created inside a ZFS pool (zpool). In this documentation, the term zvol refers to a block-type resource that is typically exported as a LUN to hosts over iSCSI, Fibre Channel, or NVMe-oF. Zvols are usually used to:		__NOTOC__<onlyinclude>A zvol is a ZFS block device created inside a ZFS pool (zpool). In this documentation, the term zvol refers to a block-type resource that is typically exported as a LUN to hosts over iSCSI, Fibre Channel, or NVMe-oF. Zvols are usually used to:

	* Provide block storage for virtual machines, databases, or other applications that expect a disk device.		* Provide block storage for virtual machines, databases, or other applications that expect a disk device.
	* Separate workloads that require different performance or data-protection policies (for example, different compression, block size, or deduplication settings).		* Separate workloads that require different performance or data-protection policies (for example, different compression, block size, or deduplication settings).
	* Control how space is consumed by different applications or tenants at the pool level.		* Control how space is consumed by different applications or tenants at the pool level.</onlyinclude>

	You first create a zvol, and then (optionally) attach it to a target to make it available to hosts.		You first create a zvol, and then (optionally) attach it to a target to make it available to hosts.

	== Creating a zvol ==		<onlyinclude>== Creating a zvol ==

	# Go to the zpool management view in the GUI.		# Go to the zpool management view in the GUI.
Line 135:		Line 135:
	* '''None''' – exclude this zvol from L2ARC caching.		* '''None''' – exclude this zvol from L2ARC caching.

	Use '''Metadata''' or '''None''' for zvols that would otherwise fill L2ARC with data that has low reuse value, thereby preserving cache space for more critical workloads.		Use '''Metadata''' or '''None''' for zvols that would otherwise fill L2ARC with data that has low reuse value, thereby preserving cache space for more critical workloads.</onlyinclude>

	=== Attach to target ===		=== Attach to target ===

Da-F at 07:58, 15 January 2026

2026-01-15T07:58:32Z

Show changes

migrate>Ja-S at 20:42, 7 September 2020

2020-09-07T20:42:36Z

← Older revision		Revision as of 20:42, 7 September 2020
Line 4:		Line 4:
	*'''Size''' - Size of the new Zvol. The unit for this values is '''GiB (Gibibyte).'''<br/>In general, if you multiply 1024 ·1024 ·1024 = 1 073 741 824b, the result is equal to 2<sup>30</sup>.<br/>For example, 1 GiB = 1024 × 1 MiB = 1024 × 1024 × 1 KiB = 1024 × 1024 × 1024 × 1 B = 1 073 741 824 ~ 1070 GB		*'''Size''' - Size of the new Zvol. The unit for this values is '''GiB (Gibibyte).'''<br/>In general, if you multiply 1024 ·1024 ·1024 = 1 073 741 824b, the result is equal to 2<sup>30</sup>.<br/>For example, 1 GiB = 1024 × 1 MiB = 1024 × 1024 × 1 KiB = 1024 × 1024 × 1024 × 1 B = 1 073 741 824 ~ 1070 GB

	*'''Provisioning''':		'''Provisioning''':'''Thin provisioned -''' involves using virtualization technology to give the appearance of having more physical resources than are actually available. Use this format to save storage space. For the thin disk, you provision as much datastore space as the disk would require based on the value that you enter for the disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations.
	**'''Thin provisioned -''' involves using virtualization technology to give the appearance of having more physical resources than are actually available. Use this format to save storage space. For the thin disk, you provision as much datastore space as the disk would require based on the value that you enter for the disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations.
	**'''Thick provisioned (default)''' - creates a virtual disk in a thick format. Space required for the virtual disk is allocated when the virtual disk is created. Data remaining on the physical device is not erased during creation.		**'''Thick provisioned (default)''' - creates a virtual disk in a thick format. Space required for the virtual disk is allocated when the virtual disk is created. Data remaining on the physical device is not erased during creation.

	*'''Deduplication''':		'''Deduplication''':'''Disabled (default)'''
	**'''Disabled (default)'''
	**'''On - '''is a pseudonym for "sha256"		**'''On - '''is a pseudonym for "sha256"
	**'''Verify - '''is a pseudonym for "sha256,verify", option that performs a full comparison of every incoming block with any alleged duplicate to ensure that they really are the same		**'''Verify - '''is a pseudonym for "sha256,verify", option that performs a full comparison of every incoming block with any alleged duplicate to ensure that they really are the same
Line 15:		Line 13:
	**'''sha256, Verify - '''enables an ability to detect and correct hash collisions, however this is very system intensive and is not recommended for casual use		**'''sha256, Verify - '''enables an ability to detect and correct hash collisions, however this is very system intensive and is not recommended for casual use

	*'''~~COPIES ~~'''- Controls the number of copies of data stored for this dataset. These copies are in addition to any redundancy provided by the pool, for example, mirroring or raid-z. The copies are stored on different disks, if possible. The space used by multiple copies is charged to the associated file and dataset, changing the "used" property and counting against quotas and reservations. Changing this property only affects the newly-written data. You can choose from three options:		*'''Number of the data copies '''- Controls the number of copies of data stored for this dataset. These copies are in addition to any redundancy provided by the pool, for example, mirroring or raid-z. The copies are stored on different disks, if possible. The space used by multiple copies is charged to the associated file and dataset, changing the "used" property and counting against quotas and reservations. Changing this property only affects the newly-written data. You can choose from three options:
	**'''1 (default)'''		**'''1 (default)'''
	**'''2'''		**'''2'''
Line 26:		Line 24:
	**'''lz4''' - is intended as a faster and smarter replacement for lzjb		**'''lz4''' - is intended as a faster and smarter replacement for lzjb
	*'''Volume block size  - '''specifies the block size of the volume. The block size cannot be changed once the volume has been written, so it should be set at volume creation time. ''''''The default value is '''128''' '''KiB. '''<br/>The value can be changed. You can choose between : 4; 8; 16; 32; 64; 128, 256; 512 [KiB] and 1 [MB].		*'''Volume block size  - '''specifies the block size of the volume. The block size cannot be changed once the volume has been written, so it should be set at volume creation time. ''''''The default value is '''128''' '''KiB. '''<br/>The value can be changed. You can choose between : 4; 8; 16; 32; 64; 128, 256; 512 [KiB] and 1 [MB].
	*'''Write cache ~~logging (~~sync~~) ~~'''- you can choose from three options :		*'''Write cache sync request '''- you can choose from three options :
	**'''always (default)'''		**'''always (default)'''
	**'''standard'''		**'''standard'''
	**'''disabled'''		**'''disabled'''
	*'''Write cache ~~logging~~ (~~log bias~~) '''-''' '''Use this property to provide a hint to system about handling synchronous requests for a specific dataset. If logbias is set to '''Write log device (latency)''', JovianDSS uses the pool's separate log devices, if any, to handle the requests at low latency. If logbias is set to '''In pool (throughput)''', the system does not use the pool's separate log devices. Instead, JovianDSS optimizes synchronous operations for global pool throughput and efficient use of resources. The default value is Write log device (latency). For most configurations, the default value is recommended.		*'''Write cache sync request handling (logbias) '''-''' '''Use this property to provide a hint to system about handling synchronous requests for a specific dataset. If logbias is set to '''Write log device (latency)''', JovianDSS uses the pool's separate log devices, if any, to handle the requests at low latency. If logbias is set to '''In pool (throughput)''', the system does not use the pool's separate log devices. Instead, JovianDSS optimizes synchronous operations for global pool throughput and efficient use of resources. The default value is Write log device (latency). For most configurations, the default value is recommended.

	*'''~~Primary~~ cache~~ ~~'''- Controls what is cached in the primary cache (ARC). If this property is set to "All", then both user data and metadata is cached. If this property is set to "None", then neither user data nor metadata is cached. If this property is set to "Metadata", then only metadata is cached. The default value is "All".		*'''Read cache (primary ARC) scope '''- Controls what is cached in the primary cache (ARC). If this property is set to "All", then both user data and metadata is cached. If this property is set to "None", then neither user data nor metadata is cached. If this property is set to "Metadata", then only metadata is cached. The default value is "All".
	*'''~~Secondary~~ cache~~ ~~'''- Controls what is cached in the secondary cache (L2ARC). If this property is set to "All", then both user data and metadata is cached. If this property is set to "None", then neither user data nor metadata is cached. If this property is set to "Metadata", then only metadata is cached. The default value is "All".		*'''Read cache (secondary, L2ARC) scope '''- Controls what is cached in the secondary cache (L2ARC). If this property is set to "All", then both user data and metadata is cached. If this property is set to "None", then neither user data nor metadata is cached. If this property is set to "Metadata", then only metadata is cached. The default value is "All".

	You can attach this newly created zvol to a target. To do that, you have to:		You can attach this newly created zvol to a target. To do that, you have to:

migrate>Ja-S at 22:23, 24 April 2019

2019-04-24T22:23:31Z

← Older revision		Revision as of 22:23, 24 April 2019
Line 8:		Line 8:
	**'''Thick provisioned (default)''' - creates a virtual disk in a thick format. Space required for the virtual disk is allocated when the virtual disk is created. Data remaining on the physical device is not erased during creation.		**'''Thick provisioned (default)''' - creates a virtual disk in a thick format. Space required for the virtual disk is allocated when the virtual disk is created. Data remaining on the physical device is not erased during creation.

	'''Deduplication''':'''Disabled (default)'''		*'''Deduplication''':
			**'''Disabled (default)'''
	**'''On - '''is a pseudonym for "sha256"		**'''On - '''is a pseudonym for "sha256"
	**'''Verify - '''is a pseudonym for "sha256,verify", option that performs a full comparison of every incoming block with any alleged duplicate to ensure that they really are the same		**'''Verify - '''is a pseudonym for "sha256,verify", option that performs a full comparison of every incoming block with any alleged duplicate to ensure that they really are the same

migrate>Ja-S at 22:22, 24 April 2019

2019-04-24T22:22:16Z

← Older revision		Revision as of 22:22, 24 April 2019
Line 4:		Line 4:
	*'''Size''' - Size of the new Zvol. The unit for this values is '''GiB (Gibibyte).'''<br/>In general, if you multiply 1024 ·1024 ·1024 = 1 073 741 824b, the result is equal to 2<sup>30</sup>.<br/>For example, 1 GiB = 1024 × 1 MiB = 1024 × 1024 × 1 KiB = 1024 × 1024 × 1024 × 1 B = 1 073 741 824 ~ 1070 GB		*'''Size''' - Size of the new Zvol. The unit for this values is '''GiB (Gibibyte).'''<br/>In general, if you multiply 1024 ·1024 ·1024 = 1 073 741 824b, the result is equal to 2<sup>30</sup>.<br/>For example, 1 GiB = 1024 × 1 MiB = 1024 × 1024 × 1 KiB = 1024 × 1024 × 1024 × 1 B = 1 073 741 824 ~ 1070 GB

	'''Provisioning''':'''Thin provisioned -''' involves using virtualization technology to give the appearance of having more physical resources than are actually available. Use this format to save storage space. For the thin disk, you provision as much datastore space as the disk would require based on the value that you enter for the disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations.		*'''Provisioning''':
			**'''Thin provisioned -''' involves using virtualization technology to give the appearance of having more physical resources than are actually available. Use this format to save storage space. For the thin disk, you provision as much datastore space as the disk would require based on the value that you enter for the disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations.
	**'''Thick provisioned (default)''' - creates a virtual disk in a thick format. Space required for the virtual disk is allocated when the virtual disk is created. Data remaining on the physical device is not erased during creation.		**'''Thick provisioned (default)''' - creates a virtual disk in a thick format. Space required for the virtual disk is allocated when the virtual disk is created. Data remaining on the physical device is not erased during creation.

	*'''Deduplication''':		'''Deduplication''':'''Disabled (default)'''
	**'''Disabled (default)'''
	**'''On - '''is a pseudonym for "sha256"		**'''On - '''is a pseudonym for "sha256"
	**'''Verify - '''is a pseudonym for "sha256,verify", option that performs a full comparison of every incoming block with any alleged duplicate to ensure that they really are the same		**'''Verify - '''is a pseudonym for "sha256,verify", option that performs a full comparison of every incoming block with any alleged duplicate to ensure that they really are the same

migrate>Ja-S at 22:21, 24 April 2019

2019-04-24T22:21:13Z

← Older revision		Revision as of 22:21, 24 April 2019
Line 7:		Line 7:
	**'''Thick provisioned (default)''' - creates a virtual disk in a thick format. Space required for the virtual disk is allocated when the virtual disk is created. Data remaining on the physical device is not erased during creation.		**'''Thick provisioned (default)''' - creates a virtual disk in a thick format. Space required for the virtual disk is allocated when the virtual disk is created. Data remaining on the physical device is not erased during creation.

	'''Deduplication''':'''Disabled (default)'''		*'''Deduplication''':
			**'''Disabled (default)'''
	**'''On - '''is a pseudonym for "sha256"		**'''On - '''is a pseudonym for "sha256"
	**'''Verify - '''is a pseudonym for "sha256,verify", option that performs a full comparison of every incoming block with any alleged duplicate to ensure that they really are the same		**'''Verify - '''is a pseudonym for "sha256,verify", option that performs a full comparison of every incoming block with any alleged duplicate to ensure that they really are the same

Ma-W at 13:25, 14 February 2019

2019-02-14T13:25:55Z

← Older revision		Revision as of 13:25, 14 February 2019
Line 18:		Line 18:
	**'''3'''		**'''3'''

	*~~<span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif">~~'''Compression - '''there are several data compression methods - You will see all available methods on the drop-down list. The default compression method is '''lz4'''''.''You can also choose no compression ''('''''None''').~~</span></span>~~		*'''Compression - '''there are several data compression methods - You will see all available methods on the drop-down list. The default compression method is '''lz4'''''.''You can also choose no compression ''('''''None''').
	**~~<span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif"><span style="line-height: 18px">~~'''gzip''', the standard levels of 1 through 9 are supported, where 1 is as fast as possible, with the least compression, and 9 is as compressed as possible, taking as much time as necessary.~~</span></span></span>~~		**'''gzip''', the standard levels of 1 through 9 are supported, where 1 is as fast as possible, with the least compression, and 9 is as compressed as possible, taking as much time as necessary.
	**~~<span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif"><span style="line-height: 18px">~~'''lzjb''' -  is a fast method with tight compression ratios, which is standard with most Lempel-Ziv algorithms. LZJB seems to provide the best all around results in terms of performance and compression.~~</span></span></span>~~		**'''lzjb''' -  is a fast method with tight compression ratios, which is standard with most Lempel-Ziv algorithms. LZJB seems to provide the best all around results in terms of performance and compression.
	**~~<span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif"><span style="line-height: 18px">~~'''zle''' is a very fast compression method, with very light compression ratios.~~</span></span></span>~~		**'''zle''' is a very fast compression method, with very light compression ratios.
	**~~<span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif"><span style="line-height: 18px">~~'''lz4''' - is intended as a faster and smarter replacement for lzjb~~</span></span></span>~~		**'''lz4''' - is intended as a faster and smarter replacement for lzjb
	*~~<span style="font-size:small"><span style="line-height: 18px"></span>~~'''Volume block size  - '''~~s<span style="color: rgb(0, 0, 0)">pecifies~~ the block size of the volume. The block size ~~</span><span style="color: rgb(0, 0, 0)">~~cannot be changed once the volume has been written, so it should be set at volume creation time. ~~</span></span>~~''''''~~T<span style="font-size: small">he~~ default value is '''128'''~~</span><span style="font-size: small">~~ ~~</span>~~'''KiB. '''<br/~~><span style="font-size: small"~~>The value can be changed. You can choose between : 4; 8; 16; 32; 64; 128, 256; 512 [KiB] and 1 [MB].~~</span>~~		*'''Volume block size  - '''specifies the block size of the volume. The block size cannot be changed once the volume has been written, so it should be set at volume creation time. ''''''The default value is '''128''' '''KiB. '''<br/>The value can be changed. You can choose between : 4; 8; 16; 32; 64; 128, 256; 512 [KiB] and 1 [MB].
	*~~<span style="font-size:small">~~'''Write cache logging (sync) '''- you can choose from three options :~~</span>~~		*'''Write cache logging (sync) '''- you can choose from three options :
	**~~<span style="font-size:small">~~'''always (default)'''~~</span>~~		**'''always (default)'''
	**~~<span style="font-size:small">~~'''standard'''~~</span>~~		**'''standard'''
	**~~<span style="font-size:small">~~'''disabled'''~~</span>~~		**'''disabled'''
	*'''~~<span style="font-size:small">Write~~ cache logging (log bias) ~~</span>~~'''-''' '''~~<span style="font-size: small"><span style="font-family:arial,helvetica,sans-serif">~~Use this property to provide a hint to system about handling synchronous requests for a specific dataset. If ~~</span></span><span style="font-family: arial, helvetica, sans-serif; font-size: small">~~logbias~~</span><span style="font-size: small; font-family: arial, helvetica, sans-serif">~~ is set to '''Write log device (latency)''',~~</span><font style="font-size: small" face="arial, helvetica, sans-serif">~~ JovianDSS uses the pool's separate log devices, if any, to handle the requests at low latency. If ~~</font><span style="font-family: arial, helvetica, sans-serif; font-size: small">~~logbias ~~</span><font style="font-size: small" face="arial, helvetica, sans-serif">~~is set to '''In pool (throughput)'''~~</font><font style="font-size: small" face="arial, helvetica, sans-serif">~~, the system does not use the pool's separate log devices. Instead, JovianDSS optimizes synchronous operations for global pool throughput and efficient use of resources. The default value is Write log device (~~</font><span style="font-family: arial, helvetica, sans-serif; font-size: small">~~latency)~~</span><font style="font-size: small" face="arial, helvetica, sans-serif">~~. For most configurations, the default value is recommended.~~ </font>~~		*'''Write cache logging (log bias) '''-''' '''Use this property to provide a hint to system about handling synchronous requests for a specific dataset. If logbias is set to '''Write log device (latency)''', JovianDSS uses the pool's separate log devices, if any, to handle the requests at low latency. If logbias is set to '''In pool (throughput)''', the system does not use the pool's separate log devices. Instead, JovianDSS optimizes synchronous operations for global pool throughput and efficient use of resources. The default value is Write log device (latency). For most configurations, the default value is recommended.

	*~~<span style="font-size:small"><span style="font-family:arial,helvetica,sans-serif">~~'''Primary cache '''- ~~<span style="color: rgb(0, 0, 0)">~~Controls what is cached in the primary cache (ARC). If this ~~prop</span><span style="color: rgb(0, 0, 0)">erty~~ is set to "All", then both user data and metadata is cached.~~</span><span style="color: rgb(0, 0, 0)">~~If this property is set to "None", then neither user data nor ~~metad</span><span style="color: rgb(0, 0, 0)">ata~~ is cached. If this property is set to "Metadata", then only~~</span><span style="color: rgb(0, 0, 0)">~~ metadata is cached. The default value is "All".~~</span></span></span>~~		*'''Primary cache '''- Controls what is cached in the primary cache (ARC). If this property is set to "All", then both user data and metadata is cached. If this property is set to "None", then neither user data nor metadata is cached. If this property is set to "Metadata", then only metadata is cached. The default value is "All".
	*~~<span style="font-family:arial,helvetica,sans-serif"><span style="font-size:small">~~'''Secondary cache '''- ~~<span style="color: rgb(0, 0, 0)">~~Controls what is cached in the secondary cache (L2ARC). If this~~</span><span style="color: rgb(0, 0, 0)">~~ property is set to "All", then both user data and metadata is ~~</span><span style="color: rgb(0, 0, 0)">~~cached. If this property is set to "None", then neither user data~~</span><span style="color: rgb(0, 0, 0)">~~ nor metadata is cached. If this property is set to "Metadata", then only metadata is cached. The default value is "All".~~</span></span></span>~~		*'''Secondary cache '''- Controls what is cached in the secondary cache (L2ARC). If this property is set to "All", then both user data and metadata is cached. If this property is set to "None", then neither user data nor metadata is cached. If this property is set to "Metadata", then only metadata is cached. The default value is "All".

	<span style="font-size: small; font-family: arial, helvetica, sans-serif; color: rgb(0, 0, 0)"></span><span style="color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: small">You can attach this newly created zvol to a target. To do that, you have to:~~</span>~~		You can attach this newly created zvol to a target. To do that, you have to:

	*~~<span style="color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: small">~~choose one of the existing '''Target '''~~</span><span style="color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: small">~~names~~</span>~~		*choose one of the existing '''Target ''' names
	*~~<span style="color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: small">~~define the '''SCSI ID '''~~</span><span style="color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: small">~~for the target (you can generate a random SCSI ID number by clicking '''Generate''' button) ~~</span>~~		*define the '''SCSI ID ''' for the target (you can generate a random SCSI ID number by clicking '''Generate''' button)
	*~~<span style="color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: small">~~define the '''LUN '''~~</span><span style="color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: small">~~for the target~~</span>~~		*define the '''LUN '''for the target
	*~~<span style="color: rgb(0, 0, 0); font-family: arial, helvetica, sans-serif; font-size: small">~~'''Access mode '''for the target - the default is '''Read-Write, '''You can choose the '''Read-Only '''option~~</span>~~		*'''Access mode '''for the target - the default is '''Read-Write, '''You can choose the '''Read-Only '''option


	~~<div></div>~~
	[[Category:Help topics]]		[[Category:Help topics]]

Ma-W at 15:55, 13 February 2019

2019-02-13T15:55:35Z

← Older revision		Revision as of 15:55, 13 February 2019
Line 2:		Line 2:

	*'''Name''' - Name of the new Zvol		*'''Name''' - Name of the new Zvol
	*'''Size''' - Size of the new Zvol. The unit for this values is '''GiB (Gibibyte).'''<br/>In general, if you multiply 1024 ·1024 ·1024 = 1 073 741 824b, the result is equal to ~~230~~.<br/>For example, 1 GiB = 1024 × 1 MiB = 1024 × 1024 × 1 KiB = 1024 × 1024 × 1024 × 1 B = 1 073 741 824 ~ 1070 GB		*'''Size''' - Size of the new Zvol. The unit for this values is '''GiB (Gibibyte).'''<br/>In general, if you multiply 1024 ·1024 ·1024 = 1 073 741 824b, the result is equal to 2<sup>30</sup>.<br/>For example, 1 GiB = 1024 × 1 MiB = 1024 × 1024 × 1 KiB = 1024 × 1024 × 1024 × 1 B = 1 073 741 824 ~ 1070 GB

	'''Provisioning''':'''Thin provisioned -''' involves using virtualization technology to give the appearance of having more physical resources than are actually available. Use this format to save storage space. For the thin disk, you provision as much datastore space as the disk would require based on the value that you enter for the disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations.		'''Provisioning''':'''Thin provisioned -''' involves using virtualization technology to give the appearance of having more physical resources than are actually available. Use this format to save storage space. For the thin disk, you provision as much datastore space as the disk would require based on the value that you enter for the disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations.

Ma-W at 15:55, 13 February 2019

2019-02-13T15:55:13Z

← Older revision		Revision as of 15:55, 13 February 2019
Line 2:		Line 2:

	*'''Name''' - Name of the new Zvol		*'''Name''' - Name of the new Zvol
	*'''Size''' - Size of the new Zvol. The unit for this values is '''GiB (Gibibyte).'''		*'''Size''' - Size of the new Zvol. The unit for this values is '''GiB (Gibibyte).'''<br/>In general, if you multiply 1024 ·1024 ·1024 = 1 073 741 824b, the result is equal to 230.<br/>For example, 1 GiB = 1024 × 1 MiB = 1024 × 1024 × 1 KiB = 1024 × 1024 × 1024 × 1 B = 1 073 741 824 ~ 1070 GB

	In general, if you multiply 1024 ·1024 ·1024 = 1 073 741 824b, the result is equal to 230.<br/>For example, 1 GiB = 1024 × 1 MiB = 1024 × 1024 × 1 KiB = 1024 × 1024 × 1024 × 1 B = 1 073 741 824 ~ 1070 GB

	'''Provisioning''':'''Thin provisioned -''' involves using virtualization technology to give the appearance of having more physical resources than are actually available. Use this format to save storage space. For the thin disk, you provision as much datastore space as the disk would require based on the value that you enter for the disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations.		'''Provisioning''':'''Thin provisioned -''' involves using virtualization technology to give the appearance of having more physical resources than are actually available. Use this format to save storage space. For the thin disk, you provision as much datastore space as the disk would require based on the value that you enter for the disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations.