Lines Matching full:metadata

24 Metadata is stored on a separate device from data, giving the
27 - Improve metadata resilience by storing metadata on a mirrored volume
30 - Improve performance by storing the metadata on SSD.
43 Userspace tools for checking and repairing the metadata have been fully
59 The pool device ties together the metadata volume and the data volume.
60 It maps I/O linearly to the data volume and updates the metadata via
71 Setting up a pool device requires a valid metadata device, and a
72 data device.  If you do not have an existing metadata device you can
73 make one by zeroing the first 4k to indicate empty metadata.
77 The amount of metadata you need will vary according to how many blocks
79 less sharing than average you'll need a larger-than-average metadata device.
82 metadata device as 48 * $data_dev_size / $data_block_size but round it up
94 if it runs out of space.  (N.B. While specifying a different metadata
128 A low water mark for the metadata device is maintained in the kernel and
129 will trigger a dm event if free space on the metadata device drops below
132 Updating on-disk metadata
135 On-disk metadata is committed every time a FLUSH or FUA bio is written.
139 writes.  The metadata should always be consistent in spite of any crash.
142 according to the configuration (see: error_if_no_space).  If metadata
143 space is exhausted or a metadata operation fails: the pool will error IO
146 Once the pool's metadata device is repaired it may be resized, which
148 is flagged as needing repair, the pool's data and metadata devices
150 that when the pool's metadata space is exhausted the current metadata
269       thin-pool <metadata dev> <data dev> <data block size (sectors)> \
286 		 metadata.  This mode is only available after the
302       <transaction id> <used metadata blocks>/<total metadata blocks>
303       <used data blocks>/<total data blocks> <held metadata root>
308 	A 64-bit number used by userspace to help synchronise with metadata
317     held metadata root:
318 	The location, in blocks, of the metadata root that has been
329 	drop into a read-only metadata mode in which no changes to
330 	the pool metadata (like allocating new blocks) are permitted.
338 	If the pool runs out of data or metadata space, the pool will
346 	A metadata operation has failed, resulting in the needs_check
347 	flag being set in the metadata's superblock.  The metadata
353 	Value of metadata low watermark in blocks.  The kernel sets this
376 	synchronise their external metadata with the internal metadata of the
387         get the root block associated with the metadata snapshot.