mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-21 13:34:40 +03:00
970dfbcd69
If a RAID array is not in-sync, replacing devices should not be allowed as a general rule. This is because the contents used to populate the incoming device may be undefined because the devices being read where not in-sync. The kernel enforces this rule unless overridden by not allowing the creation of an array that is not in-sync and includes a devices that needs to be rebuilt. Since we cannot know the sync state of an LV if it is inactive, we must also enforce the rule that an array must be active to replace devices. That leaves us with the following conditions: 1) never allow replacement or repair of devices if the LV is in-active 2) never allow replacement if the LV is not in-sync 3) allow repair if the LV is not in-sync, but warn that contents may not be recoverable. In the case where a user is performing the repair on the command line via 'lvconvert --repair', the warning is printed before the user is prompted if they would like to replace the device(s). If the repair is automated (i.e. via dmeventd and policy is "allocate"), then the device is replaced if possible and the warning is printed. |
||
|---|---|---|
| .. | ||
| activate | ||
| cache | ||
| commands | ||
| config | ||
| datastruct | ||
| device | ||
| display | ||
| error | ||
| filters | ||
| format1 | ||
| format_pool | ||
| format_text | ||
| freeseg | ||
| label | ||
| locking | ||
| log | ||
| metadata | ||
| mirror | ||
| misc | ||
| mm | ||
| raid | ||
| replicator | ||
| report | ||
| snapshot | ||
| striped | ||
| thin | ||
| unknown | ||
| uuid | ||
| zero | ||
| Makefile.in | ||