Cinder created Volume, Attach after the virtual machine is not / dev / vdc

RT, with the 2G Cinder create a volume, but attach to the instance, enter the instance used inside fdisk-l did not find / dev / vdc the disk, attach the time to write is / dev / vdc. This is why? Some encountered it?
This is the example of internal execution fdisk-l results:


This is the flavor of the case:


This is the volume of the case:


This is the instance of the situation:


virtual machine is a centos 5.5 system.


------ Solution ------------------------------------ --------------------
after re-starting with.
------ Solution ---------- ----------------------------------------------
this do not tangle, is the operating system problems, nothing to do with OpenStack, every time you add devices to the system, the system will automatically assign the device number / dev / vdb, c, d increments continue, even if the same volume is repeatedly attached to the system, will have a different name.
This is OpenStack and libvirt source from the analysis of the conclusions, and both did nothing.
------ For reference only -------------------------------------- ------------------
not encountered such a situation.
You can provide more detailed information:
1, openstack version number
2, nova and cinder log
3, more helpful information
------ For reference only -------------------------- ------------------------------
Thank you for your answer, but finally own solution. cinder on ubuntu12.10 system seems somewhat similar to patch the package, installation is finished you can attach up; did before the installation can not attach the mirror is produced, I redo a mirror just fine. The final step is to recognize the need to restart some instances the additional volumes, this and usaspy said the same, this adjustment cinder in my problems on the ubuntu12.10 no longer exists.

Finally, ddl007 may not understand what I mean, my question was not attach the volume does not appear as / dev / vdc Instead, simply do not recognize. I attach the volume only 2G, the above figure is already apparent.

Finally thanks for your answer. Thank you!
------ For reference only -------------------------------------- ------------------

Hello, your last question is how to solve it? I encountered the same problem with you. . .
------ For reference only -------------------------------------- ------------------


I fainted attach not problem, and nothing in the log file prompt. Somewhat similar to the patch package? ? What package? Could you tell me the chant