computer_science:linux:linux_troubleshooting:linux_no_space_left_on_device

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
computer_science:linux:linux_troubleshooting:linux_no_space_left_on_device [2020/06/30 14:25] carlossousacomputer_science:linux:linux_troubleshooting:linux_no_space_left_on_device [2023/12/01 12:07] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Linux - No Space left on device ======
 +
 [TODO] A detailed troubleshooting should be made instead of bulletpoints. [TODO] A detailed troubleshooting should be made instead of bulletpoints.
  
-  * Check if the device itself has free space+|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 bash level1> +</code>     |
-df -h+
  
-</code>+\\
  
  
  • computer_science/linux/linux_troubleshooting/linux_no_space_left_on_device.1593527157.txt.gz
  • Last modified: 2023/12/01 12:07
  • (external edit)