Differences

This shows you the differences between two versions of the page.

--- engineering:computer_science:linux:linux_troubleshooting:linux_no_space_left_on_device [2024/08/16 13:56] – removed - external edit (Unknown date) 127.0.0.1
+++ engineering:computer_science:linux:linux_troubleshooting:linux_no_space_left_on_device [2024/08/16 13:56] (current) – ↷ Page moved from refractor_computer_science:linux:linux_troubleshooting:linux_no_space_left_on_device to engineering:computer_science:linux:linux_troubleshooting:linux_no_space_left_on_device carlossousa
@@ Line 1: / Line 1: @@
+====== Linux - No Space left on device ======
+[TODO] A detailed troubleshooting should be made instead of bulletpoints.
+|Check if the device itself has free space|<code bash>
+df-h
+</code>     |
+|If you need to clear logs a simple redirect would be enough|<code bash>> file.log
+</code>|
+|If the issue still remains probably your inodes are full. You can check it with:|<code bash>
+df -i
+</code>     |
+|If that is the issue you can check where the issues lies with:|<code bash>
+for i in /*; do echo $i; find $i |wc -l; done
+</code>     |
+|You can go deeper then with:|<code bash>
+for i in /var/*; do echo $i; find $i |wc -l; done
+</code>     |
+|In my case the issue was by /var/spool/postfix/maildrop. A "rm -fv" doesn't work, since there are too many files in that directory. Therefore, you can make sure a loop will delete the files you actually want with:|<code bash>
+for f in *; do echo rm "$f"; done
+</code>     |
+|and if you are happy with the result, commit to it:|<code bash>
+for f in *; do rm "$f"; done
+</code>     |
+\\