/mnt/resource 100% full on Azure VM
-
Installed pfSense on Hyper-V (with WALinuxAgent) and it works perfectly. Uploaded VHD and made AzureVM from custom disk, and although it works perfectly, the "Disks" widget is showing /mnt/resource as over 100% full (3.9GB / 3.9GB).
Using 'sysctl kern.disks' on Hyper-V shows only 1 disk (da0), but on Azure, there is somehow no 2 disks (da1, da0).
Using 'mount' on Hyper-V doesn't show /mnt/resource at all, but on Azure, is shows /mnt/resource to be mounted on da1.
Can anybody explain what's going on here?
-
Partly answered my question - it's the standard temporary disk included with all Azure VMs, and I don't believe pfSense is using it - it just can't assimilate it (maybe the filesystem type).
Is there any way of "ignoring" that device?
-
What level of ignoring are you looking for? As you say pfSense already ignores it, even though it does mount it for some reason. You can just unmount it.
Steve
-
@stephenw10 Thanks for your reply. I've done some more digging since I first posted, and it appears to be a result of the temporary disk assigned to the VM in Azure, and the WALinuxAgent config specifying a Resource disk size of 16GB.
Editing /etc/waagent.conf to reduce that size down to less than the temporary disk does indeed get rid of the red bar, and then I can see a 0 byte file called 'swapfile' on /mnt/resource, but swap usage is still shown in the pfSense dashboard as x% of 409MiB, and when allocating all the RAM, although the % of swap used increases, the swapfile on /mnt/resource is still 0 bytes, so I suspect not being used.
If pfSense utilizes 2 swap files, 1 in RAM and the other on disk, how can I test to make sure the disk swapfile is beiung used?
-
The Netgate Azure image does not have SWAP at all. And in general if pfSense is using SWAP it's probably misconfigured. Performance is dramatically reduced.
If it does have swap though it's a separate disk slice that's formatted as swap. You would see it listed ingeom part listSteve
