[DRBD-user] Add new replica to existing resource
gabor.hernadi at linbit.com
Thu Mar 14 07:48:29 CET 2019
On Thu, Mar 14, 2019 at 7:18 AM <robinlee at post.cz> wrote:
> I installed DRBD/Linstor on proxmox with redundancy 1, after adding second
> node to the cluster I would like to expand the resources to another node =
> redundancy 2.
> The new resources seems be OK, but the older one, created with redundancy
> 1 seems be not mirroing to another side. I just called
> linstor resource create <second-node-name> vm-108-disk-1 --storage-pool
> now I see that the resource has two volumes, but the second one is
> actually empty, the content wasn't copied there.
> How can I mirror the old volumes content to the new node, or better, how
> can I correctly add new linstor node to the cluster? The proxmox nodes are
> connected and live migration works, but only for the new VMs, not the older
> drbd-user mailing list
> drbd-user at lists.linbit.com
first, you should check the status of drbd itself `drbdadm status`. I guess
you will see that one volume is UpToDate, and the other one (the one that
is not replicating) is Inconsistent.
Further I guess that you created that second volume AFTER you deployed the
resource. That means, something like "create resource-definition", "create
first volume definition", "create resource on first node", "create second
volume definition", "create resource on second node".
If that guess is correct, then you should read the mail "[DRBD-user] Adding
volume to an existing resource results in "Inconsistent" state" from 11th
In short: When Linstor extends an existing resource with a volume, that
volume will stay inconsistent. You have to manually primary (possibly with
--force) to mark it as UpToDate. (you can safely make that resource
secondary afterwards again)
Once a volume is UpToDate, DRBD will also start replicating to the resource
on the second node.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the drbd-user