OPNsense Forum

English Forums => General Discussion => Topic started by: M@rch0n on February 26, 2019, 03:31:25 PM

Title: [SOLVED] Wrong disk space
Post by: M@rch0n on February 26, 2019, 03:31:25 PM
Hello,

I have a recent Opensense 19.1.1 with basic settings and the following problem is occurring and I do not even know where to start verifying.

Since last Thursday I noticed a high consumption of disk by GUI interface (98%). I veirifiquei through cli (ssh) and with the df command also reported the same 98% usage.

Checking each directory and file, all added up to just over 3GB. I did this check with "# du-sh" on / and I have no other mount point.

I ran fsck, and no error is encountered.
When rebooting the system normalizes, but a few days later the information comes back and when it reaches 100% use, many services stop working complaining about lack of space and disk.

I was looking for a file to file and everything inside it came to a little more than 3GB.

# df -h
Filesystem         Size    Used   Avail Capacity  Mounted on
/dev/gpt/rootfs     49G    44G     5G     90%    /
devfs              1.0K    1.0K      0B   100%    /dev
devfs              1.0K    1.0K      0B   100%    /var/unbound/dev
devfs              1.0K    1.0K      0B   100%    /var/dhcpd/dev

# pwd
/
root@opnsense:/ # du -sh
3.6G    .

Thanks for all
Title: Re: Wrong disk space
Post by: franco on February 26, 2019, 11:23:29 PM
Hi there,

This is pretty odd.

> Since last Thursday I noticed a high consumption of disk by GUI interface (98%)

Not sure what this means. Do you use web proxy or intrusion detection or a captive portal?


Cheers,
Franco
Title: Re: Wrong disk space
Post by: M@rch0n on February 27, 2019, 04:39:49 PM
Hello Franco,

I found this question on github;

https://github.com/opnsense/core/issues/3241

And I applied the correction indicates;

# opnsense-patch 5123277

Disk space problem has been fixed.

Answering your question, I only use web proxy and captive portal.

SOLVED by patch 5123277

Thanks
Title: Re: Wrong disk space
Post by: franco on February 28, 2019, 09:06:55 PM
Oh, ok, that is also fixed in 19.1.2 which came out today.


Cheers,
Franco