NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

OpenStack Discussions

Insufficient free space for thin provisioning

LucasCozinheiro
7,043 Views

Good morning,

I've installed a new OpenStack single host but I'm having some troubles on Cinder module. I'm getting the following warning message, so any instance using a big volume fails when launching.

 

2018-02-28 17:30:33.463 12381 WARNING cinder.scheduler.filters.capacity_filter [req-bc96b3c4-820d-4851-8d54-800971a61ce6 2097652168834963b3374aa5edcd8a1d 35d9b1a4b0ee493c8935a5ca09247dc0 - default default] Insufficient free space for thin provisioning. The ratio of provisioned capacity over total capacity 1.02 has exceeded the maximum over subscription ratio 1.00

 

I think that the solution should be to change the maximum over subscription value, however when I change the cinder.conf file, the OpenStack loose the connectivity with Cinder module.

Thanks.

5 REPLIES 5

dblackwe
7,012 Views

What backend are you using for your Cinder storage?

LucasCozinheiro
7,010 Views

I'm using the default configuration. I didn't change any parameters.

dblackwe
7,007 Views

In that case you are using LVM as your Cinder backend, not NetApp storage of any kind.  Yes you can increase your ratio, but restarting the Cinder service to read it does interupt service.

LucasCozinheiro
7,000 Views

Is there a command to change the ratio value? Maybe I'm doing something wrong when I do it manually using the config file. Thanks

dblackwe
6,997 Views

We normally just answer questions for OpenStack around NetApp products, but

 

Its all in the cinder.conf file.  You need to make sure your lvm_type flag is set to thin or you can't oversubscribe at all.  Then just update your max_over_subscription_ration to 2.0 or 3.0 save and restart all cinder services.

Public