DerGraf wrote: ↑
Mon Sep 10, 2018 5:52 pm
... I think 5% of 100G is a little bit to much for journaling, etc as jwarfin mean.
Yeah, sorry about that. But I finally remembered what this storage issue is really about...
When you format a Unix/Linux partition, a number of reserved blocks are allocated during formatting. The default amount of reserved blocks for ext2/3/4 is 5% (you can use tune2fs to change the %). This "reserved blocks" idea has been a feature of Unix/Linux releases just about forever. In essence, it is implemented so superuser can recover a system with a completely full root filesystem. But, "full" actually means when the partition hits 95% full - the extra hidden 5% gives some extra space for superuser to run commands to recover the system. This is all well and good for a root file system, but it can be a pain for other types of partitions. Heck, a default 5% reserved block allocation for a 1tb non-root partition wastes a lot of space. This is why sysadmins may choose to use tune2fs to reduce the reserved blocks for a partition.
Needless to say, the reserved blocks can lead to confusion because common user commands - like df - don't directly take the reserved blocks into account. However, tune2fs has an option that lets you see what the reserved block/count is for a partition.
The php function(s) that get disk capacity apparently include the reserved blocks in the usage calculation somehow. Kind of unfortunate.
Google "linux partition reserved blocks" for more details.
For example: https://odzangba.wordpress.com/2010/02/ ... artitions/