1 files changed, 8 insertions, 7 deletions
diff --git a/Documentation/device-mapper/thin-provisioning.txt b/Documentation/device-mapper/thin-provisioning.txt
index 30b8b83bd333..50c44cf79b0e 100644
--- a/Documentation/device-mapper/thin-provisioning.txt
+++ b/Documentation/device-mapper/thin-provisioning.txt
@@ -99,13 +99,14 @@ Using an existing pool device
                 $data_block_size $low_water_mark"
 $data_block_size gives the smallest unit of disk space that can be
-allocated at a time expressed in units of 512-byte sectors.  People
+allocated at a time expressed in units of 512-byte sectors.
-primarily interested in thin provisioning may want to use a value such
+$data_block_size must be between 128 (64KB) and 2097152 (1GB) and a
-as 1024 (512KB).  People doing lots of snapshotting may want a smaller value
+multiple of 128 (64KB).  $data_block_size cannot be changed after the
-such as 128 (64KB).  If you are not zeroing newly-allocated data,
+thin-pool is created.  People primarily interested in thin provisioning
-a larger $data_block_size in the region of 256000 (128MB) is suggested.
+may want to use a value such as 1024 (512KB).  People doing lots of
-$data_block_size must be the same for the lifetime of the
+snapshotting may want a smaller value such as 128 (64KB).  If you are
-metadata device.
+not zeroing newly-allocated data, a larger $data_block_size in the
+region of 256000 (128MB) is suggested.
 $low_water_mark is expressed in blocks of size $data_block_size.  If
 free space on the data device drops below this level then a dm event

diff --git a/Documentation/device-mapper/thin-provisioning.txt b/Documentation/device-mapper/thin-provisioning.txt index 30b8b83bd333..50c44cf79b0e 100644 --- a/Documentation/device-mapper/thin-provisioning.txt +++ b/Documentation/device-mapper/thin-provisioning.txt
@@ -99,13 +99,14 @@ Using an existing pool device
99	$data_block_size $low_water_mark"	99	$data_block_size $low_water_mark"
100		100
101	$data_block_size gives the smallest unit of disk space that can be	101	$data_block_size gives the smallest unit of disk space that can be
102	allocated at a time expressed in units of 512-byte sectors. People	102	allocated at a time expressed in units of 512-byte sectors.
103	primarily interested in thin provisioning may want to use a value such	103	$data_block_size must be between 128 (64KB) and 2097152 (1GB) and a
104	as 1024 (512KB). People doing lots of snapshotting may want a smaller value	104	multiple of 128 (64KB). $data_block_size cannot be changed after the
105	such as 128 (64KB). If you are not zeroing newly-allocated data,	105	thin-pool is created. People primarily interested in thin provisioning
106	a larger $data_block_size in the region of 256000 (128MB) is suggested.	106	may want to use a value such as 1024 (512KB). People doing lots of
107	$data_block_size must be the same for the lifetime of the	107	snapshotting may want a smaller value such as 128 (64KB). If you are
108	metadata device.	108	not zeroing newly-allocated data, a larger $data_block_size in the
		109	region of 256000 (128MB) is suggested.
109		110
110	$low_water_mark is expressed in blocks of size $data_block_size. If	111	$low_water_mark is expressed in blocks of size $data_block_size. If
111	free space on the data device drops below this level then a dm event	112	free space on the data device drops below this level then a dm event