Op 04-09-2023 om 17:13 schreef Granwille Strauss:
Hi
Thank you, in our case, we start our VMs at 60 GB, clients then can
upgrade to 120 GB as the next upgrade. However, clients also have the
option to "Downgrade" back to 60 GB based on their package. Would kinda
not make sense to prohibit
Hi
Thank you, in our case, we start our VMs at 60 GB, clients then can
upgrade to 120 GB as the next upgrade. However, clients also have the
option to "Downgrade" back to 60 GB based on their package. Would kinda
not make sense to prohibit clients from doing that, from a legal POV. So
this ki
Hi,
Normally cloud providers create vm templates with small size (e.g. 10GB).
When create vm from the template, user can override the root disk size so
that vm have a larger size (e.g. 60GB)
If the vm template has cloud-init installed, it can detect the new disk
size and auto-grow the partition to
I believe most do not allow shrinkage, simples. :)
At least the likes of Digitalocean and Hetzner do not.
Instead how you could juggle storage flexibly is by adding or removing
data volumes and within the VM use them with LVM.
HTH
On 2023-09-04 15:50, Granwille Strauss wrote:
Hi Wido
Thank
Hi Wido
Thank you. Yes, I only shrink it inside the VM. But still Cloudstack
volume shows 120GB and within the VM lsblk command shows that 120 GB is
available. Since I cannot shrink the volume, how do most providers take
care of this issue? I mean it would be awkward if a client see they can
Op 04-09-2023 om 13:08 schreef Granwille Strauss:
Hi Wido
I mounted a live ISO to the VM, booted into the ISO and went into
recover mode, had to unmount the / partition of the VM, and then proceed
to resize it via parted and write changes. Rebooted via and detatched
the ISO and now VM show
Hi Wei
As far as I understand, you have resized the disk inside the VM to 60GB,
right ?
- Yes, I have resized the partitions in VM back to 60 GB.
However, the allocated disk size of the VM should be still 120GB, not 60GB.
You can verify it by `qemu-img info -U /mnt//`
- Yes, in VM if
Hi,
As far as I understand, you have resized the disk inside the VM to 60GB,
right ?
However, the allocated disk size of the VM should be still 120GB, not 60GB.
You can verify it by `qemu-img info -U /mnt//`
Shrinking a QCOW2 image is possible, but complicated. It is currently not
suppor
Hi Wido
I mounted a live ISO to the VM, booted into the ISO and went into
recover mode, had to unmount the / partition of the VM, and then proceed
to resize it via parted and write changes. Rebooted via and detatched
the ISO and now VM shows 60 GB correctly. However, in Cloudstack, still
says
Op 04/09/2023 om 09:18 schreef Granwille Strauss:
Thank you. Can you confirm if this behaviour is expected? Or am I
experiencing a bug?
What exactly? You did this resize manually outside the knowledge of
cloudstack, am I correct?
How did you do this live/recovery method?
Wido
On 9/4/2
Thank you. Can you confirm if this behaviour is expected? Or am I
experiencing a bug?
On 9/4/23 09:00, Wido den Hollander wrote:
Op 04-09-2023 om 08:20 schreef Granwille Strauss:
Hi
I managed to resize the VM itself back to 60 GB via live/recovery
method. However, now in Cloudstack it stil
Op 04-09-2023 om 08:20 schreef Granwille Strauss:
Hi
I managed to resize the VM itself back to 60 GB via live/recovery
method. However, now in Cloudstack it still says the volume remains 120
GB and when I want to shrink it I am presented with the errors from my
previous reply. Is there a
Hi
I managed to resize the VM itself back to 60 GB via live/recovery
method. However, now in Cloudstack it still says the volume remains 120
GB and when I want to shrink it I am presented with the errors from my
previous reply. Is there a way around this? Such as making a database
change. Al
Hi Wei
It seems you're right you cannot shrink the volume in Cloudstack:
Failed to resize volume operation of volume UUID:
[eec8285e-8715-441b-b418-b71b231f1bab] due to - Unable to shrink
volumes of type QCOW2
Going from existing size of 128849018880 to size of 64424509440 would
shrink the
Hi Wido,
Does it work with kvm ?
my suggestion would be
- create a new vm with 60GB
- copy the data using `rsync`
-Wei
On Sat, 2 Sept 2023 at 08:25, Wido den Hollander wrote:
> Hi,
>
> Yes, you should make sure the filesystem and partitions are within the
> to be set new boundaries.
>
> Once
Thank you Wido
I appreciate your feedback.
On 9/2/23 08:24, Wido den Hollander wrote:
Hi,
Yes, you should make sure the filesystem and partitions are within the
to be set new boundaries.
Once that's done you can shrink the volume.
I would recommend:
- Shrink EXT4 + Partitions to 59GB
- Sh
Hi,
Yes, you should make sure the filesystem and partitions are within the
to be set new boundaries.
Once that's done you can shrink the volume.
I would recommend:
- Shrink EXT4 + Partitions to 59GB
- Shrink volume to 60GB
- Grow EXT4 + Partitions to 60GB
The step to 59GB is to prevent that
Hi Guys
Anyone willing to assist me with a quick one. What's the best and
recommended way to shrink a VM volume via UI? The VM volume was first 60
GB, we then expended it to 120 GB and increased it in the VM via parted.
I now want to take it back to 60GB. How do I proceed? Do I first shrink
18 matches
Mail list logo
