Error while migrating Proxmox3

Discussion in 'Debian Appliance Builder' started by labor, Aug 8, 2013.

  1. labor

    labor New Member

    Joined:
    Aug 8, 2013
    Messages:
    1
    Likes Received:
    0
    Good day dear community.Immediately I ask forgiveness for my knowledge of the language.There is a cluster consisting of two nodes. The other day byd updated to version 3, previously worked for version 2.Prior to this migration mechanism is not used. After the upgrade, decided to try. The migration is successful, the machine is put to another node, but at the end of fall migration in the log is reported.
    Code:
    Aug 08 09:57:24 migration speed: 11.31 MB/s - downtime 54 ms
    Aug 08 09:57:24 migration status: completed
    Aug 08 09:57:27 ERROR: volume deativation failed: drbd7_asterisk:vm-105-disk-1 at /usr/share/perl5/PVE/Storage.pm line 784.
    Aug 08 09:57:27 ERROR: migration finished with problems (duration 00:03:06)
    TASK ERROR: migration problems
    
    Please tell me how this is a critical issue?
    PS: I'm sorry if posted in the wrong section.

    Russian version
    Добрый день уважаемое сообщество.

    Сразу прошу прощение за мое знание языка.
    Есть кластер состоящий из двух нод. На днях быд обновлен до 3 версии, до этого работало на версии 2.
    До этого механизмом миграции не пользовался. После обновления решил попробывать. Миграция проходит успешно, машинка заводится на другой ноде, но в конце миграции в логе выпадает такое сообщение:
    Code:
    Aug 08 09:57:24 migration speed: 11.31 MB/s - downtime 54 ms
    Aug 08 09:57:24 migration status: completed
    Aug 08 09:57:27 ERROR: volume deativation failed: drbd7_asterisk:vm-105-disk-1 at /usr/share/perl5/PVE/Storage.pm line 784.
    Aug 08 09:57:27 ERROR: migration finished with problems (duration 00:03:06)
    TASK ERROR: migration problems
    
    Подскажите пожалуйста насколько это критичная проблема?
    PS: Простите если разместил не в том разделе.
     
  2. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,319
    Likes Received:
    285
    It is not critical, as long as you do not access the volume manually on the other node. But try to find out
    why volume de-activation failed - try to de-activate manually (see 'man lvchange').
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice