You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Pierre-Luc Dion <pd...@cloudops.com> on 2014/01/22 17:24:03 UTC

force expunge disks

I'm stuck with some disks with "Expunging" state. The the VDI for the
hypervisor is gone but the disk in Cloudstack remain in Expunging state. is
their a way to  force expunging them or updating the database to reflect
the proper state of the disk ?

I'm tempted to execute following SQL queries but would I miss entries
somewhere else?

update volumes set removed='2014-01-16 18:57:25', state='Expunged',
display_volume=0 WHERE name='DATA-1442' LIMIT 1;
update volume_view set removed='2014-01-16 18:57:25', state='Expunged',
display_volume=0 WHERE name='DATA-1442' LIMIT 1;


Thanks,

Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

RE: force expunge disks

Posted by Geoff Higginbottom <ge...@shapeblue.com>.
If you are 'sure' the volumes have been deleted from the Primary Storage, and you just want to clean up the references in the UI, then in the volumes table, update the 'state' column to 'Expunged' and add a date/time into the 'removed' column.

You may also want to 'null' the 'last_pod_id' , 'folder' & pod_id, columns.  I only say this as volumes which were successfully expunged did not have values in these columns.

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbottom@shapeblue.com

-----Original Message-----
From: Rafael Weingartner [mailto:rafaelweingartner@gmail.com]
Sent: 22 January 2014 18:51
To: users@cloudstack.apache.org
Subject: Re: force expunge disks

is there any errors on MS logs? Could you post them here?

On Wed, Jan 22, 2014 at 4:48 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote:
> The delete and expunge process work fine. it's just that for some
> reason we have few disks which failed, I'm suspecting a primary
> storage that would have been removed without emptied it.
>
>
> Pierre-Luc Dion
> Architecte de Solution Cloud | Cloud Solutions Architect 514-447-3456,
> 1101
> - - -
>
> *CloudOps*420 rue Guy
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
>
>
> On Wed, Jan 22, 2014 at 1:46 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote:
>
>> Settings expunge.delay and expunge.interval have been set to 60 long
>> time ago. I'm in the situation of a "kind of broken" system for now
>> where in cloudstack some disks are in "Expunging" state but the VDI
>> (.vhd file)  itself as been deleted from the primary storage.
>>
>>
>> Pierre-Luc Dion
>> Architecte de Solution Cloud | Cloud Solutions Architect
>> 514-447-3456, 1101
>> - - -
>>
>> *CloudOps*
>> 420 rue Guy
>> Montréal QC  H3J 1S6
>> www.cloudops.com
>> @CloudOps_
>>
>>
>> On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. <
>> hollman.enciso@gmail.com> wrote:
>>
>>> You have to wait the interval configured on global settings:
>>>
>>>
>>> expunge.delay    Determines how long (in seconds) to wait before actually
>>> expunging destroyed vm. The default value = the default value of
>>> expunge.interval
>>>
>>>
>>> expunge.interval    The interval (in seconds) to wait before running the
>>> expunge thread.
>>>
>>> I can't remember the default time, i think that it's 42 hours. i
>>> Change it to 1 hour (in seconds)
>>>
>>> and that's it
>>>
>>>
>>> On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion
>>> <pdion@cloudops.com
>>> >wrote:
>>>
>>> > I'm stuck with some disks with "Expunging" state. The the VDI for
>>> > the hypervisor is gone but the disk in Cloudstack remain in
>>> > Expunging
>>> state. is
>>> > their a way to  force expunging them or updating the database to
>>> > reflect the proper state of the disk ?
>>> >
>>> > I'm tempted to execute following SQL queries but would I miss
>>> > entries somewhere else?
>>> >
>>> > update volumes set removed='2014-01-16 18:57:25',
>>> > state='Expunged',
>>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1; update
>>> > volume_view set removed='2014-01-16 18:57:25', state='Expunged',
>>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1;
>>> >
>>> >
>>> > Thanks,
>>> >
>>> > Pierre-Luc Dion
>>> > Architecte de Solution Cloud | Cloud Solutions Architect
>>> > 514-447-3456, 1101
>>> > - - -
>>> >
>>> > *CloudOps*420 rue Guy
>>> > Montréal QC  H3J 1S6
>>> > www.cloudops.com
>>> > @CloudOps_
>>> >
>>>
>>>
>>>
>>> --
>>> Hollman Eduardo Enciso R.
>>> http://nexxuz.com
>>> http://algolibre.com <http://www.hollmanenciso.com/> @hollman
>>>
>>
>>



