/tmp at 100% space - why?

    Hello,


    I wanted to open the user crontab, so typed 'crontab -e' and as a result received this:

    Code
    /tmp/crontab.SSGOfJ/crontab: No space left on device


    So checked /tmp and found three files:

    npm-26318-bc545970

    systemd-private-9599c278efaf4e8980a22942458b471c-chrony.service-jP6vh4

    systemd-private-9599c278efaf4e8980a22942458b471c-systemd-resolved.service-PKtX2n


    There is plenty of space available.


    Why do I get a "no space" reply?


    And if I try to cd into (to check what's in there)

    Code
    /tmp/crontab.SSGOfJ/crontab

    or

    Code
    /tmp/crontab.SSGOfJ/

    it returns that the file or directory is not found.


    'df -h' however shows that /tmp is at 100%

    I'm currently using FFMPEG to record a video stream in sections onto /srv/USB, so totally bypassing the local file system. I'm assuming this should not affect /tmp.


    What can fill /tmp ?

    Some content might be slightly modified to mask personal settings- just to keep the sharks away, you never know :)

  • NAS-i-Goreng

    Hat den Titel des Themas von „crontab -e followed by "No space left on device"“ zu „/tmp at 100% space - why?“ geändert.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden