mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-21 13:34:40 +03:00
bc29785d09
There are two known bugs in the lvconvert-raid-status-validation.sh test. The first one I consider to be more of an annoyance (1507719). The second one I consider to be more serious (1507729). RHBZ 1507719 simply documents the fact that the three RAID status fields may not always be coherent due to the way they are set and unset when the MD thread is shutting down and starting up. For example, the sync ratio may be 100% but the sync action may not yet have switched to "idle" and the health characters may not yet all be 'A's (i.e. the devices set to InSync). RHBZ 1507729 is more serious. The sync ratio can be 100% for a short period of time after upconverting linear -> RAID1. It is reset to 0 once the MD sync thread gets to work on it. It does this because, technically, the array /is/ in-sync if the new devices are excluded - i.e. the data is 100% available and consistent. I'm not sure what to do about this problem, but we'd much rather not have this state that looks exactly like the end of the process when the sync ratio is 100% because the "recover" process finished, but the sync action and health characters haven't been updated yet. Put simply, the problem is that we can't tell if a sync is starting or finished based on the status output. |
||
|---|---|---|
| .. | ||
| api | ||
| dbus | ||
| lib | ||
| shell | ||
| unit | ||
| .gitignore | ||
| Makefile.in | ||