Lines Matching +full:data +full:- +full:mirror
1 # SPDX-License-Identifier: GPL-2.0-only
29 Software RAID mini-HOWTO, available from
44 a several-second delay in the boot time due to various
54 use the so-called linear mode, i.e. it will combine the hard disk
63 tristate "RAID-0 (striping) mode"
67 use the so-called raid0 mode, i.e. it will combine the hard disk
73 Software-RAID mini-HOWTO, available from
83 tristate "RAID-1 (mirroring) mode"
86 A RAID-1 set consists of several disk drives which are exact copies
87 of each other. In the event of a mirror failure, the RAID driver
91 of a single drive, and the set protects against a failure of (N - 1)
95 Software-RAID mini-HOWTO, available from
99 If you want to use such a RAID-1 set, say Y. To compile this code
105 tristate "RAID-10 (mirrored striping) mode"
108 RAID-10 provides a combination of striping (RAID-0) and
109 mirroring (RAID-1) with easier configuration and more flexible
111 Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
114 RAID-10 provides a variety of layouts that provide different levels
117 RAID-10 requires mdadm-1.7.0 or later, available at:
124 tristate "RAID-4/RAID-5/RAID-6 mode"
133 A RAID-5 set of N drives with a capacity of C MB per drive provides
134 the capacity of C * (N - 1) MB, and protects against a failure
135 of a single drive. For a given sector (row) number, (N - 1) drives
136 contain data sectors, and one drive contains the parity protection.
137 For a RAID-4 set, the parity blocks are present on a single drive,
138 while a RAID-5 set distributes the parity across the drives in one
141 A RAID-6 set of N drives with a capacity of C MB per drive
142 provides the capacity of C * (N - 2) MB, and protects
144 (row) number, (N - 2) drives contain data sectors, and two
146 RAID-5, RAID-6 distributes the syndromes across the drives
150 Software-RAID mini-HOWTO, available from
154 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
164 MD_MULTIPATH provides a simple multi-path personality for use
207 Device-mapper is a low level volume manager. It works by allowing
215 called dm-mod.
223 Enable this for messages that may help debug device-mapper problems.
232 as a cache, holding recently-read blocks in memory and performing
244 bool "Keep stack trace of persistent data block lock holders"
257 Some bio locking schemes used by other device-mapper targets
260 source "drivers/md/persistent-data/Kconfig"
267 RAID0 or dm-striped target.
277 This device-mapper target allows you to create a device that
278 transparently encrypts the data on it. You'll need to activate
281 For further information on dm-crypt and userspace tools see:
285 be called dm-crypt.
302 Provides thin provisioning and snapshots that share a data store.
311 dm-cache attempts to improve performance of a block device by
312 moving frequently used data to a smaller, higher performance
345 dm-ebs emulates smaller logical block size on backing devices
355 dm-era tracks which parts of a block device are written to
365 dm-clone produces a one-to-one copy of an existing, read-only source
374 tristate "Mirror target"
377 Allow volume managers to mirror logical volumes, also
378 needed for live data migration tools such as 'pvmove'.
381 tristate "Mirror userspace logging"
386 relaying the dm-dirty-log API to userspace. Log designs
402 A RAID-5 set of N drives with a capacity of C MB per drive provides
403 the capacity of C * (N - 1) MB, and protects against a failure
404 of a single drive. For a given sector (row) number, (N - 1) drives
405 contain data sectors, and one drive contains the parity protection.
406 For a RAID-4 set, the parity blocks are present on a single drive,
407 while a RAID-5 set distributes the parity across the drives in one
410 A RAID-6 set of N drives with a capacity of C MB per drive
411 provides the capacity of C * (N - 2) MB, and protects
413 (row) number, (N - 2) drives contain data sectors, and two
415 RAID-5, RAID-6 distributes the syndromes across the drives
437 tristate "I/O Path Selector based on the number of in-flight I/Os"
441 the path with the least number of in-flight I/Os.
485 bool "DM \"dm-mod.create=\" parameter support"
488 Enable "dm-mod.create=" parameter to create mapped devices at init time.
491 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
515 This device-mapper target creates a read-only device that
516 transparently validates the data on one underlying device against
517 a pre-generated tree of cryptographic checksums stored on a second
524 be called dm-verity.
530 bool "Verity data device root hash signature verification support"
534 Add ability for dm-verity device to be validated if the
535 pre-generated tree of cryptographic checksums passed has a pkcs#7
546 Add forward error correction support to dm-verity. This option
547 makes it possible to use pre-generated error correction data to
556 This device-mapper target creates a device that supports an arbitrary
557 mapping of fixed-size regions of I/O across a fixed set of paths.
562 be called dm-switch.
570 This device-mapper target takes two devices, one device to use
578 be called dm-log-writes.
590 This device-mapper target emulates a block device that has
591 additional per-sector tags that can be used for storing
594 This integrity target is used with the dm-crypt target to
599 be called dm-integrity.
602 tristate "Drive-managed zoned block device target support"
606 This device-mapper target takes a host-managed or host-aware zoned
608 device (drive-managed zoned block device) without any write
616 be called dm-zoned.