On 10/03/2012 03:04 PM, Alex Huang wrote:
-----Original Message-----
From: Nik Martin [mailto:nik.mar...@nfinausa.com]
Sent: Wednesday, October 03, 2012 12:27 PM
To: cloudstack-users@incubator.apache.org
Subject: Re: Storage failure in not handled well in CS
https://issues.apache.org/jira/browse/CLOUDSTACK-251
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"
Martin,
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.
--Alex
ALex,
Thank you for the update and feedback.
--
Regards,
Nik
Nik Martin
VP Business Development
Nfina Technologies, Inc.
+1.251.243.0043 x1003
Relentless Reliability
