Lines Matching refs:metadata

23 - Improve metadata resilience by storing metadata on a mirrored volume
26 - Improve performance by storing the metadata on SSD.
39 Userspace tools for checking and repairing the metadata have been fully
55 The pool device ties together the metadata volume and the data volume.
56 It maps I/O linearly to the data volume and updates the metadata via
67 Setting up a pool device requires a valid metadata device, and a
68 data device.  If you do not have an existing metadata device you can
69 make one by zeroing the first 4k to indicate empty metadata.
73 The amount of metadata you need will vary according to how many blocks
75 less sharing than average you'll need a larger-than-average metadata device.
78 metadata device as 48 * $data_dev_size / $data_block_size but round it up
90 if it runs out of space.  (N.B. While specifying a different metadata
122 A low water mark for the metadata device is maintained in the kernel and
123 will trigger a dm event if free space on the metadata device drops below
126 Updating on-disk metadata
129 On-disk metadata is committed every time a FLUSH or FUA bio is written.
133 writes.  The metadata should always be consistent in spite of any crash.
136 according to the configuration (see: error_if_no_space).  If metadata
137 space is exhausted or a metadata operation fails: the pool will error IO
140 Once the pool's metadata device is repaired it may be resized, which
142 is flagged as needing repair, the pool's data and metadata devices
144 that when the pool's metadata space is exhausted the current metadata
255     thin-pool <metadata dev> <data dev> <data block size (sectors)> \
268 		 metadata.  This mode is only available after the
281     <transaction id> <used metadata blocks>/<total metadata blocks>
282     <used data blocks>/<total data blocks> <held metadata root>
287 	A 64-bit number used by userspace to help synchronise with metadata
296     held metadata root:
297 	The location, in blocks, of the metadata root that has been
308 	drop into a read-only metadata mode in which no changes to
309 	the pool metadata (like allocating new blocks) are permitted.
317 	If the pool runs out of data or metadata space, the pool will
325 	A metadata operation has failed, resulting in the needs_check
326 	flag being set in the metadata's superblock.  The metadata
332 	Value of metadata low watermark in blocks.  The kernel sets this
359 	synchronise their external metadata with the internal metadata of the
371         get the root block associated with the metadata snapshot.