Lines Matching refs:pool

54 The pool device ties together the metadata volume and the data volume.
63 Setting up a fresh pool device
66 Setting up a pool device requires a valid metadata device, and a
85 Reloading a pool table
88 You may reload a pool's table, indeed this is how the pool is resized
94 Using an existing pool device
97     dmsetup create pool \
98 	--table "0 20971520 thin-pool $metadata_dev $data_dev \
105 thin-pool is created.  People primarily interested in thin provisioning
114 extend the pool device.  Only one such event will be sent.
132 If data space is exhausted the pool will either error or queue IO
134 space is exhausted or a metadata operation fails: the pool will error IO
135 until the pool is taken offline and repair is performed to 1) fix any
137 Once the pool's metadata device is repaired it may be resized, which
138 will allow the pool to return to normal operation.  Note that if a pool
139 is flagged as needing repair, the pool's data and metadata devices
141 that when the pool's metadata space is exhausted the current metadata
142 transaction is aborted.  Given that the pool will cache IO whose
145 (e.g. fsck) be performed on those layers when repair of the pool is
154   active pool device, /dev/mapper/pool in this example.
156     dmsetup message /dev/mapper/pool 0 "create_thin 0"
166     dmsetup create thin --table "0 2097152 thin /dev/mapper/pool 0"
175   Snapshots are created with another message to the pool.
182     dmsetup message /dev/mapper/pool 0 "create_snap 1 0"
200     dmsetup create snap --table "0 2097152 thin /dev/mapper/pool 1"
223     dmsetup message /dev/mapper/pool 0 "create_thin 0"
229     dmsetup create snap --table "0 2097152 thin /dev/mapper/pool 0 /dev/image"
237 All devices using a pool must be deactivated before the pool itself
242     dmsetup remove pool
247 'thin-pool' target
252     thin-pool <metadata dev> <data dev> <data block size (sectors)> \
264       read_only: Don't allow any changes to be made to the pool
284 	If the number of free blocks drops below the pool's low water mark a
300 	If the pool encounters certain types of device failures it will
302 	the pool metadata (like allocating new blocks) are permitted.
310 	If the pool runs out of data or metadata space, the pool will
313 	'no_space_timeout' expires.  The 'no_space_timeout' dm-thin-pool
321 	thin-pool can be made fully operational again.  '-' indicates
348 	pool target.  The thin-pool target offers to store an
358         this message was executed.  Use the pool's status command to
370     thin <pool dev> <dev id> [<external origin dev>]
372     pool dev:
373 	the thin-pool device, e.g. /dev/mapper/my_pool or 253:0
380 	an optional block device outside the pool to be treated as a
384 The pool doesn't store any size against the thin devices.  If you
394 	If the pool has encountered device errors and failed, the status