Lines Matching full:metadata
29 The dm-clone target reuses the metadata library used by the thin-provisioning
58 3. A small metadata device - it records which regions are already valid in the
95 only updates its metadata.
124 Updating on-disk metadata
127 On-disk metadata is committed every time a FLUSH or FUA bio is written. If no
130 power is lost you may lose some recent writes. The metadata should always be
141 clone <metadata dev> <destination dev> <source dev> <region size>
145 metadata dev Fast device holding the persistent metadata
184 <metadata block size> <#used metadata blocks>/<#total metadata blocks>
187 <clone metadata mode>
190 metadata block size Fixed block size for each metadata block in sectors
191 #used metadata blocks Number of metadata blocks used
192 #total metadata blocks Total number of metadata blocks
202 clone metadata mode ro if read-only, rw if read-write
206 will just contain the string 'Fail'. If the metadata
261 The metadata device is no longer needed and can be safely discarded or reused
301 * dm-snapshot stores its metadata in the COW device, so the resulting device
306 * dm-snapshot needs to commit its metadata whenever a pending exception
308 need to be so strict and can rely on committing metadata every time a FLUSH
327 thinly-provisioned volumes. Thin-provisioning has an inherent metadata