Suspicious:
The total partition capacity is 7.2 TB. After the partition is mounted, only TB of space can be used. Where is the GB space?
Exploration:
1. Is the disk space not released after the file is deleted?
Run the lsof | grep DELETE command to check whether there is any file handle in the deleted State occupied by the process.
2. Is the file system damaged?
After umount is partitioned, fsck. ext3 is partitioned. After mounting, only TB of space is available.
3. Is the hardware broken?
Let's put the hardware status first. What else will cause this problem?
Who eats my disk space?
Under the consistent exploration of several partners, who will eventually be really fierce?
Conclusion:
Originally, ext File System reserves 5% disk space by default for root users to maintain the system or record key system logs.
Mkfs. ext3 man page:
-M reserved-blocks-Percentage
Specify the percentage of the filesystem blocks reserved for
Super-user. This avoids fragmentation, and allows root-owned
Daemons, such as syslogd (8), to continue to function correctly
After non-privileged processes are prevented from writing to
Filesystem. The default percentage is 5%.
Is it too difficult to reserve such a large space as a hard disk? Can you reduce the reserved space or remove the reserved space?
That's of course. We can use tune2fs to change the default setting of 5%, for example, reserve only 1% of the space. It can be set to 0%, but is not recommended.
Tune2fs-M 1/dev/SDB
Tune2fs 1.41.12 (17-may-2010)
Setting reserved blocks percentage to 1% (19529728 blocks)
A lot of available space is released at once.
Generally, the total disk space is not large, and the reserved space is about 5% GB, which is not obvious.
This article from the "O & M said: From the rookie to the old bird" blog, please be sure to keep this source http://liuqunying.blog.51cto.com/3984207/1568966
Exploring: who has eaten the available disk space?