[rhos-list] launch instance and create volume issues
Darren Birkett
darren.birkett at gmail.com
Fri Sep 14 15:00:29 UTC 2012
Did you reboot the machine? The loopback setup will not persist a reboot.
Run the following again:
sudo losetup -fv ~/nova-volumes
sudo vgcreate nova-volumes /dev/loop0
and then try creating a volume again.
On 14 September 2012 15:56, Xu, HongnaX <hongnax.xu at intel.com> wrote:
> the volume.log said:
> 2012-09-14 21:48:15 AUDIT nova.service [-] Starting volume node (version 2012.1.1-LOCALBRANCH:LOCALREVISION)
> 2012-09-14 21:48:15 CRITICAL nova [-] volume group nova-volumes doesn't exist
>
> My steps are:
> $sudo truncate --size 20G ~/nova-volumes
> $ sudo losetup -fv ~/nova-volumes
> $sudo vgcreate nova-volumes /dev/loop0
> *********************
> No physical volume label read from /dev/loop0
> Writing physical volume data to disk "/dev/loop0"
> Physical volume "/dev/loop0" successfully created
> Volume group "nova-volumes" successfully created
> ****************
> $sudo vgdisplay nova-volumes
> ****************
> --- Volume group ---
> VG Name nova-volumes
> System ID
> Format lvm2
> Metadata Areas 1
> Metadata Sequence No 1
> VG Access read/write
> VG Status resizable
> MAX LV 0
> Cur LV 0
> Open LV 0
> Max PV 0
> Cur PV 1
> Act PV 1
> VG Size 20.00 GiB
> PE Size 4.00 MiB
> Total PE 5119
> Alloc PE / Size 0 / 0
> Free PE / Size 5119 / 20.00 GiB
> VG UUID tslbL3-iEfc-8DPW-FXBx-vmQV-4Fcb-Dkvw0W
> **********************
> After a while or restart the service, vgdisplay nova-volumes will show Volume group "nova-volumes" not found, I don't know why.
>
> Best Regards,
> Hongna
>
> -----Original Message-----
> From: Russell Bryant [mailto:rbryant at redhat.com]
> Sent: Friday, September 14, 2012 10:45 PM
> To: darren.birkett at gmail.com
> Cc: Xu, HongnaX; rhos-list at redhat.com
> Subject: Re: [rhos-list] launch instance and create volume issues
>
> On 09/14/2012 10:35 AM, Darren Birkett wrote:
>> Hi,
>>
>> The warnings you are seeing are just debug messages from nova-manage
>> and are not relevant to your problems.
>>
>> Did you try restarting all the nova services and wait a minute?
>>
>> As for the nova-volume problem, what does the volume.log say? Do you
>> have a vg called nova-volumes?
>
> It would be good to check the other logs in /var/log/nova/ for hints about the first problem, as well.
>
> --
> Russell Bryant
More information about the rhos-list
mailing list