Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1447D106FB for ; Wed, 22 Jan 2014 18:32:21 +0000 (UTC) Received: (qmail 28899 invoked by uid 500); 22 Jan 2014 18:32:19 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 28860 invoked by uid 500); 22 Jan 2014 18:32:18 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 28846 invoked by uid 99); 22 Jan 2014 18:32:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jan 2014 18:32:17 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of hollman.enciso@gmail.com designates 209.85.215.179 as permitted sender) Received: from [209.85.215.179] (HELO mail-ea0-f179.google.com) (209.85.215.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jan 2014 18:32:11 +0000 Received: by mail-ea0-f179.google.com with SMTP id q10so3643317ead.38 for ; Wed, 22 Jan 2014 10:31:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=qU0/qFglU+V8BTvxf/JgT1NzUGZQzo73i6u93m96Us8=; b=N+2TewAO9yfgup/kOijFLxZ9e+tUBUC7LltL8wyHZlaLA60sfRquThhuh7YzflOSRI 9ISxo4liOeuz7218jnrisutkiwKQjOWzIekb2QNskyF4xqkoZEwq338DO9S64rdKB3qM hiuP9wzbEdR9O7cqfqCkG1MzxeFiqb9oZ7b4ZNikQUn+GmONFrc+7yrr8TsvjBG+zt2C cJUeurj+Mqw1cVR3izRMwc5Xsi6rI2jE21ZEUODxXjn/Cv/DJvL2+njEwppHbP/CysxZ 6i9KvaZPpMxLYkrKXUVLdhL6pSbx9ygCMwGadk3WW+mK31KsFnsgUOhKiw/DfJs31Ke5 1RRQ== X-Received: by 10.14.241.142 with SMTP id g14mr3113861eer.40.1390415511323; Wed, 22 Jan 2014 10:31:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.38.193 with HTTP; Wed, 22 Jan 2014 10:31:31 -0800 (PST) In-Reply-To: References: From: "Hollman Enciso R." Date: Wed, 22 Jan 2014 13:31:31 -0500 Message-ID: Subject: Re: force expunge disks To: users@cloudstack.apache.org Content-Type: multipart/alternative; boundary=001a1132f64aa48a3d04f0935600 X-Virus-Checked: Checked by ClamAV on apache.org --001a1132f64aa48a3d04f0935600 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 =3D 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 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=3D'2014-01-16 18:57:25', state=3D'Expunged', > display_volume=3D0 WHERE name=3D'DATA-1442' LIMIT 1; > update volume_view set removed=3D'2014-01-16 18:57:25', state=3D'Expunged= ', > display_volume=3D0 WHERE name=3D'DATA-1442' LIMIT 1; > > > Thanks, > > Pierre-Luc Dion > Architecte de Solution Cloud | Cloud Solutions Architect > 514-447-3456, 1101 > - - - > > *CloudOps*420 rue Guy > Montr=C3=A9al QC H3J 1S6 > www.cloudops.com > @CloudOps_ > --=20 Hollman Eduardo Enciso R. http://nexxuz.com http://algolibre.com @hollman --001a1132f64aa48a3d04f0935600--