| Kconfig (cc1092019ce3d9b3e85a285b41e852ff94a6b590) | Kconfig (14f50b49fdab8f4c9fc87b55d3631e3bf1ffd385) |
|---|---|
| 1# 2# Block device driver configuration 3# 4 5if BLOCK 6 7menu "Multi-device support (RAID and LVM)" 8 --- 124 unchanged lines hidden (view full) --- 133 134 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To 135 compile this code as a module, choose M here: the module 136 will be called raid456. 137 138 If unsure, say Y. 139 140config MD_RAID5_RESHAPE | 1# 2# Block device driver configuration 3# 4 5if BLOCK 6 7menu "Multi-device support (RAID and LVM)" 8 --- 124 unchanged lines hidden (view full) --- 133 134 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To 135 compile this code as a module, choose M here: the module 136 will be called raid456. 137 138 If unsure, say Y. 139 140config MD_RAID5_RESHAPE |
| 141 bool "Support adding drives to a raid-5 array (experimental)" 142 depends on MD_RAID456 && EXPERIMENTAL | 141 bool "Support adding drives to a raid-5 array" 142 depends on MD_RAID456 143 default y |
| 143 ---help--- 144 A RAID-5 set can be expanded by adding extra drives. This 145 requires "restriping" the array which means (almost) every 146 block must be written to a different place. 147 148 This option allows such restriping to be done while the array | 144 ---help--- 145 A RAID-5 set can be expanded by adding extra drives. This 146 requires "restriping" the array which means (almost) every 147 block must be written to a different place. 148 149 This option allows such restriping to be done while the array |
| 149 is online. However it is still EXPERIMENTAL code. It should 150 work, but please be sure that you have backups. | 150 is online. |
| 151 152 You will need mdadm version 2.4.1 or later to use this 153 feature safely. During the early stage of reshape there is 154 a critical section where live data is being over-written. A 155 crash during this time needs extra care for recovery. The 156 newer mdadm takes a copy of the data in the critical section 157 and will restore it, if necessary, after a crash. 158 159 The mdadm usage is e.g. 160 mdadm --grow /dev/md1 --raid-disks=6 161 to grow '/dev/md1' to having 6 disks. 162 163 Note: The array can only be expanded, not contracted. 164 There should be enough spares already present to make the new 165 array workable. 166 | 151 152 You will need mdadm version 2.4.1 or later to use this 153 feature safely. During the early stage of reshape there is 154 a critical section where live data is being over-written. A 155 crash during this time needs extra care for recovery. The 156 newer mdadm takes a copy of the data in the critical section 157 and will restore it, if necessary, after a crash. 158 159 The mdadm usage is e.g. 160 mdadm --grow /dev/md1 --raid-disks=6 161 to grow '/dev/md1' to having 6 disks. 162 163 Note: The array can only be expanded, not contracted. 164 There should be enough spares already present to make the new 165 array workable. 166 |
| 167 If unsure, say Y. 168 |
|
| 167config MD_MULTIPATH 168 tristate "Multipath I/O support" 169 depends on BLK_DEV_MD 170 help 171 Multipath-IO is the ability of certain devices to address the same 172 physical disk over multiple 'IO paths'. The code ensures that such 173 paths can be defined and handled at runtime, and ensures that a 174 transparent failover to the backup path(s) happens if a IO errors --- 90 unchanged lines hidden --- | 169config MD_MULTIPATH 170 tristate "Multipath I/O support" 171 depends on BLK_DEV_MD 172 help 173 Multipath-IO is the ability of certain devices to address the same 174 physical disk over multiple 'IO paths'. The code ensures that such 175 paths can be defined and handled at runtime, and ensures that a 176 transparent failover to the backup path(s) happens if a IO errors --- 90 unchanged lines hidden --- |