--
Rafael Weingärtner
Need Enterprise Grade Support for Apache CloudStack?
Our CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> offers the best 24/7 SLA for CloudStack Environments.

Apache CloudStack Bootcamp training courses

**NEW!** CloudStack 4.2.1 training<http://shapeblue.com/cloudstack-training/>
18th-19th February 2014, Brazil. Classroom<http://shapeblue.com/cloudstack-training/>
17th-23rd March 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
24th-28th March 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
16th-20th June 2014, Region A. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>
23rd-27th June 2014, Region B. Instructor led, On-line<http://shapeblue.com/cloudstack-training/>

This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: force expunge disks

Posted by Rafael Weingartner <ra...@gmail.com>.
is there any errors on MS logs? Could you post them here?

On Wed, Jan 22, 2014 at 4:48 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote:
> The delete and expunge process work fine. it's just that for some reason we
> have few disks which failed, I'm suspecting a primary storage that would
> have been removed without emptied it.
>
>
> Pierre-Luc Dion
> Architecte de Solution Cloud | Cloud Solutions Architect
> 514-447-3456, 1101
> - - -
>
> *CloudOps*420 rue Guy
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
>
>
> On Wed, Jan 22, 2014 at 1:46 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote:
>
>> Settings expunge.delay and expunge.interval have been set to 60 long time
>> ago. I'm in the situation of a "kind of broken" system for now where in
>> cloudstack some disks are in "Expunging" state but the VDI (.vhd file)
>>  itself as been deleted from the primary storage.
>>
>>
>> Pierre-Luc Dion
>> Architecte de Solution Cloud | Cloud Solutions Architect
>> 514-447-3456, 1101
>> - - -
>>
>> *CloudOps*
>> 420 rue Guy
>> Montréal QC  H3J 1S6
>> www.cloudops.com
>> @CloudOps_
>>
>>
>> On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. <
>> hollman.enciso@gmail.com> wrote:
>>
>>> You have to wait the interval configured on global settings:
>>>
>>>
>>> expunge.delay    Determines how long (in seconds) to wait before actually
>>> expunging destroyed vm. The default value = the default value of
>>> expunge.interval
>>>
>>>
>>> expunge.interval    The interval (in seconds) to wait before running the
>>> expunge thread.
>>>
>>> I can't remember the default time, i think that it's 42 hours. i Change it
>>> to 1 hour (in seconds)
>>>
>>> and that's it
>>>
>>>
>>> On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion <pdion@cloudops.com
>>> >wrote:
>>>
>>> > I'm stuck with some disks with "Expunging" state. The the VDI for the
>>> > hypervisor is gone but the disk in Cloudstack remain in Expunging
>>> state. is
>>> > their a way to  force expunging them or updating the database to reflect
>>> > the proper state of the disk ?
>>> >
>>> > I'm tempted to execute following SQL queries but would I miss entries
>>> > somewhere else?
>>> >
>>> > update volumes set removed='2014-01-16 18:57:25', state='Expunged',
>>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1;
>>> > update volume_view set removed='2014-01-16 18:57:25', state='Expunged',
>>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1;
>>> >
>>> >
>>> > Thanks,
>>> >
>>> > Pierre-Luc Dion
>>> > Architecte de Solution Cloud | Cloud Solutions Architect
>>> > 514-447-3456, 1101
>>> > - - -
>>> >
>>> > *CloudOps*420 rue Guy
>>> > Montréal QC  H3J 1S6
>>> > www.cloudops.com
>>> > @CloudOps_
>>> >
>>>
>>>
>>>
>>> --
>>> Hollman Eduardo Enciso R.
>>> http://nexxuz.com
>>> http://algolibre.com <http://www.hollmanenciso.com/>
>>> @hollman
>>>
>>
>>



