How to keep control over disk-size












7















I'm using Cloud9 (railstutorial.org) and noticed that the disk space used by my workspace is fastly growing toward the disk quota.



Is there a way to clean up the workspace and thereby reduce the disk space used?



The workspace is currently 817MB (see below using quota -s). I downloaded it to look at the size of the directories, and I don't understand it. The directory containing my project is only 170 MB in size and the .9 folder is only 3 MB. So together that doesn't come near the 817 MB... And the disk space used keeps growing even though I don't I'm making any major changes to the content of my project.



  Size  Used Avail  Use%
1.1G 817M 222M 79%


Has it perhaps got to do with the .9 folder? For example, I've manually deleted several sub-projects but in the .9 folder these projects still exist, including their files. I also wonder if perhaps different versions of gems remain installed in the .9 folder... so that if you update a gem, it includes both versions of the gem.



I'm not sure how this folder or Cloud9 storage in general works, but my question is how to clean up disk space (without having to remove anything in my project)? Is there perhaps some clean-up function? I could of course create a new workspace and upload my project there, but perhaps there's an alternative while keeping the current workspace.










share|improve this question



























    7















    I'm using Cloud9 (railstutorial.org) and noticed that the disk space used by my workspace is fastly growing toward the disk quota.



    Is there a way to clean up the workspace and thereby reduce the disk space used?



    The workspace is currently 817MB (see below using quota -s). I downloaded it to look at the size of the directories, and I don't understand it. The directory containing my project is only 170 MB in size and the .9 folder is only 3 MB. So together that doesn't come near the 817 MB... And the disk space used keeps growing even though I don't I'm making any major changes to the content of my project.



      Size  Used Avail  Use%
    1.1G 817M 222M 79%


    Has it perhaps got to do with the .9 folder? For example, I've manually deleted several sub-projects but in the .9 folder these projects still exist, including their files. I also wonder if perhaps different versions of gems remain installed in the .9 folder... so that if you update a gem, it includes both versions of the gem.



    I'm not sure how this folder or Cloud9 storage in general works, but my question is how to clean up disk space (without having to remove anything in my project)? Is there perhaps some clean-up function? I could of course create a new workspace and upload my project there, but perhaps there's an alternative while keeping the current workspace.










    share|improve this question

























      7












      7








      7


      4






      I'm using Cloud9 (railstutorial.org) and noticed that the disk space used by my workspace is fastly growing toward the disk quota.



      Is there a way to clean up the workspace and thereby reduce the disk space used?



      The workspace is currently 817MB (see below using quota -s). I downloaded it to look at the size of the directories, and I don't understand it. The directory containing my project is only 170 MB in size and the .9 folder is only 3 MB. So together that doesn't come near the 817 MB... And the disk space used keeps growing even though I don't I'm making any major changes to the content of my project.



        Size  Used Avail  Use%
      1.1G 817M 222M 79%


      Has it perhaps got to do with the .9 folder? For example, I've manually deleted several sub-projects but in the .9 folder these projects still exist, including their files. I also wonder if perhaps different versions of gems remain installed in the .9 folder... so that if you update a gem, it includes both versions of the gem.



      I'm not sure how this folder or Cloud9 storage in general works, but my question is how to clean up disk space (without having to remove anything in my project)? Is there perhaps some clean-up function? I could of course create a new workspace and upload my project there, but perhaps there's an alternative while keeping the current workspace.










      share|improve this question














      I'm using Cloud9 (railstutorial.org) and noticed that the disk space used by my workspace is fastly growing toward the disk quota.



      Is there a way to clean up the workspace and thereby reduce the disk space used?



      The workspace is currently 817MB (see below using quota -s). I downloaded it to look at the size of the directories, and I don't understand it. The directory containing my project is only 170 MB in size and the .9 folder is only 3 MB. So together that doesn't come near the 817 MB... And the disk space used keeps growing even though I don't I'm making any major changes to the content of my project.



        Size  Used Avail  Use%
      1.1G 817M 222M 79%


      Has it perhaps got to do with the .9 folder? For example, I've manually deleted several sub-projects but in the .9 folder these projects still exist, including their files. I also wonder if perhaps different versions of gems remain installed in the .9 folder... so that if you update a gem, it includes both versions of the gem.



      I'm not sure how this folder or Cloud9 storage in general works, but my question is how to clean up disk space (without having to remove anything in my project)? Is there perhaps some clean-up function? I could of course create a new workspace and upload my project there, but perhaps there's an alternative while keeping the current workspace.







      cloud9-ide






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 18 '15 at 14:53









      NickNick

      1,33911849




      1,33911849
























          4 Answers
          4






          active

          oldest

          votes


















          8














          The du-c9 command lists all the files contributing to your quota. You can reclaim disk space by deleting files listed by this command.






          share|improve this answer
























          • Cool to see. It confirms that in my case it are particularly gems that take up a lot of space. This includes gems that are no longer in use. Is there a better way to remove gems than to just delete its files one by one?

            – Nick
            May 19 '15 at 12:43











          • Development.log and test.log also took over 100MB in my case. So I removed them.

            – Nick
            May 19 '15 at 12:49






          • 2





            Helpful to reduce disk space are: gem cleanup, rake tmp:clear (clear session, cache, and socket files from tmp/), rake assets:clean (remove old compiled assets), and rake log:clear (truncates all *.log files in log/ to zero bytes).

            – Nick
            May 31 '15 at 10:38





















          7














          For a user-friendly interface, you may want to install ncdu to see the size of all your folders. First, free some space for the install. A common way to do this is by removing your tmp folder:



          rm -rf /tmp/*


          Then install ncdu:



          sudo apt-get install ncdu


          Then run ncdu and navigate through your folders to see which ones are using up the most space:



          ncdu ~


          Reference: https://docs.c9.io/discuss/557ecf787eafa719001d1af8






          share|improve this answer


























          • ncdu is excellent and takes very little space itself. Thanks very much!

            – Marnen Laibow-Koser
            Dec 4 '15 at 22:59



















          2














          For me the answers above unfortunately did not work (the first produced a list incomprehensibly long, so long that I run out of scroll space in the shell and the second one produced a strange list-- see at the end of this answer):



          What did was the following:



          1) From this support faq article: du -hx / -t 50000000



          2) Identify the culprit from the easy to read, easy to understand list: in my case 1.1G /home/ubuntu/.local/share/heroku/tmp



          3) From the examples of this article: rm -r /home/ubuntu/.local/share/heroku/tmp



          Strange list:
          1 ./.bundle
          1 ./.git
          1 ./README.md
          1 ./Project_5
          2 ./.c9
          2 ./Project_1
          3 ./Project_2
          17 ./Project_3
          28 ./Project_4
          50 .






          share|improve this answer































            0














            If you want to dig into more details of which file is affecting your workspace disk try this command: sudo du -h -t 50M / --exclude=/nix --exclude=/mnt --exclude=/proc



            This will give you all the files on your Linux server and then you can remove any file by this command:
            sudo rm -rf /fileThatNeedsToDelete/*






            share|improve this answer























              Your Answer






              StackExchange.ifUsing("editor", function () {
              StackExchange.using("externalEditor", function () {
              StackExchange.using("snippets", function () {
              StackExchange.snippets.init();
              });
              });
              }, "code-snippets");

              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "1"
              };
              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%2fstackoverflow.com%2fquestions%2f30306455%2fhow-to-keep-control-over-disk-size%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              4 Answers
              4






              active

              oldest

              votes








              4 Answers
              4






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              8














              The du-c9 command lists all the files contributing to your quota. You can reclaim disk space by deleting files listed by this command.






              share|improve this answer
























              • Cool to see. It confirms that in my case it are particularly gems that take up a lot of space. This includes gems that are no longer in use. Is there a better way to remove gems than to just delete its files one by one?

                – Nick
                May 19 '15 at 12:43











              • Development.log and test.log also took over 100MB in my case. So I removed them.

                – Nick
                May 19 '15 at 12:49






              • 2





                Helpful to reduce disk space are: gem cleanup, rake tmp:clear (clear session, cache, and socket files from tmp/), rake assets:clean (remove old compiled assets), and rake log:clear (truncates all *.log files in log/ to zero bytes).

                – Nick
                May 31 '15 at 10:38


















              8














              The du-c9 command lists all the files contributing to your quota. You can reclaim disk space by deleting files listed by this command.






              share|improve this answer
























              • Cool to see. It confirms that in my case it are particularly gems that take up a lot of space. This includes gems that are no longer in use. Is there a better way to remove gems than to just delete its files one by one?

                – Nick
                May 19 '15 at 12:43











              • Development.log and test.log also took over 100MB in my case. So I removed them.

                – Nick
                May 19 '15 at 12:49






              • 2





                Helpful to reduce disk space are: gem cleanup, rake tmp:clear (clear session, cache, and socket files from tmp/), rake assets:clean (remove old compiled assets), and rake log:clear (truncates all *.log files in log/ to zero bytes).

                – Nick
                May 31 '15 at 10:38
















              8












              8








              8







              The du-c9 command lists all the files contributing to your quota. You can reclaim disk space by deleting files listed by this command.






              share|improve this answer













              The du-c9 command lists all the files contributing to your quota. You can reclaim disk space by deleting files listed by this command.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered May 19 '15 at 12:15









              Fabian JakobsFabian Jakobs

              16.1k53336




              16.1k53336













              • Cool to see. It confirms that in my case it are particularly gems that take up a lot of space. This includes gems that are no longer in use. Is there a better way to remove gems than to just delete its files one by one?

                – Nick
                May 19 '15 at 12:43











              • Development.log and test.log also took over 100MB in my case. So I removed them.

                – Nick
                May 19 '15 at 12:49






              • 2





                Helpful to reduce disk space are: gem cleanup, rake tmp:clear (clear session, cache, and socket files from tmp/), rake assets:clean (remove old compiled assets), and rake log:clear (truncates all *.log files in log/ to zero bytes).

                – Nick
                May 31 '15 at 10:38





















              • Cool to see. It confirms that in my case it are particularly gems that take up a lot of space. This includes gems that are no longer in use. Is there a better way to remove gems than to just delete its files one by one?

                – Nick
                May 19 '15 at 12:43











              • Development.log and test.log also took over 100MB in my case. So I removed them.

                – Nick
                May 19 '15 at 12:49






              • 2





                Helpful to reduce disk space are: gem cleanup, rake tmp:clear (clear session, cache, and socket files from tmp/), rake assets:clean (remove old compiled assets), and rake log:clear (truncates all *.log files in log/ to zero bytes).

                – Nick
                May 31 '15 at 10:38



















              Cool to see. It confirms that in my case it are particularly gems that take up a lot of space. This includes gems that are no longer in use. Is there a better way to remove gems than to just delete its files one by one?

              – Nick
              May 19 '15 at 12:43





              Cool to see. It confirms that in my case it are particularly gems that take up a lot of space. This includes gems that are no longer in use. Is there a better way to remove gems than to just delete its files one by one?

              – Nick
              May 19 '15 at 12:43













              Development.log and test.log also took over 100MB in my case. So I removed them.

              – Nick
              May 19 '15 at 12:49





              Development.log and test.log also took over 100MB in my case. So I removed them.

              – Nick
              May 19 '15 at 12:49




              2




              2





              Helpful to reduce disk space are: gem cleanup, rake tmp:clear (clear session, cache, and socket files from tmp/), rake assets:clean (remove old compiled assets), and rake log:clear (truncates all *.log files in log/ to zero bytes).

              – Nick
              May 31 '15 at 10:38







              Helpful to reduce disk space are: gem cleanup, rake tmp:clear (clear session, cache, and socket files from tmp/), rake assets:clean (remove old compiled assets), and rake log:clear (truncates all *.log files in log/ to zero bytes).

              – Nick
              May 31 '15 at 10:38















              7














              For a user-friendly interface, you may want to install ncdu to see the size of all your folders. First, free some space for the install. A common way to do this is by removing your tmp folder:



              rm -rf /tmp/*


              Then install ncdu:



              sudo apt-get install ncdu


              Then run ncdu and navigate through your folders to see which ones are using up the most space:



              ncdu ~


              Reference: https://docs.c9.io/discuss/557ecf787eafa719001d1af8






              share|improve this answer


























              • ncdu is excellent and takes very little space itself. Thanks very much!

                – Marnen Laibow-Koser
                Dec 4 '15 at 22:59
















              7














              For a user-friendly interface, you may want to install ncdu to see the size of all your folders. First, free some space for the install. A common way to do this is by removing your tmp folder:



              rm -rf /tmp/*


              Then install ncdu:



              sudo apt-get install ncdu


              Then run ncdu and navigate through your folders to see which ones are using up the most space:



              ncdu ~


              Reference: https://docs.c9.io/discuss/557ecf787eafa719001d1af8






              share|improve this answer


























              • ncdu is excellent and takes very little space itself. Thanks very much!

                – Marnen Laibow-Koser
                Dec 4 '15 at 22:59














              7












              7








              7







              For a user-friendly interface, you may want to install ncdu to see the size of all your folders. First, free some space for the install. A common way to do this is by removing your tmp folder:



              rm -rf /tmp/*


              Then install ncdu:



              sudo apt-get install ncdu


              Then run ncdu and navigate through your folders to see which ones are using up the most space:



              ncdu ~


              Reference: https://docs.c9.io/discuss/557ecf787eafa719001d1af8






              share|improve this answer















              For a user-friendly interface, you may want to install ncdu to see the size of all your folders. First, free some space for the install. A common way to do this is by removing your tmp folder:



              rm -rf /tmp/*


              Then install ncdu:



              sudo apt-get install ncdu


              Then run ncdu and navigate through your folders to see which ones are using up the most space:



              ncdu ~


              Reference: https://docs.c9.io/discuss/557ecf787eafa719001d1af8







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Sep 13 '16 at 20:55

























              answered Oct 2 '15 at 17:04









              Akira YamamotoAkira Yamamoto

              3,32123337




              3,32123337













              • ncdu is excellent and takes very little space itself. Thanks very much!

                – Marnen Laibow-Koser
                Dec 4 '15 at 22:59



















              • ncdu is excellent and takes very little space itself. Thanks very much!

                – Marnen Laibow-Koser
                Dec 4 '15 at 22:59

















              ncdu is excellent and takes very little space itself. Thanks very much!

              – Marnen Laibow-Koser
              Dec 4 '15 at 22:59





              ncdu is excellent and takes very little space itself. Thanks very much!

              – Marnen Laibow-Koser
              Dec 4 '15 at 22:59











              2














              For me the answers above unfortunately did not work (the first produced a list incomprehensibly long, so long that I run out of scroll space in the shell and the second one produced a strange list-- see at the end of this answer):



              What did was the following:



              1) From this support faq article: du -hx / -t 50000000



              2) Identify the culprit from the easy to read, easy to understand list: in my case 1.1G /home/ubuntu/.local/share/heroku/tmp



              3) From the examples of this article: rm -r /home/ubuntu/.local/share/heroku/tmp



              Strange list:
              1 ./.bundle
              1 ./.git
              1 ./README.md
              1 ./Project_5
              2 ./.c9
              2 ./Project_1
              3 ./Project_2
              17 ./Project_3
              28 ./Project_4
              50 .






              share|improve this answer




























                2














                For me the answers above unfortunately did not work (the first produced a list incomprehensibly long, so long that I run out of scroll space in the shell and the second one produced a strange list-- see at the end of this answer):



                What did was the following:



                1) From this support faq article: du -hx / -t 50000000



                2) Identify the culprit from the easy to read, easy to understand list: in my case 1.1G /home/ubuntu/.local/share/heroku/tmp



                3) From the examples of this article: rm -r /home/ubuntu/.local/share/heroku/tmp



                Strange list:
                1 ./.bundle
                1 ./.git
                1 ./README.md
                1 ./Project_5
                2 ./.c9
                2 ./Project_1
                3 ./Project_2
                17 ./Project_3
                28 ./Project_4
                50 .






                share|improve this answer


























                  2












                  2








                  2







                  For me the answers above unfortunately did not work (the first produced a list incomprehensibly long, so long that I run out of scroll space in the shell and the second one produced a strange list-- see at the end of this answer):



                  What did was the following:



                  1) From this support faq article: du -hx / -t 50000000



                  2) Identify the culprit from the easy to read, easy to understand list: in my case 1.1G /home/ubuntu/.local/share/heroku/tmp



                  3) From the examples of this article: rm -r /home/ubuntu/.local/share/heroku/tmp



                  Strange list:
                  1 ./.bundle
                  1 ./.git
                  1 ./README.md
                  1 ./Project_5
                  2 ./.c9
                  2 ./Project_1
                  3 ./Project_2
                  17 ./Project_3
                  28 ./Project_4
                  50 .






                  share|improve this answer













                  For me the answers above unfortunately did not work (the first produced a list incomprehensibly long, so long that I run out of scroll space in the shell and the second one produced a strange list-- see at the end of this answer):



                  What did was the following:



                  1) From this support faq article: du -hx / -t 50000000



                  2) Identify the culprit from the easy to read, easy to understand list: in my case 1.1G /home/ubuntu/.local/share/heroku/tmp



                  3) From the examples of this article: rm -r /home/ubuntu/.local/share/heroku/tmp



                  Strange list:
                  1 ./.bundle
                  1 ./.git
                  1 ./README.md
                  1 ./Project_5
                  2 ./.c9
                  2 ./Project_1
                  3 ./Project_2
                  17 ./Project_3
                  28 ./Project_4
                  50 .







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 3 '17 at 18:02









                  alexandros84alexandros84

                  11010




                  11010























                      0














                      If you want to dig into more details of which file is affecting your workspace disk try this command: sudo du -h -t 50M / --exclude=/nix --exclude=/mnt --exclude=/proc



                      This will give you all the files on your Linux server and then you can remove any file by this command:
                      sudo rm -rf /fileThatNeedsToDelete/*






                      share|improve this answer




























                        0














                        If you want to dig into more details of which file is affecting your workspace disk try this command: sudo du -h -t 50M / --exclude=/nix --exclude=/mnt --exclude=/proc



                        This will give you all the files on your Linux server and then you can remove any file by this command:
                        sudo rm -rf /fileThatNeedsToDelete/*






                        share|improve this answer


























                          0












                          0








                          0







                          If you want to dig into more details of which file is affecting your workspace disk try this command: sudo du -h -t 50M / --exclude=/nix --exclude=/mnt --exclude=/proc



                          This will give you all the files on your Linux server and then you can remove any file by this command:
                          sudo rm -rf /fileThatNeedsToDelete/*






                          share|improve this answer













                          If you want to dig into more details of which file is affecting your workspace disk try this command: sudo du -h -t 50M / --exclude=/nix --exclude=/mnt --exclude=/proc



                          This will give you all the files on your Linux server and then you can remove any file by this command:
                          sudo rm -rf /fileThatNeedsToDelete/*







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 22 '18 at 3:51









                          Hamid HemaniHamid Hemani

                          32




                          32






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Stack Overflow!


                              • 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%2fstackoverflow.com%2fquestions%2f30306455%2fhow-to-keep-control-over-disk-size%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

                              "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                              Alcedinidae

                              RAC Tourist Trophy