Lines Matching full:thin
2 Thin provisioning
9 between them implement thin-provisioning and snapshots.
51 This section describes some quick recipes for using thin provisioning.
63 - Function calls from the thin targets
78 are shared between thin devices (i.e. through snapshots). If you have
105 --table "0 20971520 thin-pool $metadata_dev $data_dev \
112 thin-pool is created. People primarily interested in thin provisioning
137 means the thin-provisioning target behaves like a physical disk that has
157 Thin provisioning
173 Thinly-provisioned volumes are activated using the 'thin' target::
175 dmsetup create thin --table "0 2097152 thin /dev/mapper/pool 0"
192 dmsetup suspend /dev/mapper/thin
194 dmsetup resume /dev/mapper/thin
211 dmsetup create snap --table "0 2097152 thin /dev/mapper/pool 1"
218 thin device will be passed through to the origin. Writes trigger
226 Of course, you may write to the thin device and take internal snapshots
227 of the thin volume.
231 This is the same as creating a thin device.
240 Append an extra parameter to the thin target specifying the origin::
242 dmsetup create snap --table "0 2097152 thin /dev/mapper/pool 0 /dev/image"
255 dmsetup remove thin
262 'thin-pool' target
269 thin-pool <metadata dev> <data dev> <data block size (sectors)> \
287 thin-pool has been created and first used in full
289 thin-pool creation.
341 'no_space_timeout' expires. The 'no_space_timeout' dm-thin-pool
349 thin-pool can be made fully operational again. '-' indicates
372 Deletes a thin device. Irreversible.
377 pool target. The thin-pool target offers to store an
392 'thin' target
399 thin <pool dev> <dev id> [<external origin dev>]
402 the thin-pool device, e.g. /dev/mapper/my_pool or 253:0
411 thin target will be mapped to this device.
413 The pool doesn't store any size against the thin devices. If you
414 load a thin target that is smaller than you've been using previously,