-- 
Rafael Weingärtner

Re: force expunge disks

Posted by Pierre-Luc Dion <pd...@cloudops.com>.
The delete and expunge process work fine. it's just that for some reason we
have few disks which failed, I'm suspecting a primary storage that would
have been removed without emptied it.


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Wed, Jan 22, 2014 at 1:46 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote:

> Settings expunge.delay and expunge.interval have been set to 60 long time
> ago. I'm in the situation of a "kind of broken" system for now where in
> cloudstack some disks are in "Expunging" state but the VDI (.vhd file)
>  itself as been deleted from the primary storage.
>
>
> Pierre-Luc Dion
> Architecte de Solution Cloud | Cloud Solutions Architect
> 514-447-3456, 1101
> - - -
>
> *CloudOps*
> 420 rue Guy
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
>
>
> On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. <
> hollman.enciso@gmail.com> wrote:
>
>> You have to wait the interval configured on global settings:
>>
>>
>> expunge.delay    Determines how long (in seconds) to wait before actually
>> expunging destroyed vm. The default value = the default value of
>> expunge.interval
>>
>>
>> expunge.interval    The interval (in seconds) to wait before running the
>> expunge thread.
>>
>> I can't remember the default time, i think that it's 42 hours. i Change it
>> to 1 hour (in seconds)
>>
>> and that's it
>>
>>
>> On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion <pdion@cloudops.com
>> >wrote:
>>
>> > I'm stuck with some disks with "Expunging" state. The the VDI for the
>> > hypervisor is gone but the disk in Cloudstack remain in Expunging
>> state. is
>> > their a way to  force expunging them or updating the database to reflect
>> > the proper state of the disk ?
>> >
>> > I'm tempted to execute following SQL queries but would I miss entries
>> > somewhere else?
>> >
>> > update volumes set removed='2014-01-16 18:57:25', state='Expunged',
>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1;
>> > update volume_view set removed='2014-01-16 18:57:25', state='Expunged',
>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1;
>> >
>> >
>> > Thanks,
>> >
>> > Pierre-Luc Dion
>> > Architecte de Solution Cloud | Cloud Solutions Architect
>> > 514-447-3456, 1101
>> > - - -
>> >
>> > *CloudOps*420 rue Guy
>> > Montréal QC  H3J 1S6
>> > www.cloudops.com
>> > @CloudOps_
>> >
>>
>>
>>
>> --
>> Hollman Eduardo Enciso R.
>> http://nexxuz.com
>> http://algolibre.com <http://www.hollmanenciso.com/>
>> @hollman
>>
>
>

Re: force expunge disks

Posted by Pierre-Luc Dion <pd...@cloudops.com>.
yes, Cloudstack management-server has been restart many times.


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Wed, Jan 22, 2014 at 1:48 PM, Rafael Weingartner <
rafaelweingartner@gmail.com> wrote:

