Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
From: =?utf-8?q?David=20Amor=c3=adn?= <david.amorin@adderglobal.com>
To: users@cloudstack.apache.org, "users@cloudstack.apache.org"
 <users@cloudstack.apache.org>
Subject: Re[3]: Erased snapshot/templates still remains in storage
Date: Mon, 24 Oct 2016 13:48:56 +0000
Message-Id: <em93502de1-3ffd-468f-9506-39f8530a67b4@pcpaddgno010>
In-Reply-To: <em73b07baf-4107-4729-a57a-fc99916dff20@pcpaddgno010>
References: <e10cebae-a239-26e7-73db-45452beeb12a@failiem.lv>
 <em51f7df65-8d87-4e96-af50-79378e07eb17@pcpaddgno010>
 <CAG97rac+cgPMu33TK287pOWf795JHSGL1_2+8ryo9K52mFOU+A@mail.gmail.com>
 <BY2PR02MB2007214E154A8FD77BBA30CDA9C40@by2pr02mb2007.namprd02.prod.outlook.com>
 <BY2PR02MB200767FB60C3531D50F9D7BCA9DA0@by2pr02mb2007.namprd02.prod.outlook.com>
 <em73b07baf-4107-4729-a57a-fc99916dff20@pcpaddgno010>
Reply-To: =?utf-8?q?David=20Amor=c3=adn?= <david.amorin@adderglobal.com>
User-Agent: eM_Client/7.0.26687.0
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------=_MB6D551A8B-8CAC-4EA0-B892-78832103371B"
archived-at: Mon, 24 Oct 2016 13:49:11 -0000

--------=_MB6D551A8B-8CAC-4EA0-B892-78832103371B
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Sorry to bring up an old question, just want to ask again if anyone can=20
confirm that when you delete a instance the snapshots belong to the=20
instance still remain on primary storage.

Thanks for the confirmation

David


------ Mensaje original ------
De: "David Amor=C3=ADn" <david.amorin@adderglobal.com>
Para: "users@cloudstack.apache.org" <users@cloudstack.apache.org>
Enviado: 14/10/2016 12:37:27
Asunto: Re[2]: Erased snapshot/templates still remains in storage

>Hi Simon,
>Yes it was enable but I changed the default values of the timer set to:
>storage.cleanup.delay 60storage.cleanup.interval=20
>300storage.cleanup.enabled=3Dtrue
>In order to make a couple of test and when i delete an instance with=20
>snapshost and templates, i see the following behavior:
>The templates are deleted correctly but the snapshosts still remain on=20
>primary storage
>
>I was reading the following thread about the same issue:
>
>https://www.mail-archive.com/users@cloudstack.apache.org/msg19669.html
>
>
>Thanks for your help
>
>Best
>
>David
>
>
>------ Mensaje original ------
>De: "Simon Weller" <sweller@ena.com>
>Para: "users@cloudstack.apache.org" <users@cloudstack.apache.org>;=20
>"David Amor=C3=ADn" <david.amorin@adderglobal.com>
>Enviado: 11/10/2016 13:42:24
>Asunto: Re: Erased snapshot/templates still remains in storage
>
>>David,
>>
>>What have you got your storage cleanup thread timer set to? ACS will=20
>>normally run a periodic process to expunge deleted storage objects.
>>
>>- si
>>
>>________________________________
>>From: David Amor=C3=ADn <david.amorin@adderglobal.com>
>>Sent: Tuesday, October 11, 2016 4:04 AM
>>To: users@cloudstack.apache.org
>>Subject: Erased snapshot/templates still remains in storage
>>
>>Hi all,
>>I just wanted to share with you the following behavior we saw on CS
>>4.5.2 and now we also see on version 4.9.
>>
>>Our environment: Xenserver 6.5, Cloudstack 4.9, primary storage: iSCSI
>>Description: When I take a volume snapshot, I see an snapshot in
>>XenServer primary storage:xe vdi-list name-label=3Dsnapshot-20161010uuid=
=20
>>(
>>RO)                : 81d37e1c-d9a7-431e-9996-7a550b72528bname-label (
>>RW): snapshot-20161010name-description ( RW):sr-uuid ( RO):
>>36eb8055-90f1-8cbf-e35c-3b13c0dd701avirtual-size ( RO):
>>26843545600sharable ( RO): falseread-only ( RO): falseOnce it is
>>transferred to the secondary storage, I see the following
>>message:2016-10-10 13:44:38,897 DEBUG
>>[c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-419:ctx-7b451fd0)
>>(logid:b8c932db) Successfully destroyed snapshot on volume:
>>82d3194e-a4f0-4813-b0c9-c0c3c4a81deb execept this current snapshot
>>81d37e1c-d9a7-431e-9996-7a550b72528bThen when I delete from Cloudstack
>>this volume snapshots:2016-10-10 13:47:41,402 DEBUG
>>[o.a.c.s.s.XenserverSnapshotStrategy]=20
>>(API-Job-Executor-69:ctx-77734d15
>>job-3789 ctx-1f2ebdf0) (logid:1cac9567) Snapshot: 754 doesn't have
>>children, so it's ok to delete it and its parentsChecking CS database,
>>in "snapshot_store_ref" table, the element with
>>install_path=3D81d37e1c-d9a7-431e-9996-7a550b72528b changed its status
>>from "Ready" to "Destroyed" but in Xenserver this vdi wasn't
>>deleted.Something similar happens deleting templates, but in this=20
>>case,
>>in table "template_spool_ref", the referenced vdi never change to
>>"Destroyed".
>>
>>Questions:
>>If i don't have any wrong configuration on CS, i confirm that when i
>>delete a snapshot or template from CloudStack, the file VHD is deleted
>>correctly on the secondary storage but the volumen (VDI) on primary
>>storage remains. Can you confirm if somebody else has the same=20
>>behavior?
>>When we take a manual snapshot or template. CS always keep the
>>snapshot/template on the secondary storage and ALSO on primary=20
>>storage.
>>Is that correct?
>>
>>Thanks for your help
>>
>>Best,
>>
>>David
>>
>>
--------=_MB6D551A8B-8CAC-4EA0-B892-78832103371B--