PCS6 Snapshot Error?!?

Discussion in 'General Questions' started by futureweb, Jun 2, 2016.

  1. futureweb

    futureweb Tera Poster

    Messages:
    390
    Hi,

    today I got a Problem with Snapshoting a CT.

    Code:
    [root@bl9 ~]# vzctl snapshot 341                   
    Creating snapshot {6ac58ac6-1693-4c1f-acae-03ed8f4b4981}
    Storing /vz/private/341/Snapshots.xml.tmp
    Setting up checkpoint...
            suspend...
    Checkpointing finished successfully
    Creating image snapshot uuid={6ac58ac6-1693-4c1f-acae-03ed8f4b4981} image=/vz/private/341/root.hdd
    Failed to create image /vz/private/341/root.hdd snapshot: Error in merge_image (merge.c:335): Error in ioctl(PLOOP_IOC_MERGE): Device or resource busy [3]
    Resuming the Container...
    Failed to create snapshot
    
    [root@bl9 ~]# vzctl snapshot-list 341
    PARENT_UUID                            C UUID                                   DATE                NAME
    
    [root@bl9 ~]# ploop list -a
    ploop31837  /pstorage/pcs1/private/341/root.hdd/root.hds /vz/root/341
    ploop41405  /pstorage/localSSD/pfcache.hdd/root.hdd /vz/pfcache
    
    [root@bl9 ~]# cat /proc/mounts | grep 341 | grep ploop
    /dev/ploop31837p1 /vz/root/341 ext4 rw,relatime,barrier=1,data=ordered,balloon_ino=12,pfcache_csum,pfcache=/vz/pfcache 0 0
    
    [root@bl9 ~]# grep /341/ /sys/block/ploop*/pdelta/*/image
    /sys/block/ploop31837/pdelta/0/image:/pstorage/pcs1/private/341/root.hdd/root.hds
    /sys/block/ploop31837/pdelta/1/image:/pstorage/pcs1/private/341/root.hdd/root.hds.{c78d6f11-fe54-48ae-9af7-5740916abaf1}
    
    [root@bl9 ~]# ploop snapshot-list /vz/private/341/root.hdd/DiskDescriptor.xml  
    PARENT_UUID  C UUID  FNAME  
    {00000000-0000-0000-0000-000000000000}  {e7da3bb5-3c09-4f8e-a36a-95e926669ce0} /pstorage/pcs1/private/341/root.hdd/root.hds
    {e7da3bb5-3c09-4f8e-a36a-95e926669ce0} * {5fbaabe3-6958-40ff-92a7-860e329aab41} /pstorage/pcs1/private/341/root.hdd/root.hds.{c78d6f11-fe54-48ae-9af7-5740916abaf1}
    
    [root@bl9 ~]# vzctl tsnapshot-delete 341 --id {e7da3bb5-3c09-4f8e-a36a-95e926669ce0}
    Delete image snapshot uuid={e7da3bb5-3c09-4f8e-a36a-95e926669ce0} image=/vz/private/341/root.hdd
    Failed to delete snapshot: Error in merge_image (merge.c:335): Error in ioctl(PLOOP_IOC_MERGE): Device or resource busy [3]
    Temporary snapshot {e7da3bb5-3c09-4f8e-a36a-95e926669ce0} has been successfully deleted
    
    [root@bl9 ~]# ploop snapshot-list /vz/private/341/root.hdd/DiskDescriptor.xml   
    PARENT_UUID  C UUID  FNAME   
    {00000000-0000-0000-0000-000000000000}  {e7da3bb5-3c09-4f8e-a36a-95e926669ce0} /pstorage/pcs1/private/341/root.hdd/root.hds
    {e7da3bb5-3c09-4f8e-a36a-95e926669ce0} * {5fbaabe3-6958-40ff-92a7-860e329aab41} /pstorage/pcs1/private/341/root.hdd/root.hds.{c78d6f11-fe54-48ae-9af7-5740916abaf1}
    
    Any ideas on this?

    Thx
    Andreas Schnederle-Wagner
     
    Last edited: Jun 2, 2016
  2. futureweb

    futureweb Tera Poster

    Messages:
    390
    Well - I guess it's a Bug in combination of Snapshots + moving a CT from one Root Server to another?!?
    CT 341 was moved from bl15 to bl9 yesterday ... the above posted output is from current Server - bl9 - but when I look at old Root - bl15:

    Code:
    [root@bl15 /]# ploop list -a | grep 341
    ploop49969   /pstorage/pcs1/private/341/root.hdd/root.hds  ~backup
    
    [root@bl15 /]# grep /341/ /sys/block/ploop*/pdelta/*/image
    /sys/block/ploop49969/pdelta/0/image:/pstorage/pcs1/private/341/root.hdd/root.hds
    
    [root@bl15 /]# ploop snapshot-list /vz/private/341/root.hdd/DiskDescriptor.xml
    PARENT_UUID                            C UUID                                   FNAME                           
    {00000000-0000-0000-0000-000000000000}   {e7da3bb5-3c09-4f8e-a36a-95e926669ce0} /pstorage/pcs1/private/341/root.hdd/root.hds
    {e7da3bb5-3c09-4f8e-a36a-95e926669ce0} * {5fbaabe3-6958-40ff-92a7-860e329aab41} /pstorage/pcs1/private/341/root.hdd/root.hds.{c78d6f11-fe54-48ae-9af7-5740916abaf1}
    
    I will open a Ticket for this ...
     
  3. futureweb

    futureweb Tera Poster

    Messages:
    390
    alright - it's reproduceable ...

    1) CT 999 on bl9
    2) Start a (full) BACKUP of 999 within PVA (or CLI ...)
    3) while the Backup is running move the CT --> vzmigrate root@bl13.fweb.at 999
    4) problems welcome ...

    Migration while a Backup is running:
    Now on bl9:
    bl13:
    as one can see - it's not possible to create Snapshots anymore as same root.hdd is ... ploop device on booth Servers on same root.hdd ...
     
    Last edited: Jun 2, 2016
  4. Pavel

    Pavel A.I. Auto-Responder Odin Team

    Messages:
    416
    As far as I know this was addressed today already, and a new bug was submitted. Thanks for the report!
     
  5. futureweb

    futureweb Tera Poster

    Messages:
    390
    yea - internal ID PSBM-47951 was created for this Problem.
     
  6. futureweb

    futureweb Tera Poster

    Messages:
    390
    Guess this Problem is not yet solved?!? Just run into it again :-/
     
  7. Pavel

    Pavel A.I. Auto-Responder Odin Team

    Messages:
    416
    Yes, it is not solved, yet.
    You can always check release notes for the bug ID to find out whether it was fixed or not.
     
  8. futureweb

    futureweb Tera Poster

    Messages:
    390
    Is there some kind of "complete changelog" now? Where all Changes are visible on one Page?
    --> Like PHP Changelog: http://php.net/ChangeLog-7.php

    Otherwise it's a bit hard to click through dozens of Release Notes searching for a specific Bug ID ;-)
     
  9. Pavel

    Pavel A.I. Auto-Responder Odin Team

    Messages:
    416
  10. futureweb

    futureweb Tera Poster

    Messages:
    390
    alright - that's ok for such usecases! ;-)

    But would still be very helpful to have a Changelog like PHPs - maybe you could open Feature-Request at the responsible department? :)
     

Share This Page