I have encountered this problem a couple of times now, where the used space in df -h does not correlate with actual used space on the disk.
Running 8.1-RELEASE
Here's an example:
Now, try as I might, I cannot find 175G worth of used space on the system. A reboot results in the following:
I suspect that something has a hold of those extra 83G, but I'm not sure how to track down the source, so that a reboot isn't necessary.
Any tips on identifying what could be holding onto the elusive 83G shown in the first df -h? This is a pretty active syslog server, so I could easily use that much space, but killing syslog-ng doesn't seem to resolve the problem.
Running 8.1-RELEASE
Here's an example:
Code:
$ df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/da0s1a 192G 175G 1.4G 99% /
Code:
$ df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/da0s1a 192G 92G 84G 52% /
Any tips on identifying what could be holding onto the elusive 83G shown in the first df -h? This is a pretty active syslog server, so I could easily use that much space, but killing syslog-ng doesn't seem to resolve the problem.