How to Fix the Linux No Space Left on Device Error

If you’re encountering the “No space left on device” error on your Linux system, it can halt your work and cause system instability. This guide provides clear, step-by-step instructions to identify and free up disk space, helping your system run smoothly again. Before you begin, ensure you have root or sudo privileges, as many commands require administrative access. It’s also wise to back up important data before making significant changes to disk partitions or cleaning system files.

What You’ll Need

• Access to your Linux terminal or command line interface
• Root or sudo privileges
• Basic understanding of Linux commands
• Sufficient patience to follow each step carefully

Step-by-Step

1. Check Available Disk Space
   Open your terminal and run:

   df -h

   This command displays disk space usage for all mounted partitions in a human-readable format. Look for partitions with 100% usage, especially root (/), /home, or other critical directories.

2. Identify Large Files and Directories
   To find what’s consuming the most space, use:

   du -sh /* 2>/dev/null | sort -h

   or for more detailed analysis:

   du -ah / | sort -rh | head -n 20

   These commands help locate large files and directories that may be causing the space issue.

3. Clear Package Cache
   Package managers often store cached files. Clear them to free space:
   – For apt (Debian/Ubuntu):

   sudo apt-get clean

   – For yum (CentOS/RHEL):

   sudo yum clean all

   – For dnf (Fedora):

   sudo dnf clean all

4. Remove Unused Packages and Dependencies
   – For apt:

   sudo apt-get autoremove

   – For yum/dnf:

   sudo yum autoremove

5. Delete Old Log Files and Temporary Files
   Clean up log files and temp directories:

   sudo journalctl --vacuum-time=7d

   (removes logs older than 7 days)
   Also, check /tmp and /var/tmp for unnecessary files:

   sudo rm -rf /tmp/* /var/tmp/*

6. Identify and Remove Large, Unnecessary Files
   Manually delete large files that are no longer needed, such as old backups, ISO images, or media files.
   Use

   rm

   cautiously to delete files, ensuring you do not remove essential system files.

7. Consider Moving Files to External Storage or Different Partitions
   If certain large files are important but not needed immediately, move them to external drives or different partitions with more space.
   Use

   mv /path/to/large/file /new/location/

   to relocate files safely.

8. Resize Partitions or Add Storage (Advanced)
   If disk space is critically low and cleaning isn’t enough, consider resizing existing partitions or adding new storage devices. This step requires careful planning and backups. Use tools like GParted or command-line utilities with caution.
9. Verify Free Space
   After cleaning, run

   df -h

   again to confirm that free space has increased and the error is resolved.

Common Mistakes

• Deleting system files or directories essential for operation, causing system instability or boot issues.
• Removing files without verifying their importance, leading to data loss.
• Cleaning cache or logs without understanding their purpose, which might affect troubleshooting or system functions.
• Ignoring mounted filesystems or external drives, missing opportunities to free space elsewhere.
• Resizing partitions without proper backups, risking data corruption or loss.

Tips

• Regularly monitor disk usage to prevent sudden space shortages.
• Set up automated cleanup scripts for logs and cache if possible.
• Use graphical tools like GParted or Disk Usage Analyzer for visual understanding of disk space.
• Keep backups of critical data before performing major cleanup or partition resizing.
• Identify and remove duplicate or outdated files to optimize storage.

Troubleshooting

If you still encounter the “No space left on device” error after following these steps, consider the following:

• Reboot your system: Sometimes, temporary files or caches may not be cleaned up until restart.
• Check for mounted filesystems: Ensure no external or network filesystems are full or disconnected.
• Use disk cleanup tools: Utilities like BleachBit can automate cleanup of cache, logs, and temp files.
• Verify disk health: Use tools like smartctl to check for failing disks which can cause erroneous space reporting.
• Review logs for errors: Look into system logs for underlying issues that may prevent proper cleanup or cause disk consumption spikes.
• Seek expert help: If the problem persists, consult with a system administrator or Linux expert, especially before resizing partitions or making major changes.

Frequently Asked Questions

1. How do I find large files consuming disk space?

Use the du -ah / | sort -rh | head -n 20 command to list the top 20 largest files and directories, helping you identify space hogs.

2. Will deleting log files affect system stability?

Generally not, especially if logs are old or no longer needed. However, avoid deleting logs that are actively used for troubleshooting ongoing issues.

3. How often should I check disk space to prevent issues?

It’s good practice to check weekly or set up automated alerts for critical disk usage thresholds to prevent sudden shortages.

4. Can resizing partitions cause data loss?

Yes, resizing partitions can lead to data loss if not done carefully. Always back up data before attempting partition modifications.

5. Is it safe to delete files from /tmp or /var/tmp?

Most temporary files can be safely deleted, but ensure no processes are actively using files in those directories to avoid disrupting running services.

6. What tools can help me visualize disk usage?

Graphical tools like GParted, Disk Usage Analyzer, or ncdu provide visual representations of disk space, making it easier to identify problem areas.

Related

• How to Fix SMB Printing Issues on macOS Tahoe 26
• Fix SmartScreen Can’t Be Reached Right Now on Windows 10 and 11
• How to Fix Smart TV Not Showing in Cast or Screen Mirroring