Greetings, everything is working fine because your firewall is not running out of space as it might seem, there are some files that are meant to be that way ( at a 100%) Please check below
In a Unix-style OS, processes access devices via /dev directory. Within this directory there are device nodes allocated as block or character devices, each with a major and minor number corresponding to its device driver and its device instance. (Eg. da0 and da0s1a)
For a new device such as a USB drive to be supported by kernel, there has to be a node in /dev corresponding to it so that processes are able to access it.
The virtual filesystemdevfs, created by the kernel, keeps track of the device drivers currently registered while also automatically creating and removing the corresponding device nodes in/dev. The kernel will dynamically resize it so that it will always be as large as required for the device nodes, sodfwill show it as always being very small and 100% full.This is normal and harmless.
The/procfile system (procfs) is a real-time API to the kernel. It is a virtual file system: it is not associated with a block device but exists only in memory. The files in theprocfsare there to allow user programs not only access certain information from the kernel, but also for debug purposes.
Each process has its own directory under/procwith the process id as the name. In this directory we can find all kinds of information the kernel has for the particular process.
Since this /procfswill be made dynamically depending upon the process running and populate it with corresponding PID, it is as large as required at that moment and hence 100% utilized,which is normal and harmless.
In fact,psuses the proc file system to obtain its information. We can get a more detailed view of the process by reading the file/proc/PID/status. Here is a snapshot of one such process: