Hi Simone,

Since there is a lot of stuff in the setup log that i don't want to send to the internet, are there anything specific that i could pick out from the log?

Here is the lsbl and fdisk output from the engine:

[root@engine ~]# lsblk 

NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT

sr0     11:0    1 1024M  0 rom  

vda    253:0    0   90G  0 disk 

└─vda1 253:1    0   10G  0 part /

[root@engine ~]# fdisk -l /dev/vda

Disk /dev/vda: 96.6 GB, 96636764160 bytes, 188743680 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk label type: dos

Disk identifier: 0x0009e1bc

   Device Boot      Start         End      Blocks   Id  System

/dev/vda1   *        2048    20971519    10484736   83  Linux

2017-03-13 10:44 GMT+01:00 Simone Tiraboschi <stirabos@redhat.com>:

On Mon, Mar 13, 2017 at 8:26 AM, gflwqs gflwqs <gflwqs@gmail.com> wrote:

Hi, I have recently installed a new ovirt environment from scratch.

The version is 4.1.0.

I made a 90GB disk for the hosted engine.

When i had installed it and log into the engine i see that it has only configured 10GB of those 90GB.

So there is 80GB of unconfigured disk unused.

Can you please attach your hosted-engine-setup log file?

Could you please check if the disk is 90GB but the main disk partition is just 10 GB?

cloud-utils-growpart should grow the partition on the first boot, if the issue is there we need to understand why it didn't triggered in your case.

 

That is fine as long as it had used lvm but it has not meaning i have to take the engine down to extend the disk?

My questions is:

1. Why does it not configure all disk?

2. Why is it not using lvm?

3. What should i do to extend the disk?

It depends on where the issue is (is on the disk size or just on the partition size?).

 

Regards

Christian

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users