Lines Matching +full:allow +full:- +full:set +full:- +full:time
1 # SPDX-License-Identifier: GPL-2.0-only
20 # after relevant mdadm enhancements - to make "names=yes"
21 # the default - are widely available.
34 Software RAID mini-HOWTO, available from
49 a several-second delay in the boot time due to various
69 use the so-called linear mode, i.e. it will combine the hard disk
78 tristate "RAID-0 (striping) mode"
82 use the so-called raid0 mode, i.e. it will combine the hard disk
88 Software-RAID mini-HOWTO, available from
98 tristate "RAID-1 (mirroring) mode"
101 A RAID-1 set consists of several disk drives which are exact copies
103 will continue to use the operational mirrors in the set, providing
105 kernel. In a set with N drives, the available space is the capacity
106 of a single drive, and the set protects against a failure of (N - 1)
110 Software-RAID mini-HOWTO, available from
114 If you want to use such a RAID-1 set, say Y. To compile this code
120 tristate "RAID-10 (mirrored striping) mode"
123 RAID-10 provides a combination of striping (RAID-0) and
124 mirroring (RAID-1) with easier configuration and more flexible
126 Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
129 RAID-10 provides a variety of layouts that provide different levels
132 RAID-10 requires mdadm-1.7.0 or later, available at:
139 tristate "RAID-4/RAID-5/RAID-6 mode"
148 A RAID-5 set of N drives with a capacity of C MB per drive provides
149 the capacity of C * (N - 1) MB, and protects against a failure
150 of a single drive. For a given sector (row) number, (N - 1) drives
152 For a RAID-4 set, the parity blocks are present on a single drive,
153 while a RAID-5 set distributes the parity across the drives in one
156 A RAID-6 set of N drives with a capacity of C MB per drive
157 provides the capacity of C * (N - 2) MB, and protects
159 (row) number, (N - 2) drives contain data sectors, and two
161 RAID-5, RAID-6 distributes the syndromes across the drives
165 Software-RAID mini-HOWTO, available from
169 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
179 MD_MULTIPATH provides a simple multi-path personality for use
224 Device-mapper is a low level volume manager. It works by allowing
232 called dm-mod.
240 Enable this for messages that may help debug device-mapper problems.
249 as a cache, holding recently-read blocks in memory and performing
274 Some bio locking schemes used by other device-mapper targets
277 source "drivers/md/persistent-data/Kconfig"
284 RAID0 or dm-striped target.
295 This device-mapper target allows you to create a device that
299 For further information on dm-crypt and userspace tools see:
303 be called dm-crypt.
312 Allow volume managers to take writable snapshots of a device.
329 dm-cache attempts to improve performance of a block device by
363 dm-ebs emulates smaller logical block size on backing devices
373 dm-era tracks which parts of a block device are written to
374 over time. Useful for maintaining cache coherency when using
383 dm-clone produces a one-to-one copy of an existing, read-only source
395 Allow volume managers to mirror logical volumes, also
404 relaying the dm-dirty-log API to userspace. Log designs
420 A RAID-5 set of N drives with a capacity of C MB per drive provides
421 the capacity of C * (N - 1) MB, and protects against a failure
422 of a single drive. For a given sector (row) number, (N - 1) drives
424 For a RAID-4 set, the parity blocks are present on a single drive,
425 while a RAID-5 set distributes the parity across the drives in one
428 A RAID-6 set of N drives with a capacity of C MB per drive
429 provides the capacity of C * (N - 2) MB, and protects
431 (row) number, (N - 2) drives contain data sectors, and two
433 RAID-5, RAID-6 distributes the syndromes across the drives
452 Allow volume managers to support multipath hardware.
455 tristate "I/O Path Selector based on the number of in-flight I/Os"
459 the path with the least number of in-flight I/Os.
464 tristate "I/O Path Selector based on the service time"
469 time.
474 tristate "I/O Path Selector based on historical service time"
479 time by comparing estimated service time (based on historical
480 service time).
489 executed on and the CPU to path mapping setup at path addition time.
512 bool "DM \"dm-mod.create=\" parameter support"
515 Enable "dm-mod.create=" parameter to create mapped devices at init time.
516 This option is useful to allow mounting rootfs without requiring an
518 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
542 This device-mapper target creates a read-only device that
544 a pre-generated tree of cryptographic checksums stored on a second
551 be called dm-verity.
561 Add ability for dm-verity device to be validated if the
562 pre-generated tree of cryptographic checksums passed has a pkcs#7
574 Rely on the secondary trusted keyring to verify dm-verity signatures.
584 Add forward error correction support to dm-verity. This option
585 makes it possible to use pre-generated error correction data to
594 This device-mapper target creates a device that supports an arbitrary
595 mapping of fixed-size regions of I/O across a fixed set of paths.
600 be called dm-switch.
608 This device-mapper target takes two devices, one device to use
616 be called dm-log-writes.
630 This device-mapper target emulates a block device that has
631 additional per-sector tags that can be used for storing
634 This integrity target is used with the dm-crypt target to
639 be called dm-integrity.
642 tristate "Drive-managed zoned block device target support"
647 This device-mapper target takes a host-managed or host-aware zoned
649 device (drive-managed zoned block device) without any write
657 be called dm-zoned.
666 Generate audit events for device-mapper.
669 particular device-mapper targets, especially the integrity target.