Post History
If you want to go with command-line tools, the first step might be to run a du -h --max-depth=1 | sort -h -k 1 -r in your root directory. This will give you a list of the sub-directories sorted...
Answer
#3: Post edited
by
AdminBee
·
2024-10-02T08:10:30Z (about 2 months ago)
Mention graphical tool
- If you want to go with command-line tools, the first step might be to run a
- ```
- du -h --max-depth=1 | sort -h -k 1 -r
- ```
- in your root directory. This will give you a list of the sub-directories sorted by gross usage. You may then proceed by applying the same command inside the sub-directory identified as the "heaviest", to ultimately find the files that eat up all your storage space.
Note that for a "complete picture" you may need to do this with `sudo` privileges to access directories that your regular user may not enter. Also keep in mind that there are limitations to the accuracy of disk usage reported by `du`, as explained e.g. [in the Wiki page](https://en.wikipedia.org/wiki/Du_(Unix)).
- If you want to go with command-line tools, the first step might be to run a
- ```
- du -h --max-depth=1 | sort -h -k 1 -r
- ```
- in your root directory. This will give you a list of the sub-directories sorted by gross usage. You may then proceed by applying the same command inside the sub-directory identified as the "heaviest", to ultimately find the files that eat up all your storage space.
- Note that for a "complete picture" you may need to do this with `sudo` privileges to access directories that your regular user may not enter. Also keep in mind that there are limitations to the accuracy of disk usage reported by `du`, as explained e.g. [in the Wiki page](https://en.wikipedia.org/wiki/Du_(Unix)).
- If you want to go for a graphical tool, there is the [`QDirStat`](https://github.com/shundhammer/qdirstat) project which will represent the individual files as tiles (with sizes proportional to their ... size).
#2: Post edited
by
AdminBee
·
2024-10-02T07:58:00Z (about 2 months ago)
Minor rewording
- If you want to go with command-line tools, the first step might be to run a
- ```
- du -h --max-depth=1 | sort -h -k 1 -r
- ```
in your root directory. This will give you a list of the sub-directories sorted by gross usage. You may then proceed by applying the same command to the sub-directory identified as the "heaviest", to ultimately find the files that eat up all your storage space.- Note that for a "complete picture" you may need to do this with `sudo` privileges to access directories that your regular user may not enter. Also keep in mind that there are limitations to the accuracy of disk usage reported by `du`, as explained e.g. [in the Wiki page](https://en.wikipedia.org/wiki/Du_(Unix)).
- If you want to go with command-line tools, the first step might be to run a
- ```
- du -h --max-depth=1 | sort -h -k 1 -r
- ```
- in your root directory. This will give you a list of the sub-directories sorted by gross usage. You may then proceed by applying the same command inside the sub-directory identified as the "heaviest", to ultimately find the files that eat up all your storage space.
- Note that for a "complete picture" you may need to do this with `sudo` privileges to access directories that your regular user may not enter. Also keep in mind that there are limitations to the accuracy of disk usage reported by `du`, as explained e.g. [in the Wiki page](https://en.wikipedia.org/wiki/Du_(Unix)).
#1: Initial revision
by
AdminBee
·
2024-10-02T07:56:40Z (about 2 months ago)
If you want to go with command-line tools, the first step might be to run a ``` du -h --max-depth=1 | sort -h -k 1 -r ``` in your root directory. This will give you a list of the sub-directories sorted by gross usage. You may then proceed by applying the same command to the sub-directory identified as the "heaviest", to ultimately find the files that eat up all your storage space. Note that for a "complete picture" you may need to do this with `sudo` privileges to access directories that your regular user may not enter. Also keep in mind that there are limitations to the accuracy of disk usage reported by `du`, as explained e.g. [in the Wiki page](https://en.wikipedia.org/wiki/Du_(Unix)).