locked
Why is WHS reserving so much space for System - 216GB RRS feed

  • Question

  • I have a homebuilt WHS that has worked fine...mostly.

    Today I was poking around and noticed that in the disk manager screen in the Admin console that WHS has reserve 216 gig for system. That seems like an awful lot.

    Any ideas?

    Thanks in Advance
    Wednesday, March 3, 2010 1:16 AM

Answers

  • I have the same problem, except that I have 1.2TB assigned to "system" (the server has 4x 1TB disks), which I cant account for at all with TreeSize.
    I've started migrating all my data to new shares using SMB, and while the copies are going on the allocation may fluctuate between 1TB and 1.3TB, but it always returns back to 1.2TB after the data move.
    Are there any tools I can run to get more detail or repair this? Otherwise i'll have to migrate all my data off the system and install it from scratch, which I really dont want to have to do.
    I've run a scandisk on D:\, but that didnt find any problems.

    http://imgur.com/DJUBx.png
    http://imgur.com/ZGHRW.png
    http://i.imgur.com/cbs2n.png

    Edit: I've finally found the cause of the disk usage by manually looking through C:\fs\*.
    I had been using DriveBalancer to fix issues with disk 0 and 1 being horribly over-filled, and it apparently left a bunch of empty files behind in the \fake\ folders when it didnt exit cleanly.
     
    Wednesday, March 3, 2010 4:52 AM

All replies

  • I have a homebuilt WHS that has worked fine...mostly.

    Today I was poking around and noticed that in the disk manager screen in the Admin console that WHS has reserve 216 gig for system. That seems like an awful lot.

    Any ideas?

    Thanks in Advance
    The system portion of the pie chart in the Console is a "catch-all" for anything that doesn't fall in the other categories (Shared Folders, Duplication, PC Backups and Free Space), or if you copied files to the server in an unsupported method (anything other than \\server\[sharename]).  Shadow Copies is one possibility.  If you downloaded some files on the server and saved them to D:\shares, that would also cause that.
    Wednesday, March 3, 2010 2:28 AM
    Moderator
  • I have the same problem, except that I have 1.2TB assigned to "system" (the server has 4x 1TB disks), which I cant account for at all with TreeSize.
    I've started migrating all my data to new shares using SMB, and while the copies are going on the allocation may fluctuate between 1TB and 1.3TB, but it always returns back to 1.2TB after the data move.
    Are there any tools I can run to get more detail or repair this? Otherwise i'll have to migrate all my data off the system and install it from scratch, which I really dont want to have to do.
    I've run a scandisk on D:\, but that didnt find any problems.

    http://imgur.com/DJUBx.png
    http://imgur.com/ZGHRW.png
    http://i.imgur.com/cbs2n.png

    Edit: I've finally found the cause of the disk usage by manually looking through C:\fs\*.
    I had been using DriveBalancer to fix issues with disk 0 and 1 being horribly over-filled, and it apparently left a bunch of empty files behind in the \fake\ folders when it didnt exit cleanly.
     
    Wednesday, March 3, 2010 4:52 AM
  • Since PP1 there is no need to use drive balancer.
    --
    Wednesday, March 3, 2010 10:26 AM
  • Except in cases where a system disk was filled pre-PP1 and then subsequently upgraded to PP1... files would never move off the system disk. :)

    (I know, probably a small cornercase now when we have systems already preinstalled with PP1)
    Wednesday, March 3, 2010 7:41 PM
  • The point is more that it doesn't really matter if files ever move off the system disk. In round numbers, 1 GB of free space on the D: partition will hold 250k tombstones...
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, March 3, 2010 9:20 PM
    Moderator