Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: OS 13.2 doesnt boot: - no space left on device

  1. #1

    Question OS 13.2 doesnt boot: - no space left on device

    Hello ,

    since a few days I have a problem with my OpenSuse 13.2 System:

    KDE doesnt boot, I only can use the terminal (Strg+Alt+F1) to do something. And there it alway says "no space left on device" but df -h says
    Code:
     ...
    /dev/sda7                                                20G   15G  4.2G  78% / 
    ...
    So I googled and found out that it coud be beacuse of no left "Inodes". So I looked up with "df -i" and so there was the issue. But on Google I found only if there are no inodes avaible (100% used). But my problem is there are no Inodes on my partition:

    df -i:
    Code:
    Filesystem                                              Inodes  IUsed   IFree IUse% Mounted on
    ...
    /dev/sda7                                                    0      0       0     - /
    ...
    Does anybody know, how I can fix this problem? Thank you very much.
    Please say if you need some more information!

    edit: btw its an btrfs partition

    _________________________________

    not a native speaker
    Last edited by k3jj3k; 25-Mar-2015 at 06:40. Reason: additional information

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,718

    Default Re: OS 13.2 doesnt boot: - no space left on device

    You use Btrfs? When yes, what about snapshots?
    Henk van Velden

  3. #3

    Default Re: OS 13.2 doesnt boot: - no space left on device

    Yes I use btrfs. What do you mean exactly with 'what about snapshots'? I didnt use the snapshot function of btrfs before.

  4. #4
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,278
    Blog Entries
    15

    Default Re: OS 13.2 doesnt boot: - no space left on device

    Quote Originally Posted by k3jj3k View Post
    Yes I use btrfs. What do you mean exactly with 'what about snapshots'? I didnt use the snapshot function of btrfs before.
    Hi
    You need to configure snapper (or disable) with such a small /

    Edit the file /etc/snapper/configs/root and set the timeline create to
    no (if not already no) and then set number limit to say 2 and important
    to 2.

    Manually run the cron job /etc/cron.daily called suse.de-snapper

    Then use the command `snapper list` you should only have a few entries
    and disk space back...

    The df command is not applicable for btrfs, use btrfs filesystem show and btrfs filesystem df / commands....
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  5. #5

    Question Re: OS 13.2 doesnt boot: - no space left on device

    Thank you very much! I dont know why, but the fix from malcolmlewis works for me.

    I have a comprehension question:

    malcolmlewis:
    The df command is not applicable for btrfs, use btrfs filesystem show and btrfs filesystem df / commands....
    If the df command doesnt work correctly with btrfs. Does it mean the space information in Dolphin is also wrong?

    If I use btrfs filesystem show it says:

    Code:
    Label: none  uuid: 5839be1b-2df2-437e-8dda-8ceccd37587c
            Total devices 1 FS bytes used 13.96GiB
            devid    1 size 19.60GiB used 19.60GiB path /dev/sda7
    
    Btrfs v3.16.2+20141003
    There it says size 19.6 GiB used 19.60GiB. But now it works... it must be more space free?! Or read I it wrong?
    Thaks again!

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,278
    Blog Entries
    15

    Default Re: OS 13.2 doesnt boot: - no space left on device

    Hi
    What about do you get from;
    Code:
    btrfs filesystem df /
    If you look at the first line in the output of btrfs filesystem show
    Code:
    Total devices 1 FS bytes used 13.96GiB
    That should pretty much match the df -kh command?

    The second line is what's been alloacted, in your case the full amount, what happens is if you are making changes over a day, snapshots can add up (use snapper list command) for example large updates etc, so I think if your running only 20GB, then creating a root cronjob running every 3 or 4 hours pointing at the daily clean up job would help keep it under control, else I would disable snapper and not have snapshots.

    There are some commands you can run for cleaning up, but need to see the output from the above filesystem command first to advise.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #7

    Thumbs up Re: OS 13.2 doesnt boot: - no space left on device

    The idea with cronjob is very good.Here my "btrfs filesystem df /"

    Code:
    Data, single: total=17.32GiB, used=13.48GiB
    System, DUP: total=8.00MiB, used=16.00KiB
    System, single: total=4.00MiB, used=0.00B
    Metadata, DUP: total=1.12GiB, used=705.88MiB
    Metadata, single: total=8.00MiB, used=0.00B
    GlobalReserve, single: total=240.00MiB, used=0.00B

    btw:

    That should pretty much match the df -kh command?
    df -kh
    Code:
    Filesystem      Size  Used Avail Use% Mounted on
    /dev/sda7        20G   16G  3.9G  80% /
    ...
    or df -k
    Code:
    /dev/sda7       20550656 15823980   4030196  80% /
    vs. btrfs filesystem show
    Label: none uuid: 5839be1b-2df2-437e-8dda-8ceccd37587c
    Total devices 1 FS bytes used 14.17GiB
    devid 1 size 19.60GiB used 19.60GiB path /dev/sda7
    it's about 1GB diffrent, but it doesnt matter.

  8. #8
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,278
    Blog Entries
    15

    Default Re: OS 13.2 doesnt boot: - no space left on device

    On Fri 27 Mar 2015 08:56:01 AM CDT, k3jj3k wrote:


    The idea with cronjob is very good.Here my "btrfs filesystem df /"


    Code:
    --------------------
    Data, single: total=17.32GiB, used=13.48GiB
    System, DUP: total=8.00MiB, used=16.00KiB
    System, single: total=4.00MiB, used=0.00B
    Metadata, DUP: total=1.12GiB, used=705.88MiB
    Metadata, single: total=8.00MiB, used=0.00B
    GlobalReserve, single: total=240.00MiB, used=0.00B
    --------------------



    btw:

    > That should pretty much match the df -kh command?


    df -kh

    Code:
    --------------------
    Filesystem Size Used Avail Use% Mounted on
    /dev/sda7 20G 16G 3.9G 80% /
    ...
    --------------------


    or df -k

    Code:
    --------------------
    /dev/sda7 20550656 15823980 4030196 80% /
    --------------------


    vs. btrfs filesystem show
    > Label: none uuid: 5839be1b-2df2-437e-8dda-8ceccd37587c
    > Total devices 1 FS bytes used 14.17GiB
    > devid 1 size 19.60GiB used 19.60GiB path /dev/sda7


    it's about 1GB diffrent, but it doesnt matter.


    Hi
    I would try balancing the btrfs system, as root user (don't use sudo...)
    Code:
    btrfs balance start /
    See how that goes.

    --
    Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
    SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.38-44-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  9. #9

    Default Re: OS 13.2 doesnt boot: - no space left on device

    If I try "btrfs balance start /" as root, it stops with an error:

    Code:
    ERROR: error during balancing '/' - No space left on device
    There may be more info in syslog - try dmesg | tail
    But now with "btrfs filesystem show" there is more free spacein the row "devid"
    Code:
    Label: none  uuid: 5839be1b-2df2-437e-8dda-8ceccd37587c
            Total devices 1 FS bytes used 14.17GiB
            devid    1 size 19.60GiB used 16.81GiB path /dev/sda7
    
    Btrfs v3.16.2+20141003
    Maybe its better to buy a new HDD, so I can increase the space of the partition. But actual I dont need more than 20 GB Space (without home) for my system and I should change btrfs to ext4? what do you mean? Or have you maybe some more suggestions?
    I dont give up!

    greets k3jj3k

  10. #10
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,278
    Blog Entries
    15

    Default Re: OS 13.2 doesnt boot: - no space left on device

    Quote Originally Posted by k3jj3k View Post
    If I try "btrfs balance start /" as root, it stops with an error:

    Code:
    ERROR: error during balancing '/' - No space left on device
    There may be more info in syslog - try dmesg | tail
    But now with "btrfs filesystem show" there is more free spacein the row "devid"
    Code:
    Label: none  uuid: 5839be1b-2df2-437e-8dda-8ceccd37587c
            Total devices 1 FS bytes used 14.17GiB
            devid    1 size 19.60GiB used 16.81GiB path /dev/sda7
    
    Btrfs v3.16.2+20141003
    Maybe its better to buy a new HDD, so I can increase the space of the partition. But actual I dont need more than 20 GB Space (without home) for my system and I should change btrfs to ext4? what do you mean? Or have you maybe some more suggestions?
    I dont give up!

    greets k3jj3k
    Hi
    You may need to try a few times to see how it goes....

    No, 20GB is fine, unless your using snapshots then disable, else only keep a few and run an additional cron job or two.... Normally I use 40GB these days and leave snapper running with only 6 snapshots retained in a day....
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

Page 1 of 2 12 LastLast

Posting Permissions

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