How much storage should be taken up by 'System' in MacOS Sierra Announcing the arrival of...

Determine whether f is a function, an injection, a surjection

Are my PIs rude or am I just being too sensitive?

The following signatures were invalid: EXPKEYSIG 1397BC53640DB551

Training a classifier when some of the features are unknown

Stop battery usage [Ubuntu 18]

What is the order of Mitzvot in Rambam's Sefer Hamitzvot?

90's book, teen horror

What can I do if my MacBook isn’t charging but already ran out?

Windows 10: How to Lock (not sleep) laptop on lid close?

Why is "Captain Marvel" translated as male in Portugal?

Is drag coefficient lowest at zero angle of attack?

Unexpected result with right shift after bitwise negation

Do working physicists consider Newtonian mechanics to be "falsified"?

Slither Like a Snake

Fishing simulator

Is it possible to ask for a hotel room without minibar/extra services?

When communicating altitude with a '9' in it, should it be pronounced "nine hundred" or "niner hundred"?

How should I respond to a player wanting to catch a sword between their hands?

Statistical model of ligand substitution

Can a monk deflect thrown melee weapons?

How do I automatically answer y in bash script?

Need a suitable toxic chemical for a murder plot in my novel

Blender game recording at the wrong time

Passing functions in C++



How much storage should be taken up by 'System' in MacOS Sierra



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Good program to visualize file system usage on Mac?Mac's hard drive is filling itselfMacOS Sierra - USB boot failureHow to toggle “Tap to Click” on macOS sierraHas my macOS Sierra system been infected by unknown users?macOS Sierra Installation IssuesMacOS Sierra installer bizarrely deleting itself when download completesInstall Composer MacOS SierramacOS 10.13.1 High Sierra Disk Space iMacWhat might be the source/logic behind the hash values used by “Unified Logging” system on macOS?Mac System storage taking up too much spaceRemove build in Apache httpd on macOS (OSX)





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







14















MacOS Sierra has a helpful "Manage Storage" option in "About this Mac".



I noticed that my Mac uses 152 gigs of storage just for "system". I'm wondering if that's normal, because it seems outrageously high to me. I would imagine the OS would take up, certainly less than 100 gigs under normal circumstances.



Is there any way to cut down on how much storage is taken up by the system?



enter image description here










share|improve this question

























  • "System" is a bit of a catchall category; you need something that'll give more details about where all that space is going. See this previous question, and this similar one on apple.se.

    – Gordon Davisson
    Oct 19 '16 at 4:45


















14















MacOS Sierra has a helpful "Manage Storage" option in "About this Mac".



I noticed that my Mac uses 152 gigs of storage just for "system". I'm wondering if that's normal, because it seems outrageously high to me. I would imagine the OS would take up, certainly less than 100 gigs under normal circumstances.



Is there any way to cut down on how much storage is taken up by the system?



enter image description here










share|improve this question

























  • "System" is a bit of a catchall category; you need something that'll give more details about where all that space is going. See this previous question, and this similar one on apple.se.

    – Gordon Davisson
    Oct 19 '16 at 4:45














14












14








14


3






MacOS Sierra has a helpful "Manage Storage" option in "About this Mac".



I noticed that my Mac uses 152 gigs of storage just for "system". I'm wondering if that's normal, because it seems outrageously high to me. I would imagine the OS would take up, certainly less than 100 gigs under normal circumstances.



Is there any way to cut down on how much storage is taken up by the system?



enter image description here










share|improve this question
















MacOS Sierra has a helpful "Manage Storage" option in "About this Mac".



I noticed that my Mac uses 152 gigs of storage just for "system". I'm wondering if that's normal, because it seems outrageously high to me. I would imagine the OS would take up, certainly less than 100 gigs under normal circumstances.



Is there any way to cut down on how much storage is taken up by the system?



enter image description here







macos mac disk-space disk-cleanup






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 17 '16 at 23:55







user345866

















asked Oct 17 '16 at 23:45









johncorserjohncorser

2922414




2922414













  • "System" is a bit of a catchall category; you need something that'll give more details about where all that space is going. See this previous question, and this similar one on apple.se.

    – Gordon Davisson
    Oct 19 '16 at 4:45



















  • "System" is a bit of a catchall category; you need something that'll give more details about where all that space is going. See this previous question, and this similar one on apple.se.

    – Gordon Davisson
    Oct 19 '16 at 4:45

















"System" is a bit of a catchall category; you need something that'll give more details about where all that space is going. See this previous question, and this similar one on apple.se.

– Gordon Davisson
Oct 19 '16 at 4:45





"System" is a bit of a catchall category; you need something that'll give more details about where all that space is going. See this previous question, and this similar one on apple.se.

– Gordon Davisson
Oct 19 '16 at 4:45










5 Answers
5






active

oldest

votes


















9














If you are on High Sierra then… it's TimeMachine fault.



That's the solution that worked for me.



Type this command in you terminal:



sudo tmutil listlocalsnapshots /


to check the snapshots of TimeMachine. You get some strings like these:



com.apple.TimeMachine.2017-10-02-132639
com.apple.TimeMachine.2017-10-02-175507
com.apple.TimeMachine.2017-10-02-200417
com.apple.TimeMachine.2017-10-02-235853
com.apple.TimeMachine.2017-10-03-112713
com.apple.TimeMachine.2017-10-03-112934
com.apple.TimeMachine.2017-10-03-113254


You need this command to delete TimeMachine mess:



tmutil deletelocalsnapshots 2017-09-27-112934


Type this command for each of those snapshots (changing the date) and you'll get a great amount of free space!






share|improve this answer


























  • will these get deleted once I let time-machine sync with my harddrive again? Or does timemachine fail to delete these snapshots in general? In other words, I am a bit scared, that deleting these via terminal will screw with my backups. Or does this have no effect?

    – CrazyQwert
    Mar 27 '18 at 8:19











  • They are just snapshots of your system waiting to get uploaded in your TM disk. Every time you move/save files on your mac, TM will takes snapshots. IMO this is just an old bug. I think that they fixed it already, so just delete the older snapshots and run TM backup after that.

    – Lorenzo Andraghetti
    Mar 28 '18 at 12:53











  • Am on High Sierra with about 60GB worth of system files. I did not have any Time Machine snapshots cluttering up my drive.

    – Pieter
    Mar 30 '18 at 16:02





















1














I'm not entirely sure what Apple considers to be "System". Mine is using about 40GB. Apple's calculator seems a bit unclear and I'm unable to find an explanation of what is included in that breakdown. Here is my actual system usage:



enter image description here



I would suggest using a better application that does not use a generic breakdown, but will show you which large files are taking up so much space, perhaps something like Disk Inventory X.






