Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a web server running Windows Server 2008 R2 Enterprise. It's C:\ drive is 100 GB in size.

We started getting errors from IIS and discovered that the C:\ drive, surprisingly so, was reported to be full. This is where it gets strange: I changed folder options to show hidden files and protected system files, and then did a right click/Properties on everything on C:\ to see the cumulative size, which is only 13.7 GB (more in line of what is usually on that server).

  • The recycle bin is empty
  • There is no page file on C:\ (explicitly turned off)
  • vssadmin list shadows showed no shadows ("No items found that satisfy the query").
  • No BitLocker

Chkdsk results:

104754175 KB total disk space.
100648156 KB in 62945 files.
    46616 KB in 16972 indexes.
        0 KB in bad sectors.
   151415 KB in use by the system.
    65536 KB occupied by the log file.
  3907988 KB available on disk. (note: this is after I cleared about 4GB)

Where are the remaining 86.3 GB that are supposedly on that disk?

Answer (also below): WinDirStat helped identify C:\Windows\Temp\php53_errors.log as the culprit. Unfortunately it was impossible to identify this with regular tools. Thanks to everyone who helped point me to the tool!

share|improve this question
    
Could be a corrupted disk....have you done a chkdsk c: /f to see if this cleans things up ... reboot will of course be needed. –  mdpc Dec 17 '12 at 23:10
3  
You might try windirstat to see what it shows. It sometimes provides insight into where space is going. –  Robert Dec 17 '12 at 23:14
    
I did a regular chkdsk (no /f) and it said that no problems were found. I'm going to post the chkdsk results in the question. –  AX1 Dec 17 '12 at 23:14
    
+1 for running WinDirStat, it should show you everything. –  Brent Pabst Dec 17 '12 at 23:24
    
I've seen this type of weirdness related to volume shadow copies. Check with vssadmin list shadows. –  floyd Dec 17 '12 at 23:28

2 Answers 2

WinDirStat indeed solved the mystery. Thanks to Robert, Brent, and user72593!

The main file that ate up all the space was C:\Windows\Temp\php53_errors.log - at a massive 84.7 GB size. Not sure what all those errors are; we run Wordpress/PHP on this server, so it must come from there. Also not sure why a right click/Properties on C:\Windows doesn't report anything in the Temp folder, that's pretty stupid.

P.S.: Seems like I'm not the only one with a massive php53_errors.log file: http://stackoverflow.com/questions/13540489

share|improve this answer
    
Glad you've got it sorted ! –  user72593 Dec 17 '12 at 23:50

Assuming you're not running BitLocker which has been known to cause issues like this, I would run vssadmin to see if you have shadow copy chewing up space from failed backups, do you run some backup softeare? If neither of those apply then sounds like you have some partition corruption (if WinDirStat also shows the partition to have ample free space) I would run a repair of the partition by right-clicking on the drive letter, going to properties and tools and choosing the repair option so see if that corrects things.

share|improve this answer
    
Not running BitLocker. I've run vssadmin list shadows, which came back with "No items found that satisfy this query." –  AX1 Dec 17 '12 at 23:35
    
Have you already run WinDirStat or TreeSize or any similar application that would look inside your System Volume Information and other system folder to account for ALL the files? TreeSize can catalog things pretty quickly and tell you if there is actual data somewhere. –  user72593 Dec 17 '12 at 23:41
    
Running WinDirStat now! Will report what I find. –  AX1 Dec 17 '12 at 23:41

protected by Community Jul 3 '13 at 9:28

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.