Lines Matching refs:metadata

23 - Improve metadata resilience by storing metadata on a mirrored volume
26 - Improve performance by storing the metadata on SSD.
40 Userspace tools for checking and repairing the metadata are under
54 The pool device ties together the metadata volume and the data volume.
55 It maps I/O linearly to the data volume and updates the metadata via
66 Setting up a pool device requires a valid metadata device, and a
67 data device.  If you do not have an existing metadata device you can
68 make one by zeroing the first 4k to indicate empty metadata.
72 The amount of metadata you need will vary according to how many blocks
74 less sharing than average you'll need a larger-than-average metadata device.
77 metadata device as 48 * $data_dev_size / $data_block_size but round it up
89 if it runs out of space.  (N.B. While specifying a different metadata
119 A low water mark for the metadata device is maintained in the kernel and
120 will trigger a dm event if free space on the metadata device drops below
123 Updating on-disk metadata
126 On-disk metadata is committed every time a FLUSH or FUA bio is written.
130 writes.  The metadata should always be consistent in spite of any crash.
133 according to the configuration (see: error_if_no_space).  If metadata
134 space is exhausted or a metadata operation fails: the pool will error IO
137 Once the pool's metadata device is repaired it may be resized, which
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
252     thin-pool <metadata dev> <data dev> <data block size (sectors)> \
265 		 metadata.
275     <transaction id> <used metadata blocks>/<total metadata blocks>
276     <used data blocks>/<total data blocks> <held metadata root>
280 	A 64-bit number used by userspace to help synchronise with metadata
289     held metadata root:
290 	The location, in blocks, of the metadata root that has been
301 	drop into a read-only metadata mode in which no changes to
302 	the pool metadata (like allocating new blocks) are permitted.
310 	If the pool runs out of data or metadata space, the pool will
318 	A metadata operation has failed, resulting in the needs_check
319 	flag being set in the metadata's superblock.  The metadata
347 	synchronise their external metadata with the internal metadata of the
359         get the root block associated with the metadata snapshot.