cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre-Luc Dion <pd...@cloudops.com>
Subject Re: force expunge disks
Date Wed, 22 Jan 2014 18:51:08 GMT
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 <pdion@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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message