|
6 | 6 | [id="about-adding-devices-to-a-vg_{context}"]
|
7 | 7 | = About adding devices to a volume group
|
8 | 8 |
|
9 |
| -The `deviceSelector` field in the `LVMCluster` CR contains the configuration to specify the paths to the devices that you want to add to the LVM volume group. |
| 9 | +The `deviceSelector` field in the `LVMCluster` CR contains the configuration to specify the paths to the devices that you want to add to the LVM volume group (VG). |
10 | 10 |
|
11 |
| -You can specify the device paths in the `deviceSelector.paths` field, the `deviceSelector.optionalPaths` field, or both. If you do not specify the device paths in both the `deviceSelector.paths` field and the `deviceSelector.optionalPaths` field, {lvms} adds the supported unused devices to the LVM volume group. |
| 11 | +You can specify the device paths in the `deviceSelector.paths` field, the `deviceSelector.optionalPaths` field, or both. If you do not specify the device paths in both the `deviceSelector.paths` field and the `deviceSelector.optionalPaths` field, {lvms} adds the supported unused devices to the VG. |
12 | 12 |
|
13 |
| -The devices that you want to add to the volume group must be supported by {lvms}. For information about unsupported devices, see "Devices not supported by {lvms}" in the "Additional resources" section. |
| 13 | +You can also add the path to the RAID arrays to integrate the RAID arrays with {lvms}. For more information, see "Integrating RAID arrays with {lvms}". |
14 | 14 |
|
15 |
| -If you do not add the `deviceSelector` field in the `LVMCluster` CR, {lvms} automatically adds the new devices when the devices are available. |
| 15 | +The devices that you want to add to the VG must be supported by {lvms}. For information about unsupported devices, see "Devices not supported by {lvms}". |
16 | 16 |
|
17 |
| -{lvms} adds the devices to the LVM volume group only if the following conditions are met: |
| 17 | +{lvms} adds the devices to the VG only if the following conditions are met: |
18 | 18 |
|
19 | 19 | * The device path exists.
|
20 |
| -* The device is supported by {lvms}. |
21 |
| -
|
22 |
| -You can also add the path to the RAID arrays to integrate the RAID arrays with {lvms}. For more information, see "Integrating RAID arrays with {lvms}" in the "Additional resources" section. |
| 20 | +* The device is supported by {lvms}. |
23 | 21 |
|
24 | 22 | [IMPORTANT]
|
25 | 23 | ====
|
26 |
| -After a device is added to the LVM volume group, it cannot be removed. |
27 |
| -==== |
| 24 | +After a device is added to the VG, you cannot remove the device. |
| 25 | +==== |
| 26 | + |
| 27 | +{lvms} supports dynamic device discovery. If you do not add the `deviceSelector` field in the `LVMCluster` CR, {lvms} automatically adds the new devices to the VG when the devices are available. |
| 28 | + |
| 29 | +[WARNING] |
| 30 | +==== |
| 31 | +It is not recommended to add the devices to the VG through dynamic device discovery due to the following reasons: |
| 32 | +
|
| 33 | +* When you add a new device that you do not intend to add to the VG, {lvms} automatically adds this device to the VG through dynamic device discovery. |
| 34 | +* If {lvms} adds a device to the VG through dynamic device discovery, {lvms} does not restrict you from removing the device from the node. Removing or updating the devices that are already added to the VG can disrupt the VG. This can also lead to data loss and necessitate manual node remediation. |
| 35 | +==== |
0 commit comments