You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Alessandro Caviglione <c....@gmail.com> on 2017/11/15 16:23:56 UTC
Unable to locate datastore
Hi guys,
I'm trying to delete a Primary datastore, but when I try to delete it I got
this error:
Unable to locate datastore with id 11
In the database, I see:
11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728 7672016928768
192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42 2016-08-29
12:26:26 Maintenance DefaultPrimary CLUSTER 0
12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec NetworkFilesystem
2049 1 1 2 4085454602240 7672016928768 192.168.200.25
/volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary CLUSTER 0
In fact, 11 and 12 are the same primary storage but for a strange reason,
11 is in maintenance and does not have an ID....
How can I solve?
Could I copy all the data from 12 to 11 and delete the primary storage I
want to delete?
Keep in mind that the storage I need to delete is another one, not
CH1-PRI-SATA-2
Thank you.
Re: Unable to locate datastore
Posted by Rafael Weingärtner <ra...@gmail.com>.
Well... Then, I have no idea how you are getting that error.
According with information posted by you, you do not have entries in
volumes table that have the pool_id = 11.
On Wed, Nov 15, 2017 at 4:25 PM, Alessandro Caviglione <
c.alessandro@gmail.com> wrote:
> select v.* from cloud.snapshots s join
> cloud.volumes v on v.id = s.volume_id
> where
> pool_id = 11
>
> 0 rows returned
>
> Second query you wrote is the same :)
>
>
>
> On Wed, Nov 15, 2017 at 7:24 PM, Rafael Weingärtner <
> rafaelweingartner@gmail.com> wrote:
>
> > Can you post the query you executed?
> >
> > On Wed, Nov 15, 2017 at 4:22 PM, Alessandro Caviglione <
> > c.alessandro@gmail.com> wrote:
> >
> > > Sorry... I forgot to select cloud database and Rafael query returns an
> > > error....
> > > I've fixed and 0 rows returned!
> > >
> > > On Wed, Nov 15, 2017 at 7:19 PM, Alessandro Caviglione <
> > > c.alessandro@gmail.com> wrote:
> > >
> > > > Maybe I tried to delete storage 11 but it still here with id 12!
> > > > Rafael query does not work, SELECT * FROM cloud.storage_pool_host_ref
> > > > where pool_id=11 returns no result.
> > > >
> > > > On Wed, Nov 15, 2017 at 5:53 PM, Dag Sonstebo <
> > > Dag.Sonstebo@shapeblue.com>
> > > > wrote:
> > > >
> > > >> As Rafael says – it looks like primary store 11 is already deleted –
> > you
> > > >> have a removed date of 2016-08-29 12:26:26 (just check that this is
> > > indeed
> > > >> the removed date and not the “update_time” – the two columns follow
> > each
> > > >> other).
> > > >>
> > > >> 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728
> > > 7672016928768
> > > >> 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42
> 2016-08-29
> > > >> 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> > > >> 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec
> > > NetworkFilesystem
> > > >> 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> > > >> /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary
> CLUSTER
> > 0
> > > >>
> > > >> Also check your host to pool config:
> > > >>
> > > >> SELECT * FROM cloud.storage_pool_host_ref where pool_id=11;
> > > >>
> > > >> This will show you if pool 11 is attached to any hosts. Apart from
> > that
> > > >> check the volumes and snapshots as Rafael suggests to make sure
> > > CloudStack
> > > >> doesn’t think pool 11 is still in use.
> > > >>
> > > >> (and appreciate you want to delete another pool – not sure why it
> > would
> > > >> complain about 11, but if you get to the bottom of the above
> hopefully
> > > the
> > > >> other deletion will work)
> > > >>
> > > >> Regards,
> > > >> Dag Sonstebo
> > > >> Cloud Architect
> > > >> ShapeBlue
> > > >>
> > > >> On 15/11/2017, 16:31, "Rafael Weingärtner" <
> > rafaelweingartner@gmail.com
> > > >
> > > >> wrote:
> > > >>
> > > >> Was this storage with ID 11 deleted?
> > > >> You can check everything allocated in it by issue the following
> > > SQLs:
> > > >>
> > > >> To find all snapshots:
> > > >> select s.* from snapshots s join
> > > >> volumes v on v.id = s.volume_id
> > > >> where
> > > >> pool_id = ?
> > > >>
> > > >> To find all volumes:
> > > >> select v.* from snapshots s join
> > > >> volumes v on v.id = s.volume_id
> > > >> where
> > > >> pool_id = ?
> > > >>
> > > >>
> > > >> On Wed, Nov 15, 2017 at 2:23 PM, Alessandro Caviglione <
> > > >> c.alessandro@gmail.com> wrote:
> > > >>
> > > >> > Hi guys,
> > > >> > I'm trying to delete a Primary datastore, but when I try to
> > delete
> > > >> it I got
> > > >> > this error:
> > > >> >
> > > >> > Unable to locate datastore with id 11
> > > >> >
> > > >> > In the database, I see:
> > > >> >
> > > >> > 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728
> > > >> 7672016928768
> > > >> > 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42
> > > >> 2016-08-29
> > > >> > 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> > > >> > 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec
> > > >> NetworkFilesystem
> > > >> > 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> > > >> > /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary
> > > >> CLUSTER 0
> > > >> >
> > > >> > In fact, 11 and 12 are the same primary storage but for a
> > strange
> > > >> reason,
> > > >> > 11 is in maintenance and does not have an ID....
> > > >> >
> > > >> > How can I solve?
> > > >> > Could I copy all the data from 12 to 11 and delete the primary
> > > >> storage I
> > > >> > want to delete?
> > > >> > Keep in mind that the storage I need to delete is another one,
> > not
> > > >> > CH1-PRI-SATA-2
> > > >> >
> > > >> > Thank you.
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Rafael Weingärtner
> > > >>
> > > >>
> > > >>
> > > >> Dag.Sonstebo@shapeblue.com
> > > >> www.shapeblue.com
> > > >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > > >> @shapeblue
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > >
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>
--
Rafael Weingärtner
Re: Unable to locate datastore
Posted by Alessandro Caviglione <c....@gmail.com>.
select v.* from cloud.snapshots s join
cloud.volumes v on v.id = s.volume_id
where
pool_id = 11
0 rows returned
Second query you wrote is the same :)
On Wed, Nov 15, 2017 at 7:24 PM, Rafael Weingärtner <
rafaelweingartner@gmail.com> wrote:
> Can you post the query you executed?
>
> On Wed, Nov 15, 2017 at 4:22 PM, Alessandro Caviglione <
> c.alessandro@gmail.com> wrote:
>
> > Sorry... I forgot to select cloud database and Rafael query returns an
> > error....
> > I've fixed and 0 rows returned!
> >
> > On Wed, Nov 15, 2017 at 7:19 PM, Alessandro Caviglione <
> > c.alessandro@gmail.com> wrote:
> >
> > > Maybe I tried to delete storage 11 but it still here with id 12!
> > > Rafael query does not work, SELECT * FROM cloud.storage_pool_host_ref
> > > where pool_id=11 returns no result.
> > >
> > > On Wed, Nov 15, 2017 at 5:53 PM, Dag Sonstebo <
> > Dag.Sonstebo@shapeblue.com>
> > > wrote:
> > >
> > >> As Rafael says – it looks like primary store 11 is already deleted –
> you
> > >> have a removed date of 2016-08-29 12:26:26 (just check that this is
> > indeed
> > >> the removed date and not the “update_time” – the two columns follow
> each
> > >> other).
> > >>
> > >> 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728
> > 7672016928768
> > >> 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42 2016-08-29
> > >> 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> > >> 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec
> > NetworkFilesystem
> > >> 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> > >> /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary CLUSTER
> 0
> > >>
> > >> Also check your host to pool config:
> > >>
> > >> SELECT * FROM cloud.storage_pool_host_ref where pool_id=11;
> > >>
> > >> This will show you if pool 11 is attached to any hosts. Apart from
> that
> > >> check the volumes and snapshots as Rafael suggests to make sure
> > CloudStack
> > >> doesn’t think pool 11 is still in use.
> > >>
> > >> (and appreciate you want to delete another pool – not sure why it
> would
> > >> complain about 11, but if you get to the bottom of the above hopefully
> > the
> > >> other deletion will work)
> > >>
> > >> Regards,
> > >> Dag Sonstebo
> > >> Cloud Architect
> > >> ShapeBlue
> > >>
> > >> On 15/11/2017, 16:31, "Rafael Weingärtner" <
> rafaelweingartner@gmail.com
> > >
> > >> wrote:
> > >>
> > >> Was this storage with ID 11 deleted?
> > >> You can check everything allocated in it by issue the following
> > SQLs:
> > >>
> > >> To find all snapshots:
> > >> select s.* from snapshots s join
> > >> volumes v on v.id = s.volume_id
> > >> where
> > >> pool_id = ?
> > >>
> > >> To find all volumes:
> > >> select v.* from snapshots s join
> > >> volumes v on v.id = s.volume_id
> > >> where
> > >> pool_id = ?
> > >>
> > >>
> > >> On Wed, Nov 15, 2017 at 2:23 PM, Alessandro Caviglione <
> > >> c.alessandro@gmail.com> wrote:
> > >>
> > >> > Hi guys,
> > >> > I'm trying to delete a Primary datastore, but when I try to
> delete
> > >> it I got
> > >> > this error:
> > >> >
> > >> > Unable to locate datastore with id 11
> > >> >
> > >> > In the database, I see:
> > >> >
> > >> > 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728
> > >> 7672016928768
> > >> > 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42
> > >> 2016-08-29
> > >> > 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> > >> > 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec
> > >> NetworkFilesystem
> > >> > 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> > >> > /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary
> > >> CLUSTER 0
> > >> >
> > >> > In fact, 11 and 12 are the same primary storage but for a
> strange
> > >> reason,
> > >> > 11 is in maintenance and does not have an ID....
> > >> >
> > >> > How can I solve?
> > >> > Could I copy all the data from 12 to 11 and delete the primary
> > >> storage I
> > >> > want to delete?
> > >> > Keep in mind that the storage I need to delete is another one,
> not
> > >> > CH1-PRI-SATA-2
> > >> >
> > >> > Thank you.
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Rafael Weingärtner
> > >>
> > >>
> > >>
> > >> Dag.Sonstebo@shapeblue.com
> > >> www.shapeblue.com
> > >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > >> @shapeblue
> > >>
> > >>
> > >>
> > >>
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>
Re: Unable to locate datastore
Posted by Rafael Weingärtner <ra...@gmail.com>.
Can you post the query you executed?
On Wed, Nov 15, 2017 at 4:22 PM, Alessandro Caviglione <
c.alessandro@gmail.com> wrote:
> Sorry... I forgot to select cloud database and Rafael query returns an
> error....
> I've fixed and 0 rows returned!
>
> On Wed, Nov 15, 2017 at 7:19 PM, Alessandro Caviglione <
> c.alessandro@gmail.com> wrote:
>
> > Maybe I tried to delete storage 11 but it still here with id 12!
> > Rafael query does not work, SELECT * FROM cloud.storage_pool_host_ref
> > where pool_id=11 returns no result.
> >
> > On Wed, Nov 15, 2017 at 5:53 PM, Dag Sonstebo <
> Dag.Sonstebo@shapeblue.com>
> > wrote:
> >
> >> As Rafael says – it looks like primary store 11 is already deleted – you
> >> have a removed date of 2016-08-29 12:26:26 (just check that this is
> indeed
> >> the removed date and not the “update_time” – the two columns follow each
> >> other).
> >>
> >> 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728
> 7672016928768
> >> 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42 2016-08-29
> >> 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> >> 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec
> NetworkFilesystem
> >> 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> >> /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary CLUSTER 0
> >>
> >> Also check your host to pool config:
> >>
> >> SELECT * FROM cloud.storage_pool_host_ref where pool_id=11;
> >>
> >> This will show you if pool 11 is attached to any hosts. Apart from that
> >> check the volumes and snapshots as Rafael suggests to make sure
> CloudStack
> >> doesn’t think pool 11 is still in use.
> >>
> >> (and appreciate you want to delete another pool – not sure why it would
> >> complain about 11, but if you get to the bottom of the above hopefully
> the
> >> other deletion will work)
> >>
> >> Regards,
> >> Dag Sonstebo
> >> Cloud Architect
> >> ShapeBlue
> >>
> >> On 15/11/2017, 16:31, "Rafael Weingärtner" <rafaelweingartner@gmail.com
> >
> >> wrote:
> >>
> >> Was this storage with ID 11 deleted?
> >> You can check everything allocated in it by issue the following
> SQLs:
> >>
> >> To find all snapshots:
> >> select s.* from snapshots s join
> >> volumes v on v.id = s.volume_id
> >> where
> >> pool_id = ?
> >>
> >> To find all volumes:
> >> select v.* from snapshots s join
> >> volumes v on v.id = s.volume_id
> >> where
> >> pool_id = ?
> >>
> >>
> >> On Wed, Nov 15, 2017 at 2:23 PM, Alessandro Caviglione <
> >> c.alessandro@gmail.com> wrote:
> >>
> >> > Hi guys,
> >> > I'm trying to delete a Primary datastore, but when I try to delete
> >> it I got
> >> > this error:
> >> >
> >> > Unable to locate datastore with id 11
> >> >
> >> > In the database, I see:
> >> >
> >> > 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728
> >> 7672016928768
> >> > 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42
> >> 2016-08-29
> >> > 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> >> > 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec
> >> NetworkFilesystem
> >> > 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> >> > /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary
> >> CLUSTER 0
> >> >
> >> > In fact, 11 and 12 are the same primary storage but for a strange
> >> reason,
> >> > 11 is in maintenance and does not have an ID....
> >> >
> >> > How can I solve?
> >> > Could I copy all the data from 12 to 11 and delete the primary
> >> storage I
> >> > want to delete?
> >> > Keep in mind that the storage I need to delete is another one, not
> >> > CH1-PRI-SATA-2
> >> >
> >> > Thank you.
> >> >
> >>
> >>
> >>
> >> --
> >> Rafael Weingärtner
> >>
> >>
> >>
> >> Dag.Sonstebo@shapeblue.com
> >> www.shapeblue.com
> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >> @shapeblue
> >>
> >>
> >>
> >>
> >
>
--
Rafael Weingärtner
Re: Unable to locate datastore
Posted by Alessandro Caviglione <c....@gmail.com>.
Sorry... I forgot to select cloud database and Rafael query returns an
error....
I've fixed and 0 rows returned!
On Wed, Nov 15, 2017 at 7:19 PM, Alessandro Caviglione <
c.alessandro@gmail.com> wrote:
> Maybe I tried to delete storage 11 but it still here with id 12!
> Rafael query does not work, SELECT * FROM cloud.storage_pool_host_ref
> where pool_id=11 returns no result.
>
> On Wed, Nov 15, 2017 at 5:53 PM, Dag Sonstebo <Da...@shapeblue.com>
> wrote:
>
>> As Rafael says – it looks like primary store 11 is already deleted – you
>> have a removed date of 2016-08-29 12:26:26 (just check that this is indeed
>> the removed date and not the “update_time” – the two columns follow each
>> other).
>>
>> 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728 7672016928768
>> 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42 2016-08-29
>> 12:26:26 Maintenance DefaultPrimary CLUSTER 0
>> 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec NetworkFilesystem
>> 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
>> /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary CLUSTER 0
>>
>> Also check your host to pool config:
>>
>> SELECT * FROM cloud.storage_pool_host_ref where pool_id=11;
>>
>> This will show you if pool 11 is attached to any hosts. Apart from that
>> check the volumes and snapshots as Rafael suggests to make sure CloudStack
>> doesn’t think pool 11 is still in use.
>>
>> (and appreciate you want to delete another pool – not sure why it would
>> complain about 11, but if you get to the bottom of the above hopefully the
>> other deletion will work)
>>
>> Regards,
>> Dag Sonstebo
>> Cloud Architect
>> ShapeBlue
>>
>> On 15/11/2017, 16:31, "Rafael Weingärtner" <ra...@gmail.com>
>> wrote:
>>
>> Was this storage with ID 11 deleted?
>> You can check everything allocated in it by issue the following SQLs:
>>
>> To find all snapshots:
>> select s.* from snapshots s join
>> volumes v on v.id = s.volume_id
>> where
>> pool_id = ?
>>
>> To find all volumes:
>> select v.* from snapshots s join
>> volumes v on v.id = s.volume_id
>> where
>> pool_id = ?
>>
>>
>> On Wed, Nov 15, 2017 at 2:23 PM, Alessandro Caviglione <
>> c.alessandro@gmail.com> wrote:
>>
>> > Hi guys,
>> > I'm trying to delete a Primary datastore, but when I try to delete
>> it I got
>> > this error:
>> >
>> > Unable to locate datastore with id 11
>> >
>> > In the database, I see:
>> >
>> > 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728
>> 7672016928768
>> > 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42
>> 2016-08-29
>> > 12:26:26 Maintenance DefaultPrimary CLUSTER 0
>> > 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec
>> NetworkFilesystem
>> > 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
>> > /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary
>> CLUSTER 0
>> >
>> > In fact, 11 and 12 are the same primary storage but for a strange
>> reason,
>> > 11 is in maintenance and does not have an ID....
>> >
>> > How can I solve?
>> > Could I copy all the data from 12 to 11 and delete the primary
>> storage I
>> > want to delete?
>> > Keep in mind that the storage I need to delete is another one, not
>> > CH1-PRI-SATA-2
>> >
>> > Thank you.
>> >
>>
>>
>>
>> --
>> Rafael Weingärtner
>>
>>
>>
>> Dag.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>>
>
Re: Unable to locate datastore
Posted by Rafael Weingärtner <ra...@gmail.com>.
What query does not work?
Can you post the SQL result of your storage_pool table filtering by ID=11
(do not remove the metadata fields).
On Wed, Nov 15, 2017 at 4:19 PM, Alessandro Caviglione <
c.alessandro@gmail.com> wrote:
> Maybe I tried to delete storage 11 but it still here with id 12!
> Rafael query does not work, SELECT * FROM cloud.storage_pool_host_ref where
> pool_id=11 returns no result.
>
> On Wed, Nov 15, 2017 at 5:53 PM, Dag Sonstebo <Da...@shapeblue.com>
> wrote:
>
> > As Rafael says – it looks like primary store 11 is already deleted – you
> > have a removed date of 2016-08-29 12:26:26 (just check that this is
> indeed
> > the removed date and not the “update_time” – the two columns follow each
> > other).
> >
> > 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728 7672016928768
> > 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42 2016-08-29
> > 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> > 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec NetworkFilesystem
> > 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> > /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary CLUSTER 0
> >
> > Also check your host to pool config:
> >
> > SELECT * FROM cloud.storage_pool_host_ref where pool_id=11;
> >
> > This will show you if pool 11 is attached to any hosts. Apart from that
> > check the volumes and snapshots as Rafael suggests to make sure
> CloudStack
> > doesn’t think pool 11 is still in use.
> >
> > (and appreciate you want to delete another pool – not sure why it would
> > complain about 11, but if you get to the bottom of the above hopefully
> the
> > other deletion will work)
> >
> > Regards,
> > Dag Sonstebo
> > Cloud Architect
> > ShapeBlue
> >
> > On 15/11/2017, 16:31, "Rafael Weingärtner" <ra...@gmail.com>
> > wrote:
> >
> > Was this storage with ID 11 deleted?
> > You can check everything allocated in it by issue the following SQLs:
> >
> > To find all snapshots:
> > select s.* from snapshots s join
> > volumes v on v.id = s.volume_id
> > where
> > pool_id = ?
> >
> > To find all volumes:
> > select v.* from snapshots s join
> > volumes v on v.id = s.volume_id
> > where
> > pool_id = ?
> >
> >
> > On Wed, Nov 15, 2017 at 2:23 PM, Alessandro Caviglione <
> > c.alessandro@gmail.com> wrote:
> >
> > > Hi guys,
> > > I'm trying to delete a Primary datastore, but when I try to delete
> > it I got
> > > this error:
> > >
> > > Unable to locate datastore with id 11
> > >
> > > In the database, I see:
> > >
> > > 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728
> > 7672016928768
> > > 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42
> 2016-08-29
> > > 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> > > 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec
> > NetworkFilesystem
> > > 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> > > /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary
> > CLUSTER 0
> > >
> > > In fact, 11 and 12 are the same primary storage but for a strange
> > reason,
> > > 11 is in maintenance and does not have an ID....
> > >
> > > How can I solve?
> > > Could I copy all the data from 12 to 11 and delete the primary
> > storage I
> > > want to delete?
> > > Keep in mind that the storage I need to delete is another one, not
> > > CH1-PRI-SATA-2
> > >
> > > Thank you.
> > >
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
> >
> >
> > Dag.Sonstebo@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
>
--
Rafael Weingärtner
Re: Unable to locate datastore
Posted by Alessandro Caviglione <c....@gmail.com>.
Maybe I tried to delete storage 11 but it still here with id 12!
Rafael query does not work, SELECT * FROM cloud.storage_pool_host_ref where
pool_id=11 returns no result.
On Wed, Nov 15, 2017 at 5:53 PM, Dag Sonstebo <Da...@shapeblue.com>
wrote:
> As Rafael says – it looks like primary store 11 is already deleted – you
> have a removed date of 2016-08-29 12:26:26 (just check that this is indeed
> the removed date and not the “update_time” – the two columns follow each
> other).
>
> 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728 7672016928768
> 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42 2016-08-29
> 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec NetworkFilesystem
> 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary CLUSTER 0
>
> Also check your host to pool config:
>
> SELECT * FROM cloud.storage_pool_host_ref where pool_id=11;
>
> This will show you if pool 11 is attached to any hosts. Apart from that
> check the volumes and snapshots as Rafael suggests to make sure CloudStack
> doesn’t think pool 11 is still in use.
>
> (and appreciate you want to delete another pool – not sure why it would
> complain about 11, but if you get to the bottom of the above hopefully the
> other deletion will work)
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 15/11/2017, 16:31, "Rafael Weingärtner" <ra...@gmail.com>
> wrote:
>
> Was this storage with ID 11 deleted?
> You can check everything allocated in it by issue the following SQLs:
>
> To find all snapshots:
> select s.* from snapshots s join
> volumes v on v.id = s.volume_id
> where
> pool_id = ?
>
> To find all volumes:
> select v.* from snapshots s join
> volumes v on v.id = s.volume_id
> where
> pool_id = ?
>
>
> On Wed, Nov 15, 2017 at 2:23 PM, Alessandro Caviglione <
> c.alessandro@gmail.com> wrote:
>
> > Hi guys,
> > I'm trying to delete a Primary datastore, but when I try to delete
> it I got
> > this error:
> >
> > Unable to locate datastore with id 11
> >
> > In the database, I see:
> >
> > 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728
> 7672016928768
> > 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42 2016-08-29
> > 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> > 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec
> NetworkFilesystem
> > 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> > /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary
> CLUSTER 0
> >
> > In fact, 11 and 12 are the same primary storage but for a strange
> reason,
> > 11 is in maintenance and does not have an ID....
> >
> > How can I solve?
> > Could I copy all the data from 12 to 11 and delete the primary
> storage I
> > want to delete?
> > Keep in mind that the storage I need to delete is another one, not
> > CH1-PRI-SATA-2
> >
> > Thank you.
> >
>
>
>
> --
> Rafael Weingärtner
>
>
>
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
Re: Unable to locate datastore
Posted by Dag Sonstebo <Da...@shapeblue.com>.
As Rafael says – it looks like primary store 11 is already deleted – you have a removed date of 2016-08-29 12:26:26 (just check that this is indeed the removed date and not the “update_time” – the two columns follow each other).
11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728 7672016928768 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42 2016-08-29 12:26:26 Maintenance DefaultPrimary CLUSTER 0
12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec NetworkFilesystem 2049 1 1 2 4085454602240 7672016928768 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary CLUSTER 0
Also check your host to pool config:
SELECT * FROM cloud.storage_pool_host_ref where pool_id=11;
This will show you if pool 11 is attached to any hosts. Apart from that check the volumes and snapshots as Rafael suggests to make sure CloudStack doesn’t think pool 11 is still in use.
(and appreciate you want to delete another pool – not sure why it would complain about 11, but if you get to the bottom of the above hopefully the other deletion will work)
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 15/11/2017, 16:31, "Rafael Weingärtner" <ra...@gmail.com> wrote:
Was this storage with ID 11 deleted?
You can check everything allocated in it by issue the following SQLs:
To find all snapshots:
select s.* from snapshots s join
volumes v on v.id = s.volume_id
where
pool_id = ?
To find all volumes:
select v.* from snapshots s join
volumes v on v.id = s.volume_id
where
pool_id = ?
On Wed, Nov 15, 2017 at 2:23 PM, Alessandro Caviglione <
c.alessandro@gmail.com> wrote:
> Hi guys,
> I'm trying to delete a Primary datastore, but when I try to delete it I got
> this error:
>
> Unable to locate datastore with id 11
>
> In the database, I see:
>
> 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728 7672016928768
> 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42 2016-08-29
> 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec NetworkFilesystem
> 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary CLUSTER 0
>
> In fact, 11 and 12 are the same primary storage but for a strange reason,
> 11 is in maintenance and does not have an ID....
>
> How can I solve?
> Could I copy all the data from 12 to 11 and delete the primary storage I
> want to delete?
> Keep in mind that the storage I need to delete is another one, not
> CH1-PRI-SATA-2
>
> Thank you.
>
--
Rafael Weingärtner
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Re: Unable to locate datastore
Posted by Rafael Weingärtner <ra...@gmail.com>.
Was this storage with ID 11 deleted?
You can check everything allocated in it by issue the following SQLs:
To find all snapshots:
select s.* from snapshots s join
volumes v on v.id = s.volume_id
where
pool_id = ?
To find all volumes:
select v.* from snapshots s join
volumes v on v.id = s.volume_id
where
pool_id = ?
On Wed, Nov 15, 2017 at 2:23 PM, Alessandro Caviglione <
c.alessandro@gmail.com> wrote:
> Hi guys,
> I'm trying to delete a Primary datastore, but when I try to delete it I got
> this error:
>
> Unable to locate datastore with id 11
>
> In the database, I see:
>
> 11 CH1-PRI-SATA-2 NetworkFilesystem 2049 1 1 2 171773001728 7672016928768
> 192.168.200.25 /volume2/CH1-PRI-SATA-2 2016-08-24 20:57:42 2016-08-29
> 12:26:26 Maintenance DefaultPrimary CLUSTER 0
> 12 CH1-PRI-SATA-2 d4349999-8c54-3efa-a90a-98a35fdfbdec NetworkFilesystem
> 2049 1 1 2 4085454602240 7672016928768 192.168.200.25
> /volume2/CH1-PRI-SATA-2 2016-08-29 12:28:06 Up DefaultPrimary CLUSTER 0
>
> In fact, 11 and 12 are the same primary storage but for a strange reason,
> 11 is in maintenance and does not have an ID....
>
> How can I solve?
> Could I copy all the data from 12 to 11 and delete the primary storage I
> want to delete?
> Keep in mind that the storage I need to delete is another one, not
> CH1-PRI-SATA-2
>
> Thank you.
>
--
Rafael Weingärtner