Disk usage on my HyperV is full.
SFV6C8_HV01_SFOS 19.0.0 EAP2-Build271# df -h Filesystem Size Used Available Use% Mounted on none 640.1M 2.0M 591.4M 0% / none 1.9G 16.0K 1.9G 0% /dev none 1.9G 20.2M 1.9G 1% /tmp none 1.9G 14.7M 1.9G 1% /dev/shm /dev/boot 127.7M 26.9M 98.0M 22% /boot /dev/mapper/mountconf 560.3M 88.0M 468.4M 16% /conf /dev/content 11.8G 620.4M 11.2G 5% /content /dev/var 3.7G 3.2G 495.6M 87% /var
Looks like reporting disk is only 3.7GB, how to resize it to get more space?That problem never exist on my 18.0 or 18.5 HyperV.I used the HyperV v19EAP2 image for install.
rm /var/tslog/ *.log.0 was my quick and dirty solution to get some more space, but can not be a solution!
Problem still exist in GA release fresh installer: VI-19.0.0_GA.HYV-317.zip
How to increase safely /dev/var ???
Why is there no partition table on that /dev/hdb ?That should be the SFOS19HV_AUXILIARY-DISK.vhd
SFV6C8_HV01_SFOS 19.0.0 EAP2-Build271# sudo fdisk -l Disk /dev/hdb: 80 GB, 85900124160 bytes, 167773680 sectors 10443 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/hdb doesn't contain a valid partition table Disk /dev/sda: 16 GB, 17180319744 bytes, 33555312 sectors 2088 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sda1 1023,254,63 1023,254,63 33144832 33423359 278528 136M 83 Linux /dev/sda2 1023,254,63 1023,254,63 33423360 33554431 131072 64.0M 83 Linux
Looks like same on my v18.5, never realised that. But /dev/var is using much more space on that 80gb vhd.
You could increase the Aux Partition in Hyper-V but you should not alter the partition size on the disk itself.
__________________________________________________________________________________________________________________
Default the Aux Part is set to 80GB dynamic. So it should be usable directly.
I have the same problem.
Did you make a fresh install, or upgrade your 18.5 to 19.0GA?
I did a fresh install.
This issue has been reported to our Development team and has been assigned ID NC-94291. We will update this thread as we know more.
Best,
The fix for this issue is set to be released on v19 MR-1