Results 1 to 4 of 4

Thread: Disk Space Analyser Misreporting Disk Full?

  1. #1
    Join Date
    Oct 2008
    Location
    Isle of Islay, Scotland
    Beans
    274
    Distro
    Ubuntu Gnome 14.04 Trusty Tahr

    Disk Space Analyser Misreporting Disk Full?

    After I did this morning's updates, Disk Space Analyser popped up with a message that my hard drive is almost full. I can't see how that's possible; I have a 1TB hard drive, with not much more on it than I had on my previous system with a 160GB hard drive, and I never ran into problems then.

    I did the obvious, and deleted old Linux kernels, etc., but it's made no difference. Disk Space Analyser says I have used 925.2GB and have 55.1GB free space. I'd expect it to be pretty much the opposite - and adding up the figures from DSA's breakdown accounts for only around 50-odd GB of usage. Is DSA misreporting - in which case, can I do anything to correct it? - or am I misunderstanding something here?
    Attached Images Attached Images
    Last edited by Bearly Able; April 9th, 2013 at 01:27 PM. Reason: Correct prefix

  2. #2
    Join Date
    Apr 2008
    Location
    LOCATION=/dev/random
    Beans
    5,767
    Distro
    Ubuntu Development Release

    Re: Disk Space Analyser Misreporting Disk Full?

    Can you post the output of...
    Code:
    cd /
    sudo du -h --max-depth=1 | sort -hr
    This will list the content size of all of the directories in you root directory sorted by size.

    I suspect that you may have a runaway log file that is taking up all of your space, but post back with the output of the above commands and we'll take it from there.
    Cheesemill

  3. #3
    Join Date
    Oct 2008
    Location
    Isle of Islay, Scotland
    Beans
    274
    Distro
    Ubuntu Gnome 14.04 Trusty Tahr

    Re: Disk Space Analyser Misreporting Disk Full?

    Thanks for the reply. Here it is:

    Code:
    du: cannot access `./home/lesley/.gvfs': Permission denied
    du: cannot access `./proc/3225/task/3225/fd/3': No such file or directory
    du: cannot access `./proc/3225/task/3225/fdinfo/3': No such file or directory
    du: cannot access `./proc/3225/fd/3': No such file or directory
    du: cannot access `./proc/3225/fdinfo/3': No such file or directory
    1.3T	.
    819G	./root
    408G	./media
    36G	./home
    5.3G	./usr
    955M	./var
    397M	./lib
    49M	./boot
    18M	./etc
    8.7M	./bin
    8.6M	./sbin
    3.4M	./lib32
    1.3M	./run
    904K	./opt
    84K	./tmp
    16K	./lost+found
    4.0K	./srv
    4.0K	./selinux
    4.0K	./mnt
    4.0K	./lib64
    4.0K	./dev
    0	./sys
    0	./proc
    The reason for the discrepancy in size between this and the previous screenshot is that I have a 500GB external hard drive plugged in now. I'd disconnected it earlier, to see if it would make any difference to the analyser results as the external dive really is 80% full, but no joy.
    Last edited by Bearly Able; April 9th, 2013 at 03:22 PM.

  4. #4
    Join Date
    Oct 2008
    Location
    Isle of Islay, Scotland
    Beans
    274
    Distro
    Ubuntu Gnome 14.04 Trusty Tahr

    Re: Disk Space Analyser Misreporting Disk Full?

    Problem solved, thank you.

    I realised from the above that the problem was mine, not the Disk Analyser's. I finally tracked the culprit down to a trash folder full of deleted backups in .local/share.

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
  •