> Have you restarted the cloudstack MS after you changed the parameters?
>
> On Wed, Jan 22, 2014 at 4:46 PM, Pierre-Luc Dion <pd...@cloudops.com>
> wrote:
> > Settings expunge.delay and expunge.interval have been set to 60 long time
> > ago. I'm in the situation of a "kind of broken" system for now where in
> > cloudstack some disks are in "Expunging" state but the VDI (.vhd file)
> >  itself as been deleted from the primary storage.
> >
> >
> > Pierre-Luc Dion
> > Architecte de Solution Cloud | Cloud Solutions Architect
> > 514-447-3456, 1101
> > - - -
> >
> > *CloudOps*420 rue Guy
> > Montréal QC  H3J 1S6
> > www.cloudops.com
> > @CloudOps_
> >
> >
> > On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. <
> hollman.enciso@gmail.com
> >> wrote:
> >
> >> You have to wait the interval configured on global settings:
> >>
> >>
> >> expunge.delay    Determines how long (in seconds) to wait before
> actually
> >> expunging destroyed vm. The default value = the default value of
> >> expunge.interval
> >>
> >>
> >> expunge.interval    The interval (in seconds) to wait before running the
> >> expunge thread.
> >>
> >> I can't remember the default time, i think that it's 42 hours. i Change
> it
> >> to 1 hour (in seconds)
> >>
> >> and that's it
> >>
> >>
> >> On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion <pdion@cloudops.com
> >> >wrote:
> >>
> >> > I'm stuck with some disks with "Expunging" state. The the VDI for the
> >> > hypervisor is gone but the disk in Cloudstack remain in Expunging
> state.
> >> is
> >> > their a way to  force expunging them or updating the database to
> reflect
> >> > the proper state of the disk ?
> >> >
> >> > I'm tempted to execute following SQL queries but would I miss entries
> >> > somewhere else?
> >> >
> >> > update volumes set removed='2014-01-16 18:57:25', state='Expunged',
> >> > display_volume=0 WHERE name='DATA-1442' LIMIT 1;
> >> > update volume_view set removed='2014-01-16 18:57:25',
> state='Expunged',
> >> > display_volume=0 WHERE name='DATA-1442' LIMIT 1;
> >> >
> >> >
> >> > Thanks,
> >> >
> >> > Pierre-Luc Dion
> >> > Architecte de Solution Cloud | Cloud Solutions Architect
> >> > 514-447-3456, 1101
> >> > - - -
> >> >
> >> > *CloudOps*420 rue Guy
> >> > Montréal QC  H3J 1S6
> >> > www.cloudops.com
> >> > @CloudOps_
> >> >
> >>
> >>
> >>
> >> --
> >> Hollman Eduardo Enciso R.
> >> http://nexxuz.com
> >> http://algolibre.com <http://www.hollmanenciso.com/>
> >> @hollman
> >>
>
>
>
> --
> Rafael Weingärtner
>

Re: force expunge disks

Posted by Rafael Weingartner <ra...@gmail.com>.
Have you restarted the cloudstack MS after you changed the parameters?

On Wed, Jan 22, 2014 at 4:46 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote:
> Settings expunge.delay and expunge.interval have been set to 60 long time
> ago. I'm in the situation of a "kind of broken" system for now where in
> cloudstack some disks are in "Expunging" state but the VDI (.vhd file)
>  itself as been deleted from the primary storage.
>
>
> Pierre-Luc Dion
> Architecte de Solution Cloud | Cloud Solutions Architect
> 514-447-3456, 1101
> - - -
>
> *CloudOps*420 rue Guy
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
>
>
> On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. <hollman.enciso@gmail.com
>> wrote:
>
>> You have to wait the interval configured on global settings:
>>
>>
>> expunge.delay    Determines how long (in seconds) to wait before actually
>> expunging destroyed vm. The default value = the default value of
>> expunge.interval
>>
>>
>> expunge.interval    The interval (in seconds) to wait before running the
>> expunge thread.
>>
>> I can't remember the default time, i think that it's 42 hours. i Change it
>> to 1 hour (in seconds)
>>
>> and that's it
>>
>>
>> On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion <pdion@cloudops.com
>> >wrote:
>>
>> > I'm stuck with some disks with "Expunging" state. The the VDI for the
>> > hypervisor is gone but the disk in Cloudstack remain in Expunging state.
>> is
>> > their a way to  force expunging them or updating the database to reflect
>> > the proper state of the disk ?
>> >
>> > I'm tempted to execute following SQL queries but would I miss entries
>> > somewhere else?
>> >
>> > update volumes set removed='2014-01-16 18:57:25', state='Expunged',
>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1;
>> > update volume_view set removed='2014-01-16 18:57:25', state='Expunged',
>> > display_volume=0 WHERE name='DATA-1442' LIMIT 1;
>> >
>> >
>> > Thanks,
>> >
>> > Pierre-Luc Dion
>> > Architecte de Solution Cloud | Cloud Solutions Architect
>> > 514-447-3456, 1101
>> > - - -
>> >
>> > *CloudOps*420 rue Guy
>> > Montréal QC  H3J 1S6
>> > www.cloudops.com
>> > @CloudOps_
>> >
>>
>>
>>
>> --
>> Hollman Eduardo Enciso R.
>> http://nexxuz.com
>> http://algolibre.com <http://www.hollmanenciso.com/>
>> @hollman
>>



