Lines Matching +full:data +full:- +full:mirror
1 # SPDX-License-Identifier: GPL-2.0-only
30 Software RAID mini-HOWTO, available from
45 a several-second delay in the boot time due to various
55 use the so-called linear mode, i.e. it will combine the hard disk
64 tristate "RAID-0 (striping) mode"
68 use the so-called raid0 mode, i.e. it will combine the hard disk
74 Software-RAID mini-HOWTO, available from
84 tristate "RAID-1 (mirroring) mode"
87 A RAID-1 set consists of several disk drives which are exact copies
88 of each other. In the event of a mirror failure, the RAID driver
92 of a single drive, and the set protects against a failure of (N - 1)
96 Software-RAID mini-HOWTO, available from
100 If you want to use such a RAID-1 set, say Y. To compile this code
106 tristate "RAID-10 (mirrored striping) mode"
109 RAID-10 provides a combination of striping (RAID-0) and
110 mirroring (RAID-1) with easier configuration and more flexible
112 Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
115 RAID-10 provides a variety of layouts that provide different levels
118 RAID-10 requires mdadm-1.7.0 or later, available at:
125 tristate "RAID-4/RAID-5/RAID-6 mode"
134 A RAID-5 set of N drives with a capacity of C MB per drive provides
135 the capacity of C * (N - 1) MB, and protects against a failure
136 of a single drive. For a given sector (row) number, (N - 1) drives
137 contain data sectors, and one drive contains the parity protection.
138 For a RAID-4 set, the parity blocks are present on a single drive,
139 while a RAID-5 set distributes the parity across the drives in one
142 A RAID-6 set of N drives with a capacity of C MB per drive
143 provides the capacity of C * (N - 2) MB, and protects
145 (row) number, (N - 2) drives contain data sectors, and two
147 RAID-5, RAID-6 distributes the syndromes across the drives
151 Software-RAID mini-HOWTO, available from
155 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
165 MD_MULTIPATH provides a simple multi-path personality for use
209 Device-mapper is a low level volume manager. It works by allowing
217 called dm-mod.
225 Enable this for messages that may help debug device-mapper problems.
234 as a cache, holding recently-read blocks in memory and performing
246 bool "Keep stack trace of persistent data block lock holders"
259 Some bio locking schemes used by other device-mapper targets
262 source "drivers/md/persistent-data/Kconfig"
269 RAID0 or dm-striped target.
280 This device-mapper target allows you to create a device that
281 transparently encrypts the data on it. You'll need to activate
284 For further information on dm-crypt and userspace tools see:
288 be called dm-crypt.
305 Provides thin provisioning and snapshots that share a data store.
314 dm-cache attempts to improve performance of a block device by
315 moving frequently used data to a smaller, higher performance
348 dm-ebs emulates smaller logical block size on backing devices
358 dm-era tracks which parts of a block device are written to
368 dm-clone produces a one-to-one copy of an existing, read-only source
377 tristate "Mirror target"
380 Allow volume managers to mirror logical volumes, also
381 needed for live data migration tools such as 'pvmove'.
384 tristate "Mirror userspace logging"
389 relaying the dm-dirty-log API to userspace. Log designs
405 A RAID-5 set of N drives with a capacity of C MB per drive provides
406 the capacity of C * (N - 1) MB, and protects against a failure
407 of a single drive. For a given sector (row) number, (N - 1) drives
408 contain data sectors, and one drive contains the parity protection.
409 For a RAID-4 set, the parity blocks are present on a single drive,
410 while a RAID-5 set distributes the parity across the drives in one
413 A RAID-6 set of N drives with a capacity of C MB per drive
414 provides the capacity of C * (N - 2) MB, and protects
416 (row) number, (N - 2) drives contain data sectors, and two
418 RAID-5, RAID-6 distributes the syndromes across the drives
440 tristate "I/O Path Selector based on the number of in-flight I/Os"
444 the path with the least number of in-flight I/Os.
497 bool "DM \"dm-mod.create=\" parameter support"
500 Enable "dm-mod.create=" parameter to create mapped devices at init time.
503 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
527 This device-mapper target creates a read-only device that
528 transparently validates the data on one underlying device against
529 a pre-generated tree of cryptographic checksums stored on a second
536 be called dm-verity.
542 bool "Verity data device root hash signature verification support"
546 Add ability for dm-verity device to be validated if the
547 pre-generated tree of cryptographic checksums passed has a pkcs#7
555 bool "Verity data device root hash signature verification with secondary keyring"
559 Rely on the secondary trusted keyring to verify dm-verity signatures.
569 Add forward error correction support to dm-verity. This option
570 makes it possible to use pre-generated error correction data to
579 This device-mapper target creates a device that supports an arbitrary
580 mapping of fixed-size regions of I/O across a fixed set of paths.
585 be called dm-switch.
593 This device-mapper target takes two devices, one device to use
601 be called dm-log-writes.
614 This device-mapper target emulates a block device that has
615 additional per-sector tags that can be used for storing
618 This integrity target is used with the dm-crypt target to
623 be called dm-integrity.
626 tristate "Drive-managed zoned block device target support"
631 This device-mapper target takes a host-managed or host-aware zoned
633 device (drive-managed zoned block device) without any write
641 be called dm-zoned.