-
I created an azure vm using a cyberpanel azure market package.
-
At initialization i used an image with a 30GB disk- i’m not a fan of app + OS on the same disk so i added a data disk however that wasn’t used at all.
-
recently i noticed that my cyberpanel dashboard had my available disk at +20% and i haven’t deployed fully yet, hence i wanted to add space.
-
Had a chat here and the idea of mounting new drive under /home was raised - i have done that, it doesn’t affect my dashboard numbers.
-
Today i resorted to extending the os drive- thats done, it bleated about partition tables sorted per fdisk.
shortened fdisk -l result
Disk /dev/sdb: 16 GiB, 17179869184 bytes, 33554432 sectors
Disk model: Virtual Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xb873880d
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 33552383 33550336 16G 7 HPFS/NTFS/exFAT
Disk /dev/sda: 128 GiB, 137438953472 bytes, 268435456 sectors
Disk model: Virtual Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x64986289
Disk /dev/sdc: 128 GiB, 137438953472 bytes, 268435456 sectors
Disk model: Virtual Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 0BF5CEA1-33AC-426E-AD8B-9F211198DEC8
Device Start End Sectors Size Type
/dev/sdc1 2048 10239 8192 4M BIOS boot
/dev/sdc2 10240 227327 217088 106M EFI System
/dev/sdc3 227328 62916574 62689247 29.9G Linux filesystem
Disk /dev/loop8: 49.85 MiB, 52248576 bytes, 102048 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
here is the output for df -Th
Filesystem Type Size Used Avail Use% Mounted on
/dev/root ext4 29G 24G 5.7G 81% /
devtmpfs devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs tmpfs 3.9G 136K 3.9G 1% /dev/shm
tmpfs tmpfs 796M 1.2M 795M 1% /run
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sda ext4 125G 12G 107G 10% /home
/dev/loop0 squashfs 56M 56M 0 100% /snap/core18/2667
/dev/loop1 squashfs 56M 56M 0 100% /snap/core18/2679
/dev/loop2 squashfs 64M 64M 0 100% /snap/core20/1778
/dev/loop3 squashfs 64M 64M 0 100% /snap/core20/1822
/dev/loop6 squashfs 50M 50M 0 100% /snap/snapd/17883
/dev/loop5 squashfs 92M 92M 0 100% /snap/lxd/24061
/dev/loop4 squashfs 92M 92M 0 100% /snap/lxd/23991
/dev/loop8 squashfs 50M 50M 0 100% /snap/snapd/17950
/dev/loop7 ext4 1.5G 356K 1.4G 1% /tmp
/dev/sdc15 vfat 105M 5.2M 100M 5% /boot/efi
tmpfs tmpfs 796M 0 796M 0% /run/user/5002
questions:
-
the dashboard limits refers specifically to “/” . Is that a true reflection of space available per Cyberpanel? . i.e. if that space maxes will my sites affected?
-
If i try to extend /dev/sdc3 above, would that be a solution?
-
In truth i’d be happy to start again and migrate as space is a dealbreaker but i’m not certain i’ll have a better outcome, I expect this is a common issue - how do others avoid having space issues when running file heavy sites?