Docs: update the devicemapper default basesize from 10G to 100G

Signed-off-by: Lei Jitang <leijitang@huawei.com>
This commit is contained in:
Lei 2015-07-21 20:46:31 +08:00 committed by Tibor Vass
parent c9cf4a479a
commit ba3e24187c
2 changed files with 6 additions and 6 deletions

View File

@ -201,9 +201,9 @@ options for `zfs` start with `zfs`.
* `dm.basesize` * `dm.basesize`
Specifies the size to use when creating the base device, which limits the Specifies the size to use when creating the base device, which limits the
size of images and containers. The default value is 10G. Note, thin devices size of images and containers. The default value is 100G. Note, thin devices
are inherently "sparse", so a 10G device which is mostly empty doesn't use are inherently "sparse", so a 100G device which is mostly empty doesn't use
10 GB of space on the pool. However, the filesystem will use more space for 100 GB of space on the pool. However, the filesystem will use more space for
the empty case the larger the device is. the empty case the larger the device is.
This value affects the system-wide "base" empty filesystem This value affects the system-wide "base" empty filesystem

View File

@ -342,9 +342,9 @@ Example use: `docker -d --storage-opt dm.thinpooldev=/dev/mapper/thin-pool`
#### dm.basesize #### dm.basesize
Specifies the size to use when creating the base device, which limits Specifies the size to use when creating the base device, which limits
the size of images and containers. The default value is 10G. Note, the size of images and containers. The default value is 100G. Note,
thin devices are inherently "sparse", so a 10G device which is mostly thin devices are inherently "sparse", so a 100G device which is mostly
empty doesn't use 10 GB of space on the pool. However, the filesystem empty doesn't use 100 GB of space on the pool. However, the filesystem
will use more space for base images the larger the device will use more space for base images the larger the device
is. is.