-- 
Rafael Weingärtner

Re: force expunge disks

Posted by Pierre-Luc Dion <pd...@cloudops.com>.
Settings expunge.delay and expunge.interval have been set to 60 long time
ago. I'm in the situation of a "kind of broken" system for now where in
cloudstack some disks are in "Expunging" state but the VDI (.vhd file)
 itself as been deleted from the primary storage.


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Wed, Jan 22, 2014 at 1:31 PM, Hollman Enciso R. <hollman.enciso@gmail.com
> wrote:

> You have to wait the interval configured on global settings:
>
>
> expunge.delay    Determines how long (in seconds) to wait before actually
> expunging destroyed vm. The default value = the default value of
> expunge.interval
>
>
> expunge.interval    The interval (in seconds) to wait before running the
> expunge thread.
>
> I can't remember the default time, i think that it's 42 hours. i Change it
> to 1 hour (in seconds)
>
> and that's it
>
>
> On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion <pdion@cloudops.com
> >wrote:
>
> > I'm stuck with some disks with "Expunging" state. The the VDI for the
> > hypervisor is gone but the disk in Cloudstack remain in Expunging state.
> is
> > their a way to  force expunging them or updating the database to reflect
> > the proper state of the disk ?
> >
> > I'm tempted to execute following SQL queries but would I miss entries
> > somewhere else?
> >
> > update volumes set removed='2014-01-16 18:57:25', state='Expunged',
> > display_volume=0 WHERE name='DATA-1442' LIMIT 1;
> > update volume_view set removed='2014-01-16 18:57:25', state='Expunged',
> > display_volume=0 WHERE name='DATA-1442' LIMIT 1;
> >
> >
> > Thanks,
> >
> > Pierre-Luc Dion
> > Architecte de Solution Cloud | Cloud Solutions Architect
> > 514-447-3456, 1101
> > - - -
> >
> > *CloudOps*420 rue Guy
> > Montréal QC  H3J 1S6
> > www.cloudops.com
> > @CloudOps_
> >
>
>
>
> --
> Hollman Eduardo Enciso R.
> http://nexxuz.com
> http://algolibre.com <http://www.hollmanenciso.com/>
> @hollman
>

Re: force expunge disks

Posted by "Hollman Enciso R." <ho...@gmail.com>.
You have to wait the interval configured on global settings:


expunge.delay    Determines how long (in seconds) to wait before actually
expunging destroyed vm. The default value = the default value of
expunge.interval


expunge.interval    The interval (in seconds) to wait before running the
expunge thread.

I can't remember the default time, i think that it's 42 hours. i Change it
to 1 hour (in seconds)

and that's it


On Wed, Jan 22, 2014 at 11:24 AM, Pierre-Luc Dion <pd...@cloudops.com>wrote:

> I'm stuck with some disks with "Expunging" state. The the VDI for the
> hypervisor is gone but the disk in Cloudstack remain in Expunging state. is
> their a way to  force expunging them or updating the database to reflect
> the proper state of the disk ?
>
> I'm tempted to execute following SQL queries but would I miss entries
> somewhere else?
>
> update volumes set removed='2014-01-16 18:57:25', state='Expunged',
> display_volume=0 WHERE name='DATA-1442' LIMIT 1;
> update volume_view set removed='2014-01-16 18:57:25', state='Expunged',
> display_volume=0 WHERE name='DATA-1442' LIMIT 1;
>
>
> Thanks,
>
> Pierre-Luc Dion
> Architecte de Solution Cloud | Cloud Solutions Architect
> 514-447-3456, 1101
> - - -
>
> *CloudOps*420 rue Guy
> Montréal QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
>



-- 
Hollman Eduardo Enciso R.
http://nexxuz.com
http://algolibre.com <http://www.hollmanenciso.com/>
@hollman