Thanks for your response. I planed to add another cinder node "c01". "c01" was installed cinder-volume package, and created a VG cinder-vol.

The result by running cinder-manage host list is:

cinder-manage host list

host zone
cloud nova
c01 nova

When the VG on "cloud" was used totally, I suppose cinder-vol on "c01" should be used. So I run "cinder create --display_name multi-node-test-01 8", but:

cinder list

+--------------------------------------+-----------+--------------------+------+-------------+----------+-------------+ | ID | Status | Display Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+-----------+--------------------+------+-------------+----------+-------------+ 7ac33606-7030-4786-9b09-0eb90d781d3a | error | multi-node-test-01 | 8 | None | false | |

cinder-scheduler.log: 2013-09-13 18:13:12 ERROR [cinder.scheduler.filters.capacity_filter] Free capacity not set: volume node info collection broken. 2013-09-13 18:13:12 WARNING [cinder.scheduler.filters.capacity_filter] Insufficient free space for volume creation (requested / avail): 8/7.0 2013-09-13 18:13:12 ERROR [cinder.scheduler.manager] Failed to schedule_create_volume: No valid host was found.

At the same time I can see this on "c01": c01:~# pvscan PV /dev/loop2 VG cinder-vol lvm2 [10.00 GiB / 10.00 GiB free] Total: 1 [10.00 GiB] / in use: 1 [10.00 GiB] / in no VG: 0 [0 ]

so why the VG on c01 could not be used by cinder?

thanks again.

Hi shausy, I encountered the same problem to yours. I don't know about the formula too, kindly let me know your resolution?