Windows 2012 VM and Ubuntu 18.04

Asked by Ronald RiemVis on 2019-12-01

Using Ubuntu I8.04 in the Virtual machine within Server 2012 I found out that disk space is not dynamic.
I had to remove and install again this server to meet the space needed for update.
To avoid future problems I created a larger disc from total 27 Gbyte.
After install webmin (Dashboard) I see the disc size to be 2,82 Gbyte used / 2 GByte Free / 4.83 GByte total
In webmin going to Hardware => Partions on Local Disc I see
partion 1 Linux EXT = 8.03 Mbyte from 1 to 1
partion 2 Linux EXT = 1.03 Gbyte from 1 to 131
partion 3 Linux EXT = 26.63 Gbyte from 131 to 3525

Why report Webmin the total disc size in the dashboard to be only 4.83 Gbyte?

Is this a bug or?

Greetings,

Ronald

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu vim Edit question
Assignee:
No assignee Edit question
Last query:
2019-12-08
Last reply:
2019-12-16

This question was reopened

Manfred Hampl (m-hampl) said : #1

For diagnostic purposes, what is the output of the command

uname -a
lsb_release -crid
df -h | grep -v snap

Ronald RiemVis (gentlerv) said : #2

uname -a give:
Linux xxxxxxxx 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -crid give:
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic

df -h | grep -v snap give:
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 394M 908K 393M 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 3.9G 3.0G 736M 81% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
/dev/sda2 976M 145M 765M 16% /boot
tmpfs 394M 0 394M 0% /run/user/1000

sorry for late reply,

Ronald

Manfred Hampl (m-hampl) said : #3

The relevant part of your output:

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-ubuntu--lv 3.9G 3.0G 736M 81% /
/dev/sda2 976M 145M 765M 16% /boot

You root file system is using volume group functionality.

For further diagnostics, what is the output of the commands

sudo fdisk -l
sudo vgscan -v

Ronald RiemVis (gentlerv) said : #4

Hello manfred,

When doing the install from this server I used the standard setup option 2, logical volumes

Sudo fdisk -l :
Disk /dev/mapper/ubuntu--vg-ubuntu--lv: 4 GiB, 4294967296 bytes, 8388608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

sudo vgscan -v
    Wiping cache of LVM-capable devices
    Wiping internal VG cache
  Reading volume groups from cache.
  Found volume group "ubuntu-vg" using metadata type lvm2

Greetings,

Ronald

Manfred Hampl (m-hampl) said : #5

Based on your output I assume that you have allocated only 4 GB space when installing.

Volume groups should allow extending the space, please check the documentation and/or man pages.

Ronald RiemVis (gentlerv) said : #6

I started the install after making a disc of 27 Gbyte.
I could not send a picture in Ubuntu-One messaging service but added now a
picture from Webmin
Please see it and let me know why the logical volume inside the VM from
windows server does not become larger

On Thu, 5 Dec 2019 at 15:54, Manfred Hampl <
<email address hidden>> wrote:

> Your question #686437 on vim in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/vim/+question/686437
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> Based on your output I assume that you have allocated only 4 GB space
> when installing.
>
> Volume groups should allow extending the space, please check the
> documentation and/or man pages.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu/+source/vim/+question/686437/+confirm?answer_id=4
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+source/vim/+question/686437
>
> You received this question notification because you asked the question.
>

Ronald RiemVis (gentlerv) said : #7

Ok I solved the problem,
Even though during the installation the total disc space is not used I
could extend within Webmin the disc size when using the command Use all VG
space.
Now I have 21.3 Gbyte total
I still wonder why windows VM does not extend the logical disc size or must
I use the Use all VG space everytime ?

On Thu, 5 Dec 2019 at 15:54, Manfred Hampl <
<email address hidden>> wrote:

> Your question #686437 on vim in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/vim/+question/686437
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> Based on your output I assume that you have allocated only 4 GB space
> when installing.
>
> Volume groups should allow extending the space, please check the
> documentation and/or man pages.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/ubuntu/+source/vim/+question/686437/+confirm?answer_id=4
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+source/vim/+question/686437
>
> You received this question notification because you asked the question.
>

Manfred Hampl (m-hampl) said : #8

Using volume groups in a virtual machine is a quite complex situation.
You have the virtual disk (*.vdi) file which provides a storage container to the guest system, and you then have a volume group container for the Ubuntu disks inside the VM container. And you then allocate a logical disk for Ubuntu in the volume group container. Maybe in one of these steps you didn't pick the optimal selection.

If it is now working well, then I suggest that you close that question.
I do not see any benefit in spending more time on that problem.

Can you help with this problem?

Provide an answer of your own, or ask Ronald RiemVis for more information if necessary.

To post a message you must log in.