Tag Info

New answers tagged

0

This is an interesting problem. My suspicion here is that this is some artifact from the physical system that got virtualized, but is undetectable because whatever physical cause is no longer present. Two examples could be: bad blocks on the physical drive that VMware Converter was able to recognize and get around but now the bad blocks are part of the ...


1

Did you try running spacesniffer as administrator like HopelessN00b suggests in the comments to your question? Usually, the big unknowns clear up and probably, you will find that the C:\Windows\WinSxS is the culprit. This is where Windows keeps different versions of .DLL files in an attempt to avoid the DLL hell of olden times. You can clean it up somewhat ...


3

It's the OST files... the locally cached copy of the emails and calendar events and such that Outlook downloads from the Exchange server. You want to disable cached mode and prevent Outlook from creating an OST file, though why you'd do this instead of just using OWA (Outlook Web App/"Exchange Webmail") is beyond me. Both settings are controllable by GPO ...


9

From what you describe, the main problem is that they decided to use a RAID5 for such a large array, which is quite a bad choice for this setup, for exactly the reason you experience: Having a 2nd disk fail during the recovery breaks everything, and this second failure is all too likely to take that risk. If they had used e.g. a RAID6 instead, having a ...


1

Are the files still open? That would explain the space not being reclaimed. You may want to use lsof to check which process has your unlinked files open.


0

A little less known but worth mentioning: Windows Update stores the updates it downloads in C:\Windows\SoftwareDistribution\Download; and they are not deleted after having been installed, thus the folder can grow to be quite large over time. After new updates are installed, you can safely empty that folder and reclaim some disk space.


1

In the interest of preserving the information in case the TechNet article moves, here is how to "activate" the Microsoft disk cleanup utility on server 2008 or 2008 R2: Windows Server 2008 R2 64-bit C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe Windows Server 2008 R2 ...


1

Sometimes damaged file system can do effects like it - for example when directory /tmp is damaged. Or - when there is to much files. For "quick" fix: mv /tmp /tmp.xxx mkdir /tmp chmod a+rwxt /tmp If that help - try reboot system and fsck root file system. If it's ok - just remove /tmp.xxx directory. Another possibility is - when /tmp is "other" ...



Top 50 recent answers are included