share|improve this answer































    1














    I believe that when I got my MBP, the size was around 16 GB.



    One night the size of the 'System' section of my storage increased 40 GB in an hour (though, I am running the High Sierra Beta). I restarted a few times and nothing seemed to happen. I read an answer somewhere to an issue related to this that I could delete the com.apple.coresymbolicationd folder in /System/Library/Caches/. The system couldn't read the size of the directory so I figured it was a problem folder, so I deleted it, emptied the garbage, and restarted. Now my System section is 50 GB (used to be 120 GB).



    Disk Inventory X gave me different sizes than the System Information window and it didn't find any problematically large files. Daisy Disk, however, did find a glob of ~75 GB that it couldn't scan because of permissions, even when scanning as admin. The com.apple.coresymbolicationd directory has restrictive permissions, so I assume that was the culprit.



    Deleting that directory isn't harmful to the system as far as I know, and it regenerates when the OS needs it again.



    You can also look at the built in Disk Utility. That gave me conflicting reports each restart but did inform me on one restart that ~100 GB of data was purgeable.






    share|improve this answer



















    • 2





      You can run this to see how big that folder is: sudo du -sh /System/Library/Caches/com.apple.coresymbolicationd

      – Paul Irish
      Aug 17 '18 at 23:33











    • Far warning, DaisyDisk trial will let you queue up files but requires a full license ($10) to actually delete them.

      – Samy Bencherif
      Dec 2 '18 at 6:12



















    1














    I had the same problem. My System folder was 50 GB, my Applications folder was 20 GB, and my Downloads, Music, etc accounted for about 20 GB. And my "About this Mac" was showing "System" space used as 160 GB, thus showing that there was no disk space any more on my 256 GB mac.



    So I spent some time found where this "160 GB" was being used. In the Users/<user>/Library folder, one of my application had created a directory and was storing some files over there which accounted for majority of the 160 GB. I removed that application and deleted this folder which resolved my problem.



    Note that deleting anything in a system folder can be harmful, so only do it if you know w






    share|improve this answer































      0














      Mainly, abnormal "system" size in macos is all about this path /private/var/folders/w3. Its some kind of system temporary folder, in which you can find xcode publishing archives of different versions(if you use xcode) and lots of data, that could be restored when needed.



      Also you can clear the data, which is marked in storage preferences as Purgeable Data this way:




      • list your volumes by
        df -h

      • run secureErase for system volume by
        sudo diskutil secureErase freespace 0 /dev/disk1s1


      Also delete unused simulator images in xcode/window/devices and simulators/simulators, you can easily install them again when needed from Xcode/Preferences/Components, and clear this folder /Users/your_user/Library/Developer/Xcode/iOS DeviceSupport
      This folder expands each time when new device connected, and could be easily erased.






      share|improve this answer








      New contributor




      rustem.russia is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





















        Your Answer








        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "3"
        };
        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%2fsuperuser.com%2fquestions%2f1136012%2fhow-much-storage-should-be-taken-up-by-system-in-macos-sierra%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        5 Answers
        5






        active

        oldest

        votes








        5 Answers
        5






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        9














        If you are on High Sierra then… it's TimeMachine fault.



        That's the solution that worked for me.



        Type this command in you terminal:



        sudo tmutil listlocalsnapshots /


        to check the snapshots of TimeMachine. You get some strings like these:



        com.apple.TimeMachine.2017-10-02-132639
        com.apple.TimeMachine.2017-10-02-175507
        com.apple.TimeMachine.2017-10-02-200417
        com.apple.TimeMachine.2017-10-02-235853
        com.apple.TimeMachine.2017-10-03-112713
        com.apple.TimeMachine.2017-10-03-112934
        com.apple.TimeMachine.2017-10-03-113254


        You need this command to delete TimeMachine mess:



        tmutil deletelocalsnapshots 2017-09-27-112934


        Type this command for each of those snapshots (changing the date) and you'll get a great amount of free space!






        share|improve this answer


























        • will these get deleted once I let time-machine sync with my harddrive again? Or does timemachine fail to delete these snapshots in general? In other words, I am a bit scared, that deleting these via terminal will screw with my backups. Or does this have no effect?

          – CrazyQwert
          Mar 27 '18 at 8:19











        • They are just snapshots of your system waiting to get uploaded in your TM disk. Every time you move/save files on your mac, TM will takes snapshots. IMO this is just an old bug. I think that they fixed it already, so just delete the older snapshots and run TM backup after that.

          – Lorenzo Andraghetti
          Mar 28 '18 at 12:53











        • Am on High Sierra with about 60GB worth of system files. I did not have any Time Machine snapshots cluttering up my drive.

          – Pieter
          Mar 30 '18 at 16:02


















        9














        If you are on High Sierra then… it's TimeMachine fault.



        That's the solution that worked for me.



        Type this command in you terminal:



        sudo tmutil listlocalsnapshots /


        to check the snapshots of TimeMachine. You get some strings like these:



        com.apple.TimeMachine.2017-10-02-132639
        com.apple.TimeMachine.2017-10-02-175507
        com.apple.TimeMachine.2017-10-02-200417
        com.apple.TimeMachine.2017-10-02-235853
        com.apple.TimeMachine.2017-10-03-112713
        com.apple.TimeMachine.2017-10-03-112934
        com.apple.TimeMachine.2017-10-03-113254


        You need this command to delete TimeMachine mess:



        tmutil deletelocalsnapshots 2017-09-27-112934


        Type this command for each of those snapshots (changing the date) and you'll get a great amount of free space!






        share|improve this answer


























        • will these get deleted once I let time-machine sync with my harddrive again? Or does timemachine fail to delete these snapshots in general? In other words, I am a bit scared, that deleting these via terminal will screw with my backups. Or does this have no effect?

          – CrazyQwert
          Mar 27 '18 at 8:19











        • They are just snapshots of your system waiting to get uploaded in your TM disk. Every time you move/save files on your mac, TM will takes snapshots. IMO this is just an old bug. I think that they fixed it already, so just delete the older snapshots and run TM backup after that.

          – Lorenzo Andraghetti
          Mar 28 '18 at 12:53











        • Am on High Sierra with about 60GB worth of system files. I did not have any Time Machine snapshots cluttering up my drive.

          – Pieter
          Mar 30 '18 at 16:02
















        9












        9








        9







        If you are on High Sierra then… it's TimeMachine fault.



        That's the solution that worked for me.



        Type this command in you terminal:



        sudo tmutil listlocalsnapshots /


        to check the snapshots of TimeMachine. You get some strings like these:



        com.apple.TimeMachine.2017-10-02-132639
        com.apple.TimeMachine.2017-10-02-175507
        com.apple.TimeMachine.2017-10-02-200417
        com.apple.TimeMachine.2017-10-02-235853
        com.apple.TimeMachine.2017-10-03-112713
        com.apple.TimeMachine.2017-10-03-112934
        com.apple.TimeMachine.2017-10-03-113254


        You need this command to delete TimeMachine mess:



        tmutil deletelocalsnapshots 2017-09-27-112934


        Type this command for each of those snapshots (changing the date) and you'll get a great amount of free space!






        share|improve this answer















        If you are on High Sierra then… it's TimeMachine fault.



        That's the solution that worked for me.



        Type this command in you terminal:



        sudo tmutil listlocalsnapshots /


        to check the snapshots of TimeMachine. You get some strings like these:



        com.apple.TimeMachine.2017-10-02-132639
        com.apple.TimeMachine.2017-10-02-175507
        com.apple.TimeMachine.2017-10-02-200417
        com.apple.TimeMachine.2017-10-02-235853
        com.apple.TimeMachine.2017-10-03-112713
        com.apple.TimeMachine.2017-10-03-112934
        com.apple.TimeMachine.2017-10-03-113254


        You need this command to delete TimeMachine mess:



        tmutil deletelocalsnapshots 2017-09-27-112934


        Type this command for each of those snapshots (changing the date) and you'll get a great amount of free space!







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Mar 28 '18 at 9:07

























        answered Oct 3 '17 at 9:49









        Lorenzo AndraghettiLorenzo Andraghetti

        9114




        9114













        • will these get deleted once I let time-machine sync with my harddrive again? Or does timemachine fail to delete these snapshots in general? In other words, I am a bit scared, that deleting these via terminal will screw with my backups. Or does this have no effect?

          – CrazyQwert
          Mar 27 '18 at 8:19











        • They are just snapshots of your system waiting to get uploaded in your TM disk. Every time you move/save files on your mac, TM will takes snapshots. IMO this is just an old bug. I think that they fixed it already, so just delete the older snapshots and run TM backup after that.

          – Lorenzo Andraghetti
          Mar 28 '18 at 12:53











        • Am on High Sierra with about 60GB worth of system files. I did not have any Time Machine snapshots cluttering up my drive.

          – Pieter
          Mar 30 '18 at 16:02





















        • will these get deleted once I let time-machine sync with my harddrive again? Or does timemachine fail to delete these snapshots in general? In other words, I am a bit scared, that deleting these via terminal will screw with my backups. Or does this have no effect?

          – CrazyQwert
          Mar 27 '18 at 8:19











        • They are just snapshots of your system waiting to get uploaded in your TM disk. Every time you move/save files on your mac, TM will takes snapshots. IMO this is just an old bug. I think that they fixed it already, so just delete the older snapshots and run TM backup after that.

          – Lorenzo Andraghetti
          Mar 28 '18 at 12:53











        • Am on High Sierra with about 60GB worth of system files. I did not have any Time Machine snapshots cluttering up my drive.

          – Pieter
          Mar 30 '18 at 16:02



















        will these get deleted once I let time-machine sync with my harddrive again? Or does timemachine fail to delete these snapshots in general? In other words, I am a bit scared, that deleting these via terminal will screw with my backups. Or does this have no effect?

        – CrazyQwert
        Mar 27 '18 at 8:19





        will these get deleted once I let time-machine sync with my harddrive again? Or does timemachine fail to delete these snapshots in general? In other words, I am a bit scared, that deleting these via terminal will screw with my backups. Or does this have no effect?

        – CrazyQwert
        Mar 27 '18 at 8:19













        They are just snapshots of your system waiting to get uploaded in your TM disk. Every time you move/save files on your mac, TM will takes snapshots. IMO this is just an old bug. I think that they fixed it already, so just delete the older snapshots and run TM backup after that.

        – Lorenzo Andraghetti
        Mar 28 '18 at 12:53





        They are just snapshots of your system waiting to get uploaded in your TM disk. Every time you move/save files on your mac, TM will takes snapshots. IMO this is just an old bug. I think that they fixed it already, so just delete the older snapshots and run TM backup after that.

        – Lorenzo Andraghetti
        Mar 28 '18 at 12:53













        Am on High Sierra with about 60GB worth of system files. I did not have any Time Machine snapshots cluttering up my drive.

        – Pieter
        Mar 30 '18 at 16:02







        Am on High Sierra with about 60GB worth of system files. I did not have any Time Machine snapshots cluttering up my drive.

        – Pieter
        Mar 30 '18 at 16:02















        1














        I'm not entirely sure what Apple considers to be "System". Mine is using about 40GB. Apple's calculator seems a bit unclear and I'm unable to find an explanation of what is included in that breakdown. Here is my actual system usage:



        enter image description here



        I would suggest using a better application that does not use a generic breakdown, but will show you which large files are taking up so much space, perhaps something like Disk Inventory X.






        share|improve this answer




























          1














          I'm not entirely sure what Apple considers to be "System". Mine is using about 40GB. Apple's calculator seems a bit unclear and I'm unable to find an explanation of what is included in that breakdown. Here is my actual system usage:



          enter image description here



          I would suggest using a better application that does not use a generic breakdown, but will show you which large files are taking up so much space, perhaps something like Disk Inventory X.






          share|improve this answer


























            1












            1








            1







            I'm not entirely sure what Apple considers to be "System". Mine is using about 40GB. Apple's calculator seems a bit unclear and I'm unable to find an explanation of what is included in that breakdown. Here is my actual system usage:



            enter image description here



            I would suggest using a better application that does not use a generic breakdown, but will show you which large files are taking up so much space, perhaps something like Disk Inventory X.






            share|improve this answer













            I'm not entirely sure what Apple considers to be "System". Mine is using about 40GB. Apple's calculator seems a bit unclear and I'm unable to find an explanation of what is included in that breakdown. Here is my actual system usage:



            enter image description here



            I would suggest using a better application that does not use a generic breakdown, but will show you which large files are taking up so much space, perhaps something like Disk Inventory X.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Oct 22 '16 at 17:28









            Simon SheehanSimon Sheehan

            7,745124269




            7,745124269























                1














                I believe that when I got my MBP, the size was around 16 GB.



                One night the size of the 'System' section of my storage increased 40 GB in an hour (though, I am running the High Sierra Beta). I restarted a few times and nothing seemed to happen. I read an answer somewhere to an issue related to this that I could delete the com.apple.coresymbolicationd folder in /System/Library/Caches/. The system couldn't read the size of the directory so I figured it was a problem folder, so I deleted it, emptied the garbage, and restarted. Now my System section is 50 GB (used to be 120 GB).



                Disk Inventory X gave me different sizes than the System Information window and it didn't find any problematically large files. Daisy Disk, however, did find a glob of ~75 GB that it couldn't scan because of permissions, even when scanning as admin. The com.apple.coresymbolicationd directory has restrictive permissions, so I assume that was the culprit.



                Deleting that directory isn't harmful to the system as far as I know, and it regenerates when the OS needs it again.



                You can also look at the built in Disk Utility. That gave me conflicting reports each restart but did inform me on one restart that ~100 GB of data was purgeable.






                share|improve this answer



















                • 2





                  You can run this to see how big that folder is: sudo du -sh /System/Library/Caches/com.apple.coresymbolicationd

                  – Paul Irish
                  Aug 17 '18 at 23:33











                • Far warning, DaisyDisk trial will let you queue up files but requires a full license ($10) to actually delete them.

                  – Samy Bencherif
                  Dec 2 '18 at 6:12
















                1














                I believe that when I got my MBP, the size was around 16 GB.



                One night the size of the 'System' section of my storage increased 40 GB in an hour (though, I am running the High Sierra Beta). I restarted a few times and nothing seemed to happen. I read an answer somewhere to an issue related to this that I could delete the com.apple.coresymbolicationd folder in /System/Library/Caches/. The system couldn't read the size of the directory so I figured it was a problem folder, so I deleted it, emptied the garbage, and restarted. Now my System section is 50 GB (used to be 120 GB).



                Disk Inventory X gave me different sizes than the System Information window and it didn't find any problematically large files. Daisy Disk, however, did find a glob of ~75 GB that it couldn't scan because of permissions, even when scanning as admin. The com.apple.coresymbolicationd directory has restrictive permissions, so I assume that was the culprit.



                Deleting that directory isn't harmful to the system as far as I know, and it regenerates when the OS needs it again.



                You can also look at the built in Disk Utility. That gave me conflicting reports each restart but did inform me on one restart that ~100 GB of data was purgeable.






                share|improve this answer



















                • 2





                  You can run this to see how big that folder is: sudo du -sh /System/Library/Caches/com.apple.coresymbolicationd

                  – Paul Irish
                  Aug 17 '18 at 23:33











                • Far warning, DaisyDisk trial will let you queue up files but requires a full license ($10) to actually delete them.

                  – Samy Bencherif
                  Dec 2 '18 at 6:12














                1












                1








                1







                I believe that when I got my MBP, the size was around 16 GB.



                One night the size of the 'System' section of my storage increased 40 GB in an hour (though, I am running the High Sierra Beta). I restarted a few times and nothing seemed to happen. I read an answer somewhere to an issue related to this that I could delete the com.apple.coresymbolicationd folder in /System/Library/Caches/. The system couldn't read the size of the directory so I figured it was a problem folder, so I deleted it, emptied the garbage, and restarted. Now my System section is 50 GB (used to be 120 GB).



                Disk Inventory X gave me different sizes than the System Information window and it didn't find any problematically large files. Daisy Disk, however, did find a glob of ~75 GB that it couldn't scan because of permissions, even when scanning as admin. The com.apple.coresymbolicationd directory has restrictive permissions, so I assume that was the culprit.



                Deleting that directory isn't harmful to the system as far as I know, and it regenerates when the OS needs it again.



                You can also look at the built in Disk Utility. That gave me conflicting reports each restart but did inform me on one restart that ~100 GB of data was purgeable.






                share|improve this answer













                I believe that when I got my MBP, the size was around 16 GB.



                One night the size of the 'System' section of my storage increased 40 GB in an hour (though, I am running the High Sierra Beta). I restarted a few times and nothing seemed to happen. I read an answer somewhere to an issue related to this that I could delete the com.apple.coresymbolicationd folder in /System/Library/Caches/. The system couldn't read the size of the directory so I figured it was a problem folder, so I deleted it, emptied the garbage, and restarted. Now my System section is 50 GB (used to be 120 GB).



                Disk Inventory X gave me different sizes than the System Information window and it didn't find any problematically large files. Daisy Disk, however, did find a glob of ~75 GB that it couldn't scan because of permissions, even when scanning as admin. The com.apple.coresymbolicationd directory has restrictive permissions, so I assume that was the culprit.



                Deleting that directory isn't harmful to the system as far as I know, and it regenerates when the OS needs it again.



                You can also look at the built in Disk Utility. That gave me conflicting reports each restart but did inform me on one restart that ~100 GB of data was purgeable.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Sep 9 '17 at 20:21









                M. DavisM. Davis

                1113




                1113








                • 2





                  You can run this to see how big that folder is: sudo du -sh /System/Library/Caches/com.apple.coresymbolicationd

                  – Paul Irish
                  Aug 17 '18 at 23:33











                • Far warning, DaisyDisk trial will let you queue up files but requires a full license ($10) to actually delete them.

                  – Samy Bencherif
                  Dec 2 '18 at 6:12














                • 2





                  You can run this to see how big that folder is: sudo du -sh /System/Library/Caches/com.apple.coresymbolicationd

                  – Paul Irish
                  Aug 17 '18 at 23:33











                • Far warning, DaisyDisk trial will let you queue up files but requires a full license ($10) to actually delete them.

                  – Samy Bencherif
                  Dec 2 '18 at 6:12








                2




                2





                You can run this to see how big that folder is: sudo du -sh /System/Library/Caches/com.apple.coresymbolicationd

                – Paul Irish
                Aug 17 '18 at 23:33





                You can run this to see how big that folder is: sudo du -sh /System/Library/Caches/com.apple.coresymbolicationd

                – Paul Irish
                Aug 17 '18 at 23:33













                Far warning, DaisyDisk trial will let you queue up files but requires a full license ($10) to actually delete them.

                – Samy Bencherif
                Dec 2 '18 at 6:12





                Far warning, DaisyDisk trial will let you queue up files but requires a full license ($10) to actually delete them.

                – Samy Bencherif
                Dec 2 '18 at 6:12











                1














                I had the same problem. My System folder was 50 GB, my Applications folder was 20 GB, and my Downloads, Music, etc accounted for about 20 GB. And my "About this Mac" was showing "System" space used as 160 GB, thus showing that there was no disk space any more on my 256 GB mac.



                So I spent some time found where this "160 GB" was being used. In the Users/<user>/Library folder, one of my application had created a directory and was storing some files over there which accounted for majority of the 160 GB. I removed that application and deleted this folder which resolved my problem.



                Note that deleting anything in a system folder can be harmful, so only do it if you know w






                share|improve this answer




























                  1














                  I had the same problem. My System folder was 50 GB, my Applications folder was 20 GB, and my Downloads, Music, etc accounted for about 20 GB. And my "About this Mac" was showing "System" space used as 160 GB, thus showing that there was no disk space any more on my 256 GB mac.



                  So I spent some time found where this "160 GB" was being used. In the Users/<user>/Library folder, one of my application had created a directory and was storing some files over there which accounted for majority of the 160 GB. I removed that application and deleted this folder which resolved my problem.



                  Note that deleting anything in a system folder can be harmful, so only do it if you know w






                  share|improve this answer


























                    1












                    1








                    1







                    I had the same problem. My System folder was 50 GB, my Applications folder was 20 GB, and my Downloads, Music, etc accounted for about 20 GB. And my "About this Mac" was showing "System" space used as 160 GB, thus showing that there was no disk space any more on my 256 GB mac.



                    So I spent some time found where this "160 GB" was being used. In the Users/<user>/Library folder, one of my application had created a directory and was storing some files over there which accounted for majority of the 160 GB. I removed that application and deleted this folder which resolved my problem.



                    Note that deleting anything in a system folder can be harmful, so only do it if you know w






                    share|improve this answer













                    I had the same problem. My System folder was 50 GB, my Applications folder was 20 GB, and my Downloads, Music, etc accounted for about 20 GB. And my "About this Mac" was showing "System" space used as 160 GB, thus showing that there was no disk space any more on my 256 GB mac.



                    So I spent some time found where this "160 GB" was being used. In the Users/<user>/Library folder, one of my application had created a directory and was storing some files over there which accounted for majority of the 160 GB. I removed that application and deleted this folder which resolved my problem.



                    Note that deleting anything in a system folder can be harmful, so only do it if you know w







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Jan 27 '18 at 23:06









                    rgamberrgamber

                    1112




                    1112























                        0














                        Mainly, abnormal "system" size in macos is all about this path /private/var/folders/w3. Its some kind of system temporary folder, in which you can find xcode publishing archives of different versions(if you use xcode) and lots of data, that could be restored when needed.



                        Also you can clear the data, which is marked in storage preferences as Purgeable Data this way:




                        • list your volumes by
                          df -h

                        • run secureErase for system volume by
                          sudo diskutil secureErase freespace 0 /dev/disk1s1


                        Also delete unused simulator images in xcode/window/devices and simulators/simulators, you can easily install them again when needed from Xcode/Preferences/Components, and clear this folder /Users/your_user/Library/Developer/Xcode/iOS DeviceSupport
                        This folder expands each time when new device connected, and could be easily erased.






                        share|improve this answer








                        New contributor




                        rustem.russia is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                        Check out our Code of Conduct.

























                          0














                          Mainly, abnormal "system" size in macos is all about this path /private/var/folders/w3. Its some kind of system temporary folder, in which you can find xcode publishing archives of different versions(if you use xcode) and lots of data, that could be restored when needed.



                          Also you can clear the data, which is marked in storage preferences as Purgeable Data this way:




                          • list your volumes by
                            df -h

                          • run secureErase for system volume by
                            sudo diskutil secureErase freespace 0 /dev/disk1s1


                          Also delete unused simulator images in xcode/window/devices and simulators/simulators, you can easily install them again when needed from Xcode/Preferences/Components, and clear this folder /Users/your_user/Library/Developer/Xcode/iOS DeviceSupport
                          This folder expands each time when new device connected, and could be easily erased.






                          share|improve this answer








                          New contributor




                          rustem.russia is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.























                            0












                            0








                            0







                            Mainly, abnormal "system" size in macos is all about this path /private/var/folders/w3. Its some kind of system temporary folder, in which you can find xcode publishing archives of different versions(if you use xcode) and lots of data, that could be restored when needed.



                            Also you can clear the data, which is marked in storage preferences as Purgeable Data this way:




                            • list your volumes by
                              df -h

                            • run secureErase for system volume by
                              sudo diskutil secureErase freespace 0 /dev/disk1s1


                            Also delete unused simulator images in xcode/window/devices and simulators/simulators, you can easily install them again when needed from Xcode/Preferences/Components, and clear this folder /Users/your_user/Library/Developer/Xcode/iOS DeviceSupport
                            This folder expands each time when new device connected, and could be easily erased.






                            share|improve this answer








                            New contributor




                            rustem.russia is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.










                            Mainly, abnormal "system" size in macos is all about this path /private/var/folders/w3. Its some kind of system temporary folder, in which you can find xcode publishing archives of different versions(if you use xcode) and lots of data, that could be restored when needed.



                            Also you can clear the data, which is marked in storage preferences as Purgeable Data this way:




                            • list your volumes by
                              df -h

                            • run secureErase for system volume by
                              sudo diskutil secureErase freespace 0 /dev/disk1s1


                            Also delete unused simulator images in xcode/window/devices and simulators/simulators, you can easily install them again when needed from Xcode/Preferences/Components, and clear this folder /Users/your_user/Library/Developer/Xcode/iOS DeviceSupport
                            This folder expands each time when new device connected, and could be easily erased.







                            share|improve this answer








                            New contributor




                            rustem.russia is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            share|improve this answer



                            share|improve this answer






                            New contributor




                            rustem.russia is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.









                            answered yesterday









                            rustem.russiarustem.russia

                            101




                            101




                            New contributor




                            rustem.russia is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.





                            New contributor





                            rustem.russia is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






                            rustem.russia is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                            Check out our Code of Conduct.






























                                draft saved

                                draft discarded




















































                                Thanks for contributing an answer to Super User!


                                • 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%2fsuperuser.com%2fquestions%2f1136012%2fhow-much-storage-should-be-taken-up-by-system-in-macos-sierra%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

                                Couldn't open a raw socket. Error: Permission denied (13) (nmap)Is it possible to run networking commands...

                                VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

                                Why not use the yoke to control yaw, as well as pitch and roll? Announcing the arrival of...