Alexander Larsson 17a97293a6 devmapper: Use a smaller blocksize for the thin-pool ...

As per the thin provisioning docs for creating the pool:

   $data_block_size gives the smallest unit of disk space that can be
   allocated at a time expressed in units of 512-byte sectors.
   $data_block_size must be between 128 (64KB) and 2097152 (1GB) and a
   multiple of 128 (64KB). $data_block_size cannot be changed after the
   thin-pool is created. People primarily interested in thin provisioning
   may want to use a value such as 1024 (512KB). People doing lots of
   snapshotting may want a smaller value such as 128 (64KB).

The switch from 512 (which we used before) to 128 (recommended above
for lots of snapshoting) means a simple container creation (based on the
mattdm/fedora:f19 image) adds 1 MB of diskspace rather than 3.6.
This seems more in tune with how docker is typically used.
Upstream-commit: 8abcc8e713fdf6229d65dec23e6e104f8040d704
Component: engine

2013-10-17 15:33:00 +02:00

..

docker-device-tool

devmapper: Add simple tool to test the DeviceSet commands

2013-09-26 15:08:54 +00:00

deviceset_devmapper.go

devmapper: error reporting workaround in waitRemove()

2013-10-17 01:49:51 +00:00

devmapper_log.go

device-mapper: Move all devicemapper spew to log through utils.Debugf().

2013-10-11 16:31:06 -07:00

devmapper.go

devmapper: Use a smaller blocksize for the thin-pool

2013-10-17 15:33:00 +02:00