After restarting, the original/partition usage rate was 2%, and only 30G was used under/www. However, after restarting,

[WMS]

Hello, I have recently encountered some issues while using Centos7.6,

System environment: CentOS Linux release 7.6.1810 (Core)/ 915G swap 16G boot 1G


Problem: After restarting, the original/partition usage rate was 2%, and only 30G was used under/www. However, after restarting, the/usage rate became 100%, and no large files were found during the search


My friend also encountered this problem and finally reinstalled the system. May I ask what the problem is and how can I solve it? Looking forward to your reply, thank you.

[tunk]

Don't know what your problem is, but 7.6 is wildly out of date. Run yum update.
(Wouldn't know, but since you're out of date, you could possibly have been hacked.)

[TrevorH]

As said, 7.6 is 5 *years* out of date and missing some really important security updates. You need to `yum update` it to get current and then reboot for it to take full effect. You should also get into the habit of running yum update on a regular basis - like once a week - to check what new patches are available.

For the actual problem, please run the following

du -m -x -d 1 /

or du -m -x -d 1 / | sort -n to see that in sorted order with the largest component at the bottom.

That will list out all the top level directories in / and show their usage in MB. Find the one that has all the space and then repeat that command again, changing / to /whatever-was-the-largest in the first output. Keep repeating that process until you reach the bottom directory that contains all your space.

[WMS]

May I ask if there are any other reasons? I have executed 'yum update' without any changes, including du, sometimes entering emergency mode using xfs_ After repairing, restarting will return to normal. Now I am using xfs_ Repair and restart did not free up space,/ partition is still 100%。(my hard drive is very healthy)

[BShT]

look at log files

[tunk]

What's the output of "ls -l /"?
Compare it to the output from "du -m -x -d 1 /" and
see if there's any directories du didn't list. When
du "hangs" like that, it's because it goes through
a big directory.

[TrevorH]

And if you Ctrl-C like that you never get to see the problematic directories. It has 1TB of files to search so you need to be patient.

[WMS]

After waiting for a long time, these have emerged

[TrevorH]

If it's not a USB attached disk then those don't have anything to do with it.