This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.

after disk resize df shows the same size

2 posts / 0 new

Topic locked

Last post

#1 Sat, 12/16/2017 - 12:08

tabado

after disk resize df shows the same size

Hello,

My system: Cloudmin 9.3 kvm Hosted systems with LV disks

I made a disk resize for one of the hosted systems from 512GB to 1Terra. After the process the hosted system still have space problems with the hard disk and the fd command shows the same size (512 GB). The cloudmin shows 1024GB and the fdisk inside the hosted system see 1024GB.

LVM info on the host system:

Physical volumes allocated: sda2 225 GB sda2 275 GB sda2 524 GB

(I already made this process a while ago, I have added 275GB to the original 225GB without problem and the result was visible immediately in the hosted system without need of partitionating of the new space)

Output of fdisk on the hosted system:

Disk /dev/vda: 1099.5 GB, 1099511627776 bytes, 2147483648 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: 0x000a90d9

   Device Boot      Start         End      Blocks   Id  System
/dev/vda1            2048  2147481599  1073739776   83  Linux

The vda1 is 512GB if I calculate right... Now if I try to add a new partition, then I get the following messages:

First sector (2147481600-2147483647, default 2147481600):
Using default value 2147481600
Last sector, +sectors or +size{K,M,G} (2147481600-2147483647, default 2147483647): +100G
Value out of range.
Last sector, +sectors or +size{K,M,G} (2147481600-2147483647, default 2147483647):
Using default value 2147483647
Partition 2 of type Linux and of size 1 MiB is set

I have tried to add 100GB without success and after then I have accepted the default value. The result: 1MB. I can't create a bigger partition.

I'm stuck with this, any idea is welcome.
Thank you

#2 Tue, 12/19/2017 - 09:10

scotwnw

check to be sure the LVM volume group has space.
How can all 3 of those physical volumes be named sda2? Cant have 3 disks or partitions on the same cloudmin server with the same name.

Steps to resize for virtual machine in cloudmin. Be sure the volume group has enough space. If not, add a physical disk to the volume group. Then a cloudmin 'resize disk' will use what ever space is available in the volume group. I've never had issue growing the logical volume as long as the volume group has space available. Cloudmin resizes the disk and then the virtual machine automatically sees the new size on next boot. Nothing has to be done inside the virtual machine itself.

Topic locked