Why is actual filesystem space used greater than what Squid thinks?
If you compare df output and cachemgr storedir output, you will notice that actual disk usage is greater than what Squid reports. This may be due to a number of reasons: • Squid doesn’t keep track of the size of the swap.state file, which normally resides on each cache_dir. • Directory entries and take up filesystem space. • Other applications might be using the same disk partition. • Your filesystem block size might be larger than what Squid thinks. When calculating total disk usage, Squid rounds file sizes up to a whole number of 1024 byte blocks. If your filesystem uses larger blocks, then some “wasted” space is not accounted.
If you compare df output and cachemgr storedir output, you will notice that actual disk usage is greater than what Squid reports. This may be due to a number of reasons: • Squid doesn’t keep track of the size of the swap.state file, which normally resides on each cache_dir. • Directory entries and take up filesystem space. • Other applications might be using the same disk partition. • Your filesystem block size might be larger than what Squid thinks. When calculating total disk usage, Squid rounds file sizes up to a whole number of 1024 byte blocks. If your filesystem uses larger blocks, then some “wasted” space is not accounted. • Your cache has suffered some minor corruption and some objects have gotten lost without being removed from the swap.state file. Over time, Squid will detect this and automatically fix it.
