Unable to write to disk but disk isn't full












5















I can't write to any file, even as root, or do any other operation that requires writing. Neither can any process that needs to write, so they're all failing. df says I've got plenty of room:



Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1 30G 14G 15G 48% /
udev 984M 4.0K 984M 1% /dev
tmpfs 399M 668K 399M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 997M 0 997M 0% /run/shm


All of the results I find for "can't write to disk" are about legitimately full disks. I don't even know where to start here. The problem appeared out of nowhere this morning.



PHP's last log entry is "failed: No space left on device (28)". Vim says "Unable to open (file) for writing". Other applications give similar errors.



After deleting ~1gb just to be sure, the problem remains. I've also rebooted. Ubuntu 12.04










share|improve this question
















bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • what is the exact error message?

    – mchid
    Oct 25 '15 at 16:13











  • @mchid it depends on the application. PHP fails with "failed: No space left on device (28)". Trying to write a file with vim says "unable to open swap file, writing impossible", then "can't open file for writing".

    – felwithe
    Oct 25 '15 at 16:15











  • are you using btrfs or something?

    – mchid
    Oct 25 '15 at 16:17






  • 1





    Edit your question and add the output of sudo lsof -nP +L1

    – A.B.
    Oct 25 '15 at 16:32








  • 2





    You should write an answer. Give me a ping for an upvote.

    – A.B.
    Oct 25 '15 at 17:02
















5















I can't write to any file, even as root, or do any other operation that requires writing. Neither can any process that needs to write, so they're all failing. df says I've got plenty of room:



Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1 30G 14G 15G 48% /
udev 984M 4.0K 984M 1% /dev
tmpfs 399M 668K 399M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 997M 0 997M 0% /run/shm


All of the results I find for "can't write to disk" are about legitimately full disks. I don't even know where to start here. The problem appeared out of nowhere this morning.



PHP's last log entry is "failed: No space left on device (28)". Vim says "Unable to open (file) for writing". Other applications give similar errors.



After deleting ~1gb just to be sure, the problem remains. I've also rebooted. Ubuntu 12.04










share|improve this question
















bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • what is the exact error message?

    – mchid
    Oct 25 '15 at 16:13











  • @mchid it depends on the application. PHP fails with "failed: No space left on device (28)". Trying to write a file with vim says "unable to open swap file, writing impossible", then "can't open file for writing".

    – felwithe
    Oct 25 '15 at 16:15











  • are you using btrfs or something?

    – mchid
    Oct 25 '15 at 16:17






  • 1





    Edit your question and add the output of sudo lsof -nP +L1

    – A.B.
    Oct 25 '15 at 16:32








  • 2





    You should write an answer. Give me a ping for an upvote.

    – A.B.
    Oct 25 '15 at 17:02














5












5








5








I can't write to any file, even as root, or do any other operation that requires writing. Neither can any process that needs to write, so they're all failing. df says I've got plenty of room:



Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1 30G 14G 15G 48% /
udev 984M 4.0K 984M 1% /dev
tmpfs 399M 668K 399M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 997M 0 997M 0% /run/shm


All of the results I find for "can't write to disk" are about legitimately full disks. I don't even know where to start here. The problem appeared out of nowhere this morning.



PHP's last log entry is "failed: No space left on device (28)". Vim says "Unable to open (file) for writing". Other applications give similar errors.



After deleting ~1gb just to be sure, the problem remains. I've also rebooted. Ubuntu 12.04










share|improve this question
















I can't write to any file, even as root, or do any other operation that requires writing. Neither can any process that needs to write, so they're all failing. df says I've got plenty of room:



Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1 30G 14G 15G 48% /
udev 984M 4.0K 984M 1% /dev
tmpfs 399M 668K 399M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 997M 0 997M 0% /run/shm


All of the results I find for "can't write to disk" are about legitimately full disks. I don't even know where to start here. The problem appeared out of nowhere this morning.



PHP's last log entry is "failed: No space left on device (28)". Vim says "Unable to open (file) for writing". Other applications give similar errors.



After deleting ~1gb just to be sure, the problem remains. I've also rebooted. Ubuntu 12.04







filesystem files disk






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 25 '15 at 17:25









Tim

20.1k1586141




20.1k1586141










asked Oct 25 '15 at 16:01









felwithefelwithe

174514




174514





bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • what is the exact error message?

    – mchid
    Oct 25 '15 at 16:13











  • @mchid it depends on the application. PHP fails with "failed: No space left on device (28)". Trying to write a file with vim says "unable to open swap file, writing impossible", then "can't open file for writing".

    – felwithe
    Oct 25 '15 at 16:15











  • are you using btrfs or something?

    – mchid
    Oct 25 '15 at 16:17






  • 1





    Edit your question and add the output of sudo lsof -nP +L1

    – A.B.
    Oct 25 '15 at 16:32








  • 2





    You should write an answer. Give me a ping for an upvote.

    – A.B.
    Oct 25 '15 at 17:02



















  • what is the exact error message?

    – mchid
    Oct 25 '15 at 16:13











  • @mchid it depends on the application. PHP fails with "failed: No space left on device (28)". Trying to write a file with vim says "unable to open swap file, writing impossible", then "can't open file for writing".

    – felwithe
    Oct 25 '15 at 16:15











  • are you using btrfs or something?

    – mchid
    Oct 25 '15 at 16:17






  • 1





    Edit your question and add the output of sudo lsof -nP +L1

    – A.B.
    Oct 25 '15 at 16:32








  • 2





    You should write an answer. Give me a ping for an upvote.

    – A.B.
    Oct 25 '15 at 17:02

















what is the exact error message?

– mchid
Oct 25 '15 at 16:13





what is the exact error message?

– mchid
Oct 25 '15 at 16:13













@mchid it depends on the application. PHP fails with "failed: No space left on device (28)". Trying to write a file with vim says "unable to open swap file, writing impossible", then "can't open file for writing".

– felwithe
Oct 25 '15 at 16:15





@mchid it depends on the application. PHP fails with "failed: No space left on device (28)". Trying to write a file with vim says "unable to open swap file, writing impossible", then "can't open file for writing".

– felwithe
Oct 25 '15 at 16:15













are you using btrfs or something?

– mchid
Oct 25 '15 at 16:17





are you using btrfs or something?

– mchid
Oct 25 '15 at 16:17




1




1





Edit your question and add the output of sudo lsof -nP +L1

– A.B.
Oct 25 '15 at 16:32







Edit your question and add the output of sudo lsof -nP +L1

– A.B.
Oct 25 '15 at 16:32






2




2





You should write an answer. Give me a ping for an upvote.

– A.B.
Oct 25 '15 at 17:02





You should write an answer. Give me a ping for an upvote.

– A.B.
Oct 25 '15 at 17:02










1 Answer
1






active

oldest

votes


















0














Answered in edit by OP:




Edit: It turned out that I was out of inodes even though I wasn't out of disk space. Problem was solved here:



You are out of inodes. It's likely that you have a directory somewhere with
many very small files.





What are inodes?




Ext4 has a theoretical limit of 4 billion files, which is restricted by the size of inode number it uses to identify each file (ext4 uses 32-bit inode numbers). However, as John says, Ext4 allocates inode tables statically, so the actual limit is set when the file system is created.




Source






share|improve this answer


























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f689774%2funable-to-write-to-disk-but-disk-isnt-full%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Answered in edit by OP:




    Edit: It turned out that I was out of inodes even though I wasn't out of disk space. Problem was solved here:



    You are out of inodes. It's likely that you have a directory somewhere with
    many very small files.





    What are inodes?




    Ext4 has a theoretical limit of 4 billion files, which is restricted by the size of inode number it uses to identify each file (ext4 uses 32-bit inode numbers). However, as John says, Ext4 allocates inode tables statically, so the actual limit is set when the file system is created.




    Source






    share|improve this answer






























      0














      Answered in edit by OP:




      Edit: It turned out that I was out of inodes even though I wasn't out of disk space. Problem was solved here:



      You are out of inodes. It's likely that you have a directory somewhere with
      many very small files.





      What are inodes?




      Ext4 has a theoretical limit of 4 billion files, which is restricted by the size of inode number it uses to identify each file (ext4 uses 32-bit inode numbers). However, as John says, Ext4 allocates inode tables statically, so the actual limit is set when the file system is created.




      Source






      share|improve this answer




























        0












        0








        0







        Answered in edit by OP:




        Edit: It turned out that I was out of inodes even though I wasn't out of disk space. Problem was solved here:



        You are out of inodes. It's likely that you have a directory somewhere with
        many very small files.





        What are inodes?




        Ext4 has a theoretical limit of 4 billion files, which is restricted by the size of inode number it uses to identify each file (ext4 uses 32-bit inode numbers). However, as John says, Ext4 allocates inode tables statically, so the actual limit is set when the file system is created.




        Source






        share|improve this answer















        Answered in edit by OP:




        Edit: It turned out that I was out of inodes even though I wasn't out of disk space. Problem was solved here:



        You are out of inodes. It's likely that you have a directory somewhere with
        many very small files.





        What are inodes?




        Ext4 has a theoretical limit of 4 billion files, which is restricted by the size of inode number it uses to identify each file (ext4 uses 32-bit inode numbers). However, as John says, Ext4 allocates inode tables statically, so the actual limit is set when the file system is created.




        Source







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Apr 13 '17 at 12:23









        Community

        1




        1










        answered Oct 25 '15 at 17:28









        TimTim

        20.1k1586141




        20.1k1586141






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f689774%2funable-to-write-to-disk-but-disk-isnt-full%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            GameSpot

            日野市

            Tu-95轟炸機