Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: 0 byte left on device

  1. #11
    Join Date
    Sep 2012
    Beans
    38

    Re: 0 byte left on device

    Now the problem is back. Same lightdm log. I removed the file but i dont get back the space on the harddrive. I cant even start firefox so that i can copy the output from terminal.
    If i run df -h it says 100% used. 40gb total and 39 gb used.
    If i run
    Code:

    cd /var/log/upstart/
    du -ch *
    Then it says 23m total. I dont have any big files there anymore. Before i removed the file i had one that was 32 gb.


    Why dosent i get my space back when i removed the file.
    The file was locked so i used sudo nautilus when i removed it.


  2. #12
    Join Date
    Jun 2006
    Location
    UK
    Beans
    Hidden!
    Distro
    Ubuntu 16.04 Xenial Xerus

    Re: 0 byte left on device

    Quote Originally Posted by MacOsX74 View Post

    Why dosent i get my space back when i removed the file.
    The file was locked so i used sudo nautilus when i removed it.
    If you opened a sudo nautilus file browser and simply used the delete key, then you moved the file to root's trash. That is why you are not getting any space back. If you need to use a root nautilus (and you would be advised to use "gksudo nautilus" not sudo nautilus) then you need to hard delete with shift+delete. Alternatively, use "sudo rm" from the terminal.

    The "deleted" file(s) will be sitting in /root/.local/share/Trash.
    Ubuntu 16.04 Desktop Guide - Ubuntu 14.04 Desktop Guide - Forum Guide to BBCode - IRC #ubuntuforums

    Member: Not Canonical Team

    Please do not PM me about your forum account unless you have been asked to. The correct place to contact an admin about your account is here.

  3. #13
    Join Date
    Mar 2010
    Location
    Squidbilly-land
    Beans
    9,669
    Distro
    Lubuntu 14.04 Trusty Tahr

    Re: 0 byte left on device

    There are 2 types of areas that can be "out of storage."
    * df -h
    * df -i

    If you have lots of small files, it is possible to run out of inodes. A few weeks ago, I ran out again on a server. The default inode reservations for small HDD partitions are often not enough - at least for people who use separate development environments for perl or ruby (perlbrew/rvm/rbenv) solutions.

    Anyway, check both types - inodes will cause storage to run out even with TBs of storage available. https://en.wikipedia.org/wiki/Inode explains.

  4. #14
    Join Date
    Sep 2012
    Beans
    38

    Re: 0 byte left on device

    Quote Originally Posted by coffeecat View Post
    If you opened a sudo nautilus file browser and simply used the delete key, then you moved the file to root's trash. That is why you are not getting any space back. If you need to use a root nautilus (and you would be advised to use "gksudo nautilus" not sudo nautilus) then you need to hard delete with shift+delete. Alternatively, use "sudo rm" from the terminal.

    The "deleted" file(s) will be sitting in /root/.local/share/Trash.
    Thanks! This worked fine. The file is gone and my space is back.
    Time to find out whats causing the huge log file.
    What is the different between sudo nautilus and gksudo nautilus?

  5. #15
    Join Date
    Feb 2013
    Beans
    Hidden!

    Re: 0 byte left on device

    As upstart runs when you boot the system, /var/log/upstart will grow with each reboot. So, you can reboot and watch the difference.
    What is the different between sudo nautilus and gksudo nautilus?
    See http://www.psychocats.net/ubuntu/graphicalsudo

  6. #16
    Join Date
    Dec 2009
    Location
    germany
    Beans
    1,020
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: 0 byte left on device

    hi macos
    the big file isn't gone. look here:

    4,0K hybrid-gfx.log.6.gz 4,0K hybrid-gfx.log.7.gz 104M lightdm.log.1.gz 96M lightdm.log.2.gz 60K lightdm.log.3.gz 52K lightdm.log.4.gz 52K lightdm.log.5.gz 48K lightdm.log.6.gz 12K lightdm.log.7.gz 4,0K modemmanager.log.1.gz

    as you see the size - there is a run-away logging - the file was rotated and ziped.
    have a look at the contens of the logfile to see whats make lightdm so confused.
    ciao
    "What is the robbing of a bank compared to the FOUNDING of a bank?" Berthold Brecht

  7. #17
    Join Date
    Sep 2012
    Beans
    38

    Re: 0 byte left on device

    Now its back with an 33Gb log file after a few restarts. Can´t open the file so i´m gonna try to copy the file to another computer to see what it says. Not that I understand much but you guys do.

  8. #18
    Join Date
    Sep 2012
    Beans
    38

    Re: 0 byte left on device

    this is the errormessage in the lightdm.log

    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message
    23/03/2013 14:46:16 Authentication deferred - ignoring client message

    think it has something to do with remote desktop.
    23/03/2013 14:46:16 Authentication deferred - ignoring client message

  9. #19
    Join Date
    Sep 2012
    Beans
    38

    Re: 0 byte left on device

    Quote Originally Posted by rnerwein View Post
    hi macos
    the big file isn't gone. look here:

    4,0K hybrid-gfx.log.6.gz 4,0K hybrid-gfx.log.7.gz 104M lightdm.log.1.gz 96M lightdm.log.2.gz 60K lightdm.log.3.gz 52K lightdm.log.4.gz 52K lightdm.log.5.gz 48K lightdm.log.6.gz 12K lightdm.log.7.gz 4,0K modemmanager.log.1.gz

    as you see the size - there is a run-away logging - the file was rotated and ziped.
    have a look at the contens of the logfile to see whats make lightdm so confused.
    ciao
    Thats nothing compared to 33Gb.

Page 2 of 2 FirstFirst 12

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
  •