... | ... | @@ -1982,6 +1982,17 @@ for example: |
|
|
gnt-instance activate-disks $instance
|
|
|
done
|
|
|
|
|
|
If you see an error like this:
|
|
|
|
|
|
DRBD CRITICAL: Device 28 WFConnection UpToDate, Device 3 WFConnection UpToDate, Device 31 WFConnection UpToDate, Device 4 WFConnection UpToDate
|
|
|
|
|
|
In this case, it's warning that the node has device 4, 28, and 31 in
|
|
|
`WFConnection` state, which is incorrect. This might not be detected
|
|
|
by Ganeti and therefore requires some hand-holding. This is documented
|
|
|
in the [resyncing disks section of out DRBD documentation](howto/drbd#resyncing-disks). Like in
|
|
|
the above scenario, the solution is basically to run `activate-disks`
|
|
|
on the affected instances.
|
|
|
|
|
|
### Not enough memory for failovers
|
|
|
|
|
|
Another error that `gnt-cluster verify` can give you is, for example:
|
... | ... | |