cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Huang <>
Subject RE: Storage failure in not handled well in CS
Date Wed, 03 Oct 2012 20:04:50 GMT

> -----Original Message-----
> From: Nik Martin []
> Sent: Wednesday, October 03, 2012 12:27 PM
> To:
> Subject: Re: Storage failure in not handled well in CS
> On 10/03/2012 02:11 PM, Anthony Xu wrote:
> > It is a bug, please file a bug,
> >
> > You can try following workaround,
> > In mysql
> > Update storage_pool set removed=now() where id= "primary storage id
> you put into maintenance mode"


This should not happen.  I've raised the priority on the bug itself.

I want to make sure you understand the implications of the sql Anthony sent.  This will temporarily
remove the storage_pool from CloudStack because removed column is not null means CloudStack
data access layer won't even retrieve the storage pool.  There may be things that appear broken
while this is true.  For example, when you retrieve volumes stored on that storage pool, cloudstack
won't be able to retrieve any information on the storage pool because it can't see it.  To
get it back in working order, you have to "update storage_pool set removed=null where id =
[primary storage pool id]".

You should still put the storage pool into maintenance mode before you run Anthony's sql.

View raw message