Results 1 to 5 of 5

Thread: Low disk space on "filesystem root" problem

  1. #1
    Join Date
    Feb 2014
    Location
    Yes
    Beans
    298
    Distro
    Ubuntu 18.04 Bionic Beaver

    Low disk space on "filesystem root" problem

    Low disk space on "filesystem root"
    The volume filesystem root has only 0 bytes disk space remaining.

    Out of nowhere, I've started getting messages about disk space problems.
    This 18.04 install has been working fine, this recent message showed up while running Grsync backup.
    The disk is a samsung ssd 500g, which is normally 45 pct filled, right now Disks show it 100 pct filled. SDA1 os is 31 gbs.

    How do I fix this?
    Last edited by ra7411; January 25th, 2021 at 03:41 PM.

  2. #2
    Join Date
    Feb 2014
    Location
    Yes
    Beans
    298
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Low disk space on "filesystem root" problem

    Here's terminal output of df -h and df -hi / , if that helps.
    Attached Images Attached Images

  3. #3
    Join Date
    Aug 2011
    Location
    52.5° N 6.4° E
    Beans
    6,824
    Distro
    Xubuntu 22.04 Jammy Jellyfish

    Re: Low disk space on "filesystem root" problem

    Try to find the files taking all that space. As this happend while running backups, make sure the backup partition was actually mounted. If it wasn't, the files have been copied to some place on your root file system. I'd first look in the directory that you use as mountpoint for your backup drive.

  4. #4
    Join Date
    Apr 2008
    Location
    Southern California, USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Low disk space on "filesystem root" problem

    Find out where your large usage is:
    Code:
    sudo find / -type f -exec du -h {} + | sort -hr | head -20

  5. #5
    Join Date
    Feb 2014
    Location
    Yes
    Beans
    298
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Low disk space on "filesystem root" problem

    Quote Originally Posted by Impavidus View Post
    Try to find the files taking all that space. As this happend while running backups, make sure the backup partition was actually mounted. If it wasn't, the files have been copied to some place on your root file system. I'd first look in the directory that you use as mountpoint for your backup drive.

    I think you got it, the Grsync destination was unmounted. Very weird, I've been doing this backup daily for several years with no problems like this, I would have guessed Grsync had a way of making sure the destination was mounted or it would abort.

    So far that looks like the fix for the problem. I'll wait a couple days before going "solved" on this.

    Thanks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •