Signed-off-by: Lei Jitang <leijitang@huawei.com>
| ... | ... |
@@ -201,9 +201,9 @@ options for `zfs` start with `zfs`. |
| 201 | 201 |
* `dm.basesize` |
| 202 | 202 |
|
| 203 | 203 |
Specifies the size to use when creating the base device, which limits the |
| 204 |
- size of images and containers. The default value is 10G. Note, thin devices |
|
| 205 |
- are inherently "sparse", so a 10G device which is mostly empty doesn't use |
|
| 206 |
- 10 GB of space on the pool. However, the filesystem will use more space for |
|
| 204 |
+ size of images and containers. The default value is 100G. Note, thin devices |
|
| 205 |
+ are inherently "sparse", so a 100G device which is mostly empty doesn't use |
|
| 206 |
+ 100 GB of space on the pool. However, the filesystem will use more space for |
|
| 207 | 207 |
the empty case the larger the device is. |
| 208 | 208 |
|
| 209 | 209 |
This value affects the system-wide "base" empty filesystem |
| ... | ... |
@@ -342,9 +342,9 @@ Example use: `docker -d --storage-opt dm.thinpooldev=/dev/mapper/thin-pool` |
| 342 | 342 |
#### dm.basesize |
| 343 | 343 |
|
| 344 | 344 |
Specifies the size to use when creating the base device, which limits |
| 345 |
-the size of images and containers. The default value is 10G. Note, |
|
| 346 |
-thin devices are inherently "sparse", so a 10G device which is mostly |
|
| 347 |
-empty doesn't use 10 GB of space on the pool. However, the filesystem |
|
| 345 |
+the size of images and containers. The default value is 100G. Note, |
|
| 346 |
+thin devices are inherently "sparse", so a 100G device which is mostly |
|
| 347 |
+empty doesn't use 100 GB of space on the pool. However, the filesystem |
|
| 348 | 348 |
will use more space for base images the larger the device |
| 349 | 349 |
is. |
| 350 | 350 |
|