Timeline for Disk full after deleting large files and rebooting
Current License: CC BY-SA 4.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 27, 2022 at 11:13 | history | edited | Kamil Maciorowski | edited tags | |
| Dec 27, 2022 at 11:10 | answer | added | Kamil Maciorowski | timeline score: 1 | |
| Dec 27, 2022 at 10:58 | comment | added | cas | @Mehmet 5% of 441G is around 22G, while 1% is only around 4.5GB, I second frostschutz's suggestion to reduce root's reserve to 1%. BTW, if you haven't already done so, you can probably regain a lot of space by deleting packages downloaded by your package manager. eg. Debian (etc) store downloaded .deb files in /var/cache/apt/archives. You can delete them with apt-get clean. Other distros will differ. Also, /var/cache and /var/log are good places to search for stuff that can be deleted. Also worth considering: switch to btrfs or zfs or some other fs with transparent compression. | |
| Dec 27, 2022 at 10:56 | comment | added | Mehmet | @frostschutz Your suggestion worked. I only reduced it by 1% but that let me log in graphically. Further deletions then started showing as available space in the output of df. If you submit an answer I will accept it. | |
| Dec 27, 2022 at 10:40 | history | edited | Mehmet | CC BY-SA 4.0 | Added third option of using a live cd |
| Dec 27, 2022 at 10:14 | comment | added | Mehmet | @ArtemS.Tashkinov I've been trying to work on your suggestion, but I am struggling as the drive is encrypted. I can decrypt the drive using cryptsetup but even if I don't mount it e2fsck says the volume is in use so can't run. If I don't decrypt it e2fsk doesn't recognise it as ext4. Any suggestions? | |
| S Dec 27, 2022 at 10:09 | history | edited | Mehmet | CC BY-SA 4.0 | Fixed grammatical error, improved readability and clarity |
| S Dec 27, 2022 at 10:09 | history | suggested | geek | CC BY-SA 4.0 | Fixed grammatical error, improved readability and clarity |
| Dec 27, 2022 at 10:07 | comment | added | icarus | Have you got a lot of file/directories in /lost+found? | |
| Dec 27, 2022 at 10:01 | comment | added | Mehmet | @Alex, I didn't realise I had to, but I have now and it's not made any difference. | |
| Dec 27, 2022 at 9:55 | comment | added | Artem S. Tashkinov | @frostschutz he's got 420GB of free space. That's over 95%. | |
| Dec 27, 2022 at 9:49 | review | Suggested edits | |||
| S Dec 27, 2022 at 10:09 | |||||
| Dec 27, 2022 at 9:40 | comment | added | frostschutz | you can disable ext4 root reserve with tune2fs -m 0. alternatively set it to 1% instead of the default 5% to leave a (smaller) reserve for root. in the long term you'll just have to provide more storage space if you're that close to full capacity… that or use ncdu and similar to identify space hogs (log files, caches, ...) | |
| Dec 27, 2022 at 9:40 | comment | added | Alex | Did you reboot in order to have the LVM remounted after trim? | |
| Dec 27, 2022 at 9:34 | comment | added | Mehmet | @Alex I tried fstrim. It reported that it trimmed 20GiB but df still shows 0 available. | |
| Dec 27, 2022 at 9:32 | comment | added | Mehmet | @MC68020 I deleted the files using the command rm in a terminal. They shouldn't be clogging the trash. | |
| Dec 27, 2022 at 9:22 | comment | added | MC68020 | Using KDE ? Hmmm… how did you delete the files ? (moved to trash or actually deleted) | |
| Dec 27, 2022 at 9:04 | comment | added | Alex | might be a long shot but have you tried trimming your disks with fstrim? For example run fstrim -av and see if there will be a difference in size | |
| Dec 27, 2022 at 8:45 | comment | added | Mehmet | I will try a LiveCD in a few minutes. Yes, I'm sure I'm in the right directory. In addition, startx run as a normal user from TTY1 also cannot write to various files in /tmp | |
| Dec 27, 2022 at 8:37 | comment | added | Artem S. Tashkinov | Boot in recovery mode/from LiveCD, e2fsck /dev/device, check again. Lastly, are you sure you're in the right directory? You could be trying to create a file in another directory which e.g. belongs to a full partition/mount point. | |
| S Dec 27, 2022 at 8:32 | review | First questions | |||
| Dec 28, 2022 at 17:03 | |||||
| S Dec 27, 2022 at 8:32 | history | asked | Mehmet | CC BY-SA 4.0 |