Lines Matching +full:multi +full:- +full:cluster
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
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
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
183 tristate "Cluster Support for MD"
189 synchronization across multiple systems on the cluster, so all
190 nodes in the cluster can access the MD devices simultaneously.
193 nodes of the cluster. Currently, it can work with raid1 and raid10
210 Device-mapper is a low level volume manager. It works by allowing
218 called dm-mod.
226 Enable this for messages that may help debug device-mapper problems.
235 as a cache, holding recently-read blocks in memory and performing
260 Some bio locking schemes used by other device-mapper targets
263 source "drivers/md/persistent-data/Kconfig"
270 RAID0 or dm-striped target.
281 This device-mapper target allows you to create a device that
285 For further information on dm-crypt and userspace tools see:
289 be called dm-crypt.
315 dm-cache attempts to improve performance of a block device by
349 dm-ebs emulates smaller logical block size on backing devices
359 dm-era tracks which parts of a block device are written to
369 dm-clone produces a one-to-one copy of an existing, read-only source
390 relaying the dm-dirty-log API to userspace. Log designs
406 A RAID-5 set of N drives with a capacity of C MB per drive provides
407 the capacity of C * (N - 1) MB, and protects against a failure
408 of a single drive. For a given sector (row) number, (N - 1) drives
410 For a RAID-4 set, the parity blocks are present on a single drive,
411 while a RAID-5 set distributes the parity across the drives in one
414 A RAID-6 set of N drives with a capacity of C MB per drive
415 provides the capacity of C * (N - 2) MB, and protects
417 (row) number, (N - 2) drives contain data sectors, and two
419 RAID-5, RAID-6 distributes the syndromes across the drives
441 tristate "I/O Path Selector based on the number of in-flight I/Os"
445 the path with the least number of in-flight I/Os.
498 bool "DM \"dm-mod.create=\" parameter support"
501 Enable "dm-mod.create=" parameter to create mapped devices at init time.
504 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
528 This device-mapper target creates a read-only device that
530 a pre-generated tree of cryptographic checksums stored on a second
537 be called dm-verity.
547 Add ability for dm-verity device to be validated if the
548 pre-generated tree of cryptographic checksums passed has a pkcs#7
560 Rely on the secondary trusted keyring to verify dm-verity signatures.
570 Add forward error correction support to dm-verity. This option
571 makes it possible to use pre-generated error correction data to
580 This device-mapper target creates a device that supports an arbitrary
581 mapping of fixed-size regions of I/O across a fixed set of paths.
586 be called dm-switch.
594 This device-mapper target takes two devices, one device to use
602 be called dm-log-writes.
616 This device-mapper target emulates a block device that has
617 additional per-sector tags that can be used for storing
620 This integrity target is used with the dm-crypt target to
625 be called dm-integrity.
628 tristate "Drive-managed zoned block device target support"
633 This device-mapper target takes a host-managed or host-aware zoned
635 device (drive-managed zoned block device) without any write
643 be called dm-zoned.
651 Generate audit events for device-mapper.
654 particular device-mapper targets, especially the integrity target.