Fail to migrate after crashed node online

Discussion in 'General Questions' started by Machiasiaweb, May 9, 2016.

  1. Machiasiaweb

    Machiasiaweb Mega Poster

    Messages:
    182
    Hello,

    One of my node in cluster was crashed and need force reboot.

    CT was successful register in another node at same cluster

    After boot up and I want to migrate back to original node. It got following message.

    ----------------
    vzmigrate node2 1231335
    Connection to destination node (node2) is successfully established
    Moving the CT#1231335 -> CT#1231335, [], [] ...
    quotaugidlimit = 0
    locking 1231335
    Checking bindmounts
    Check cluster ID
    Source and target CT private resides on the same shared partition
    Shared disk detected /vz/private/1231335/root.hdd
    Checking technologies
    Checking templates for CT
    Checking IP addresses on destination node
    Checking RATE parameters in config
    CT is shared and both nodes are in HA cluster.
    ploop_get_spec() : Error in open_delta (delta_read.c:200): Image is in use /pstorage/cluster1/private/1231335/root.hdd/root.hds [42]
    Can't move CT#1231335 -> CT#1001335, [], [] : ploop_get_spec() : Error in open_delta (delta_read.c:200): Image is in use /pstorage/cluster1/private/1231335/root.hdd/root.hds [42]
    --------------------------

    Could you please advise how to migrate back to original node?

    Thanks!
     
  2. Pavel

    Pavel A.I. Auto-Responder Staff Member

    Messages:
    478
    Hello,

    Could it be you executed the command from the destination node, not from the source?
    Also, you might want to use "--online" switch to keep container running during migration.
     
  3. Machiasiaweb

    Machiasiaweb Mega Poster

    Messages:
    182
    Hi,

    Finally I need to start up CTs first and then migrate back to original node.


    But that used much more time. If it have any method can directly migrate back to original node, then will great.

    Thanks!
     
  4. Pavel

    Pavel A.I. Auto-Responder Staff Member

    Messages:
    478
    Dear Machiasiaweb,

    This _is_ the direct migration. Or at least it is supposed to be the way I picture it in my mind:
    1) failure took place
    2) VM moved to another host
    3) you go to the host where VM is present now
    4) run "pmigrate <destination> <vmname>"
    5) done

    If you add some extra steps you're probably doing it wrong
     
  5. Machiasiaweb

    Machiasiaweb Mega Poster

    Messages:
    182
    Hello,

    Yes, that is what I done it and got those error message in my first post.

    A different is step 4 which I using "vzmigrate ...." rather than pmigrate
     
    Last edited: May 15, 2016

Share This Page