Vhdx partition size

LukasQ · November 2, 2019, 11:25am

Hello all

Sorry for the stupid questions, I always forget the thing with linux disc layouts.
When I list the filesystems, it returns:

When I list the block devices, I get:

As far as I understand, sda8 is only using 5.3GB of the whole 20GB vhdx image. This seems to be the reason HA displays in the system monitor 80% disk utilisation.

Why do I see 100% on /dev/root?
Can I simply run resize2fs to extend sda8, or will this crash the other partitions?
And if so, why is sda8 not using the whole space in the vhdx image by default?

Cheers, Lukas

sota · November 2, 2019, 2:05pm

Hi Lukas,

Did you follow the procedure here? https://community.home-assistant.io/t/hass-io-on-hyper-v-step-by-step/140553

LukasQ · November 2, 2019, 2:18pm

Indeed, I did.
But when I update to a newer version, my disk gets full. See:

and the update fails:
19-11-02 14:34:59 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!

Plus, as far as I know, one wouldn’t use the opt nobarrier, see: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/storage_administration_guide/writebarrieronoff

LukasQ · November 4, 2019, 5:04pm

So, default behaviour is, sda8 would increase automatically, right?
Anyways, manual work did the trick.

gist.github.com

https://gist.github.com/larsks/3933980

gistfile1.md

Occasionally we will deploy a virtual instance into our KVM
infrastructure and realize after the fact that we need more local disk
space available.  This is the process we use to expand the disk image.
This process assumes the following:

- You're using legacy disk partitions.  The process for LVM is similar
  and I will describe that in another post.
- The partition you need to resize is the last partition on the disk.

This process will work with either a `qcow2` or `raw` disk image.  For

This file has been truncated. show original