If it was not executing coalesce you would see the parent reference when
you listed the hierarchy, right?

On Wed, Oct 25, 2017 at 10:25 PM, Lotic Lists <li...@lotic.com.br> wrote:

> I think ACS preserve all VHDs for coalesce but coalesce not occur when
> create a template or before starting next snapshot scheduled.
> If I create a template from any snapshots (2) showing in GUI, the template
> have 49GB. 49 GB is the size of the 2 latest files on secondary storage.
>
> What do you think? Bug?
>
>
> -----Original Message-----
> From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
> Sent: quarta-feira, 25 de outubro de 2017 22:07
> To: users@cloudstack.apache.org
> Subject: Re: Strange size of template from snapshot on XenServer
>
> Aha, The two destroyed entries are showing " removed: NULL".
>
> In ACS one thing is the "destroying" of a resource, another is the removal
> of this resource from the system. I believe there is something to do with
> the expunge interval, but I am not sure if the snapshots complete removal
> also happens within the expunge interval of user VMs or if it is configured
> by something else.
>
>
> On Wed, Oct 25, 2017 at 10:03 PM, Lotic Lists <li...@lotic.com.br> wrote:
>
> > I not start manual snapshot, just scheduled with keep=2
> >
> > GUI showing 2 snapshots, database showing 4 entries, 2 Destroyed and 2
> > BackedUp
> >
> > *************************** 132. row ***************************
> >               id: 6380
> >   data_center_id: 2
> >       account_id: 64
> >        domain_id: 49
> >        volume_id: 2102
> > disk_offering_id: 230
> >           status: Destroyed
> >             path: NULL
> >             name: FullCRM_ROOT-542_20171022030205
> >             uuid: 1294cdb7-01bf-4e76-b4c0-11b3c6b395e9
> >    snapshot_type: 4
> > type_description: DAILY
> >             size: 311385128960
> >          created: 2017-10-22 03:02:05
> >          removed: NULL
> >   backup_snap_id: NULL
> >         swift_id: NULL
> >       sechost_id: NULL
> >     prev_snap_id: NULL
> >  hypervisor_type: XenServer
> >          version: 2.2
> >            s3_id: NULL
> >         min_iops: NULL
> >         max_iops: NULL
> > *************************** 133. row ***************************
> >               id: 6416
> >   data_center_id: 2
> >       account_id: 64
> >        domain_id: 49
> >        volume_id: 2102
> > disk_offering_id: 230
> >           status: Destroyed
> >             path: NULL
> >             name: FullCRM_ROOT-542_20171023030205
> >             uuid: 0a8067a3-ad15-40b6-8b16-c1881d7d9f41
> >    snapshot_type: 4
> > type_description: DAILY
> >             size: 311385128960
> >          created: 2017-10-23 03:02:05
> >          removed: NULL
> >   backup_snap_id: NULL
> >         swift_id: NULL
> >       sechost_id: NULL
> >     prev_snap_id: NULL
> >  hypervisor_type: XenServer
> >          version: 2.2
> >            s3_id: NULL
> >         min_iops: NULL
> >         max_iops: NULL
> > *************************** 134. row ***************************
> >               id: 6455
> >   data_center_id: 2
> >       account_id: 64
> >        domain_id: 49
> >        volume_id: 2102
> > disk_offering_id: 230
> >           status: BackedUp
> >             path: NULL
> >             name: FullCRM_ROOT-542_20171024030207
> >             uuid: 1ca646e5-a155-4a59-aa31-5889eec7536f
> >    snapshot_type: 4
> > type_description: DAILY
> >             size: 311385128960
> >          created: 2017-10-24 03:02:07
> >          removed: NULL
> >   backup_snap_id: NULL
> >         swift_id: NULL
> >       sechost_id: NULL
> >     prev_snap_id: NULL
> >  hypervisor_type: XenServer
> >          version: 2.2
> >            s3_id: NULL
> >         min_iops: NULL
> >         max_iops: NULL
> > *************************** 135. row ***************************
> >               id: 6497
> >   data_center_id: 2
> >       account_id: 64
> >        domain_id: 49
> >        volume_id: 2102
> > disk_offering_id: 230
> >           status: BackedUp
> >             path: NULL
> >             name: FullCRM_ROOT-542_20171025030208
> >             uuid: 759d61dc-e3db-4815-b68b-b90904ccbda5
> >    snapshot_type: 4
> > type_description: DAILY
> >             size: 311385128960
> >          created: 2017-10-25 03:02:08
> >          removed: NULL
> >   backup_snap_id: NULL
> >         swift_id: NULL
> >       sechost_id: NULL
> >     prev_snap_id: NULL
> >  hypervisor_type: XenServer
> >          version: 2.2
> >            s3_id: NULL
> >         min_iops: NULL
> >         max_iops: NULL
> >
> >
> >
> > -----Original Message-----
> > From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
> > Sent: quarta-feira, 25 de outubro de 2017 21:50
> > To: users@cloudstack.apache.org
> > Subject: Re: Strange size of template from snapshot on XenServer
> >
> > The file "14818597-55bb-49be-9ace-761e9e01c074.vhd" seems more like a
> > manual snapshot. It was created 2 hours after the "normal" time. I
> > would check these snapshots in ACS and see how they are presented.
> > BTW, how many snapshots is ACS showing for this volume? I would also
> > check the "snapshots" table for the volume you have configured them.
> > select * from snapshots where volume_id = ?
> >
> > you may also filter for removed:
> > select * from snapshots where volume_id = ? and removed is null
> >
> > On Wed, Oct 25, 2017 at 9:39 PM, Lotic Lists <li...@lotic.com.br> wrote:
> >
> > > Hi Rafael, I check
> > >
> > > # ls -lrt
> > > total 285368382
> > > -rw-r--r-- 1 root root 304124744192 Oct 22 03:28
> > > 14818597-55bb-49be-9ace- 761e9e01c074.vhd
> > > -rw-r--r-- 1 root root  17770869248 Oct 23 01:10
> > > bbd9e9b5-53fb-44a2-afbe- f262396a2d84.vhd
> > > -rw-r--r-- 1 root root  52199817728 Oct 24 01:30
> > > 3b90bbb2-7ce5-41f6-9f7e- fd0ea061cb2d.vhd
> > > -rw-r--r-- 1 root root  51615670784 Oct 25 01:28
> > > 4b450217-c9ad-45a2-946b- de3cb323469b.vhd
> > >
> > > # vhd-util scan -f -m'*.vhd' -p
> > > vhd=14818597-55bb-49be-9ace-761e9e01c074.vhd capacity=311385128960
> > > size=304124744192 hidden=0 parent=none
> > > vhd=bbd9e9b5-53fb-44a2-afbe-f262396a2d84.vhd capacity=311385128960
> > > size=17770869248 hidden=0 parent=none
> > > vhd=3b90bbb2-7ce5-41f6-9f7e-fd0ea061cb2d.vhd capacity=311385128960
> > > size=52199817728 hidden=0 parent=none
> > > vhd=4b450217-c9ad-45a2-946b-de3cb323469b.vhd capacity=311385128960
> > > size=51615670784 hidden=0 parent=none
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
> > > Sent: quarta-feira, 25 de outubro de 2017 20:44
> > > To: users@cloudstack.apache.org
> > > Subject: Re: Strange size of template from snapshot on XenServer
> > >
> > > Did you check the hierarchy of those snapshot files in your
> > > secondary storage?
> > >
> > >
> > >
> > > On Wed, Oct 25, 2017 at 7:44 PM, Lotic Lists <li...@lotic.com.br>
> wrote:
> > >
> > > > Hi all
> > > >
> > > >
> > > >
> > > > Anyone identify problems with templates from snapshots on XenServer?
> > > >
> > > > I created a recurrent snapshot, first VHD on secondary storage
> > > > have a similar size of volume. If I create a template from latest
> > > > snapshot, the size of VHD of template is smaller equal from last
> > > > snapshot, I think CloudStack/Xenserver not coalesce VHD files of
> > > > secondary storage for create the template
> > > >
> > > >
> > > >
> > > > I keep two recurrent snapshots, on secondary storage have four files.
> > > >
> > > >
> > > >
> > > > Environment is ACS 4.9.3.0 and XenServer 6.5, primary storage is
> > > > PreSetup with ISCSI.
> > > >
> > > >
> > > >
> > > > Thanks
> > > >
> > > > Marcelo
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Rafael Weingärtner
> > >
> > >
> >
> >
> > --
> > Rafael Weingärtner
> >
> >
>
>
> --
> Rafael Weingärtner
>
>


-- 
Rafael Weingärtner

Reply via email to