ESET Virtual Appliance Disk Space Root?

[Guest]

Hello,

 

We have the ESET Virtual Appliance running on Hyper-V https://help.eset.com/esmc_deploy_va/70/en-US/donwload_a_virtual_appliance.html?deployent_on_hyperv.html  . It's reporting that the file system mounted at / has no free space on the webmin page, the VHD is a dynamically expanding disk  Is there a way to expand the root folder, I presume that's the one it means.

 

ESET PROTECT (Server), Version 8.0 (8.0.2225.0)
ESET PROTECT (Web Console), Version 8.0 (8.0.191.0)
Copyright (c) 1992-2021 ESET, spol. s r.o. All Rights Reserved.
End-user license agreement
CentOS (64-bit), Version 7.9.2009

 

System hostname    **********(192.*.*.*)    Operating system    CentOS Linux 7.9.2009
Webmin version    1.973     Authentic theme version    19.73 
Time on system    Friday, April 30, 2021 9:06 AM    Kernel and CPU    Linux 3.10.0-1160.24.1.el7.x86_64 on x86_64
Processor information    Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz, 1 cores    System uptime    2 minutes
Running processes    153    CPU load averages    2.38 (1 min) 3.21 (5 mins) 1.50 (15 mins)
Real memory    1.96 GiB used / 1.15 GiB cached / 4.66 GiB total    Virtual memory    0 bytes used / 3.87 GiB total
Local disk space    40.21 GiB used / 19.8 GiB free / 60.02 GiB total    Package updates    29 package updates are available
 Warning!
Warning! The 40 GiB filesystem mounted at / has only 137.68 MiB of free disk space

Edited April 30, 2021 by robg
VHS to VHD

[Guest]

This is the display output

 

[karlisi 27]

I think, the main question should be, what is in your root partition. I have about 900 endpoints and only 9GB used in root.

[Guest]

1 minute ago, karlisi said:

I think, the main question should be, what is in your root partition. I have about 900 endpoints and only 9GB used in root.

Couldn't tell really, searches for large files seemed to halt and never complete. In the end I fond a guide and resized it for now. Tried running the HTTP cache clean-up but didn't make any difference for me

 

Found a guide here https://turbofuture.com/computers/resizelinuxfilesystem  had to use xfs_growfs instead of  resize2fs 

fdisk -l
fdisk /dev/sda
n
p
3

w

shutdown - r now
fdisk -l
df -h
We want to increase the size of /dev/mapper/vg_redhat-lv_root.
pvcreate /dev/sda3
vgdisplay 
vgextend vg_redhat /dev/sda3 
vgdisplay 

 lvextend -l +12789 /dev/mapper/vg_redhat-lv_root 

resize2fs /dev/mapper/vg_redhat-lv_root (or xfs_growfs)

df -h  

[Guest]

If the http proxy is enabled I would check the size of the cache folder and eventually empty it.

Edited May 1, 2021 by kermit80

[Guest]

Thanks

Have turned it off, not sure it was on previously but cleared the cache. Disk size has stayed constant since then at about 40GB

 

40.9 GiB used / 69.14 GiB free / 110.04 GiB total