When creating a volume from an image, openstack always uses root disk space?

asked 2013-06-19 09:17:20 -0600

samishah
41 ●2 ●3 ●4

I have set up cinder to use my SAN storage. When I manually create the volume using the following syntax:

cinder create --display_name testvolume1 40

The volume is created on the SAN exactly where I would expect it to be. However, when I try to create the volume from an image (to create a bootable volume), using the following syntax:

cinder create --image-id <image id=""> --display-name <display name=""> <size>

it runs my root volume out of disk space trying to create the volume, then errors out.

Is this a defect? I have checked every configuration file and do not see where it might be linked to a root directory.

edit retag flag offensive close merge delete

Comments

which backend driver are you using and what are you referring to with "my root volume" ?

gfidente ( 2013-08-16 04:34:34 -0600 )edit

2 answers

Sort by » oldest newest most voted

0

answered 2014-04-01 09:32:36 -0600

Trump.zhang
11 ●1 ●2 ●3

Can you supply more info: 1. Which cinder driver are you using? 2. How much free space is left on your backend storage?

edit flag offensive delete link

0

answered 2013-11-11 03:00:04 -0600

Super Wang
31 ●1 ●2 ●5

Did you create a volume called cinder-volume?

Let me assume you have a secondary disk at /dev/sdb, and try the following command:

pvcreate /dev/sdb
vgcreate cinder-volumes /dev/sdb
sudo service cinder-volume restart && sudo service tgt restart

edit flag offensive delete link

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-06-19 09:17:20 -0600

Seen: 1,193 times

Last updated: Apr 01 '14

Related questions