[DRBD-user] drbdmanage upgrade to linstor

[Gábor Hernádi]

Hello,

unfortunately there is no straightforward way to correct that lvmthin
instead of lvm mistake.
LINSTOR does not allow you to delete the storage pool while it has
resources in it.
That means, I see only 2 ways to fix this issue. As you found out, the lost
storage-pool is not fully implemented yet (sorry for having it already in
our docs), but there is a lost node command. That means you could shut down
ALL satellites (that will NOT stop DRBD from replicating), issue the node
lost command, start that one satellite again which you just "lost" and
perform the corrected commands from the migration again (starting with
"linstor node create ..."). Afterwards you can restart the other satellites.

Stopping the other satellites is only needed so that the other satellites
do NOT update their DRBD .res files as the "lost" node disappeared.
Otherwise all satellites would reconfigure their local DRBD to disconnect
from the lost node's DRBD resources, which you might want to avoid in this
case.

While the second way fixing this issue might be much easier, we usually DO
NOT recommend manually editing the database directly. However, if you have
not created any new resources using the "wrong" lvmthin setting, this might
be easier for you:
Stop the controller (this will also NOT stop DRBD replication), open the
database, find the NODE_STOR_POOL table and simply update the corresponding
DRIVER_NAME to "LVM". If you are done start the controller again.

Regarding the offline controller issue, there are two things to know:
First, the current LINSTOR controller will NEVER contact another LINSTOR
controller. That means that other LINSTOR controllers added to the node
list will always be shown as OFFLINE, even if they are up and running.
Second, the previous rule is only true for "other" controllers. If you add
the current controller to its own node-list (which you can do, but is by no
means required, this is more for self-documentation purposes), the
controller will show "itself" as ONLINE. The controller determines if a
controller-typed node is "itself" by checking the local addresses to the
given IP address from the controller-typed node. If one matches, it assumes
that it has found itself (sounds enlightening...)

However, even an ONLINE controller node is nothing more but
self-documentation and has no real use or effect.

-- 
Best regards,
Gabor Hernadi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20200330/29099e81/attachment-0001.htm>