Situation as follows: I have a server with Windows Server 2003 installed and an additonal volume of 20GB total size. On the drive there are 9 files with 16,2 GB in size. Therefore 3,8GB should be free to use. But Explorer as well as Disk Management return a free size of only 736MB. I tried the following to find the root cause of the problem: - checked if there are hidden files etc. which use up the space => there are none - checked if shadow copies are stored on the volume => no shadow copies stored - made chkdsk of the drive to see if there are filesystem errors => no errors - looke at chkdsk output to see available KB on disk => returns the full 3898624KB - executed fsutil volume diskfree: Total # of free bytes : 772538368 Total # of bytes : 21466906624 Total # of avail free bytes : 772538368 - executed the Disk Usage tool from Systinterals: Du v1.34 - report directory disk usage Copyright (C) 2005-2009 Mark Russinovich Sysinternals - www.sysinternals.com Files: 11 Directories: 4 Size: 17,397,973,077 bytes Size on disk: 17,397,973,077 bytes Don't know why it reports 11 files and 17,3GB usage here. I also checked many of the other threads which already exists in MS forums, but could not come up with a solution to this problem. Would you be so kind to help me with this?

Check out Quota tab.MCITP: Enterprise Administrator; MCT; Microsoft Security Trusted Advisor

We have no quotas configured on all servers, hence quota management (right click on volume / Properties / Quota) on this specific server in general and volume in particular is also disabled.

Hi, As I understand that Windows Explorer reports different free disk space compared with CHKDSK report. Before going further, please collect the outputs of the following commands for further analysis: Fsutil fsinfo ntfsinfo c:>c:\fsutil.txt Dir c:\>>c:\dir.txt Chkdsk c:>>c:\chkdsk.txt Meanwhile, you can check the following locations in advance: 1. Click Administrative Tools, click Performance, click on Trace logs and see if you enable trace logs. If so, delete these trace logs. 2. Check if any USN journals on the volume, try to decrease the size of the reserved space that USN journal uses. To do this, take the following steps: 1) Open a command prompt, type the command : fsutil usn deletejournal /D VolumePathName Note: VolumePathName specifies the drive letter followed by a colon, the mount point, or the volume name. 2) Then type: fsutil usn createjournal m=0x800000 a=0x100000 VolumePathName 3. Please visit the following KB: FIX: The volume information is incorrectly displayed when you open the Disk Management snap-in in Windows Server 2003 Best Regards DalePlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

fsutil fsinfo ntfsinfo u:>c:\fsutil.txt NTFS Volume Serial Number : 0x94989d17989cf946 Version : 3.1 Number Sectors : 0x00000000027fc3b1 Total Clusters : 0x000000000004ff87 Free Clusters : 0x000000000000ee64 Total Reserved : 0x000000000000c088 Bytes Per Sector : 512 Bytes Per Cluster : 65536 Bytes Per FileRecord Segment : 1024 Clusters Per FileRecord Segment : 0 Mft Valid Data Length : 0x0000000000010000 Mft Start Lcn : 0x000000000000c000 Mft2 Start Lcn : 0x0000000000027fc3 Mft Zone Start : 0x000000000000c000 Mft Zone End : 0x0000000000016000 Dir u:\>>c:\dir.txt Volume in drive U is TempDB Volume Serial Number is 989C-F946 Directory of U:\ 11/11/2010 09:50 AM <DIR> Sqldata 0 File(s) 0 bytes 1 Dir(s) 769,392,640 bytes free Chkdsk u:>>c:\chkdsk.txt The type of the file system is NTFS. Volume label is TempDB. WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... 0 percent complete. (0 of 64 file records processed) 1 percent complete. (7 of 64 file records processed) 2 percent complete. (13 of 64 file records processed) 3 percent complete. (20 of 64 file records processed) 4 percent complete. (26 of 64 file records processed) 5 percent complete. (32 of 64 file records processed) 6 percent complete. (39 of 64 file records processed) 7 percent complete. (45 of 64 file records processed) 8 percent complete. (52 of 64 file records processed) 9 percent complete. (58 of 64 file records processed) 106464 64 file records processed. File verification completed. 1000 0 large file records processed. 1000 0 bad file records processed. 1000 0 EA records processed. 1000 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 12 percent complete. (6 of 171 index entries processed) 15 percent complete. (11 of 171 index entries processed) 18 percent complete. (17 of 171 index entries processed) 19 percent complete. (21 of 171 index entries processed) 20 percent complete. (22 of 171 index entries processed) 22 percent complete. (27 of 171 index entries processed) 25 percent complete. (32 of 171 index entries processed) 27 percent complete. (38 of 171 index entries processed) 30 percent complete. (43 of 171 index entries processed) 33 percent complete. (49 of 171 index entries processed) 35 percent complete. (55 of 171 index entries processed) 38 percent complete. (60 of 171 index entries processed) 39 percent complete. (62 of 171 index entries processed) 40 percent complete. (64 of 171 index entries processed) 41 percent complete. (66 of 171 index entries processed) 42 percent complete. (68 of 171 index entries processed) 43 percent complete. (70 of 171 index entries processed) 44 percent complete. (73 of 171 index entries processed) 45 percent complete. (75 of 171 index entries processed) 46 percent complete. (77 of 171 index entries processed) 47 percent complete. (79 of 171 index entries processed) 48 percent complete. (81 of 171 index entries processed) 49 percent complete. (83 of 171 index entries processed) 50 percent complete. (85 of 171 index entries processed) 51 percent complete. (87 of 171 index entries processed) 52 percent complete. (90 of 171 index entries processed) 53 percent complete. (92 of 171 index entries processed) 54 percent complete. (94 of 171 index entries processed) 55 percent complete. (96 of 171 index entries processed) 56 percent complete. (98 of 171 index entries processed) 57 percent complete. (100 of 171 index entries processed) 58 percent complete. (102 of 171 index entries processed) 59 percent complete. (104 of 171 index entries processed) 60 percent complete. (106 of 171 index entries processed) 61 percent complete. (109 of 171 index entries processed) 62 percent complete. (111 of 171 index entries processed) 63 percent complete. (113 of 171 index entries processed) 64 percent complete. (115 of 171 index entries processed) 65 percent complete. (117 of 171 index entries processed) 66 percent complete. (119 of 171 index entries processed) 67 percent complete. (121 of 171 index entries processed) 68 percent complete. (123 of 171 index entries processed) 69 percent complete. (126 of 171 index entries processed) 70 percent complete. (128 of 171 index entries processed) 71 percent complete. (130 of 171 index entries processed) 72 percent complete. (132 of 171 index entries processed) 73 percent complete. (134 of 171 index entries processed) 74 percent complete. (136 of 171 index entries processed) 75 percent complete. (138 of 171 index entries processed) 76 percent complete. (140 of 171 index entries processed) 77 percent complete. (143 of 171 index entries processed) 78 percent complete. (145 of 171 index entries processed) 79 percent complete. (147 of 171 index entries processed) 80 percent complete. (149 of 171 index entries processed) 81 percent complete. (151 of 171 index entries processed) 82 percent complete. (153 of 171 index entries processed) 83 percent complete. (155 of 171 index entries processed) 84 percent complete. (157 of 171 index entries processed) 85 percent complete. (159 of 171 index entries processed) 90171171 171 index entries processed. Index verification completed. 9155 5 unindexed files processed. CHKDSK is verifying security descriptors (stage 3 of 3)... 92 percent complete. (8 of 64 descriptors processed) 93 percent complete. (16 of 64 descriptors processed) 94 percent complete. (25 of 64 descriptors processed) 95 percent complete. (33 of 64 descriptors processed) 96 percent complete. (42 of 64 descriptors processed) 97 percent complete. (50 of 64 descriptors processed) 98 percent complete. (59 of 64 descriptors processed) 986464 64 security descriptors processed. Security descriptor verification completed. 1001111 11 data files processed. CHKDSK is verifying Usn Journal... 100176176 176 USN bytes processed. Usn Journal verification completed. 20963800 KB total disk space. 16990272 KB in 12 files. 256 KB in 12 indexes. 0 KB in bad sectors. 67480 KB in use by the system. 65536 KB occupied by the log file. 3905792 KB available on disk. 65536 bytes in each allocation unit. 327559 total allocation units on disk. 61028 allocation units available on disk. ad 1. There are no trace logs. ad 2. Deleted the USN journal which freed 8MB. Created journal again which allocated 12MB. ad 3. The conditions in the article do not apply to my case. Also this is a server with Windows Server 2003 SP2 which is the latest SP.

From the output of CHKDSK, FSUTIL, DIR commands, the FSUTIL and DIR shows the same free disk space of 736MB, but CHKDSK shows the free disk space of 3.8 GB. As I understand, Windows Explorer, the directory list command DIR and the volume list command FSUTIL displays the total file and folder statistics for only those files and folders you have permissions to access. However, those hidden files and protected operating system files are excluded. This behavior may cause Windows Explorer and DIR command to display inaccurate file and folder total size. To include these types of files, please visit the following KB to locate and correct disk space on NTFS volume. How to locate and correct disk space problems on NTFS volumes in Windows XP There are other factors that might cause disk space missing, such as hard links, VSS. Please visit the following blog for more information. NTFS Misreports Free Space? Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Tried everything from the two articles but could not find an explanation why the disk space is missing for Explorer and Dir. Is there anything else we can check?

In your original post, you said that the Windows Explorer shows 736 MB size as well as Disk Management. I am wondering how much disk space is shown in BIOS. BTW, as I mentioned in my previous reply, have you checked the VSS? Sometimes that the Microsoft Volume Shadow copy Service (VSS) snapshots doesn't get deleted automatically after the backup of Shadow Copy Components, the disk space will be occupied. Please follow the guide to check and clear VSS snapshots. How to purge the Microsoft Volume Shadow copy Service (VSS) snapshots if they do not get deleted automatically after the backup of Shadow Copy Components Please note: we provide the third party link for technical reference only. There may be some changes without notice, Microsoft doesn’t guarantee any accuracy on contacting information. However, this issue might be caused by old hard drive itself. It is recommended to run some third party tools to check hard drive status as well, you can contact the hard drive vendor for support too. Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

In my original post I already told that I've checked if shadow copies are stored on the volume and no shadow copies are stored. Additionally "vssadmin list shadowstorage" tells me that no shadow copies are stored. The drive is in fact a volume from our SAN, therefore hard drive status is OK.

I’m sorry for late reply. Some disk missing can be caused by virus infected, you may update the security software to perform a full scan. Additionally, you can use Disk Usage v1.33 to analyze the detail disk usage. There are also some similar issues for references: Windows 2008 - Disk Space Missing Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

How it works? Did you find the missing space? Please keep us update and it is really appreciated if you can share your solution with us. Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello, I would suggest you download Disk Usage tool from the Sysinternals site? http://technet.microsoft.com/en-us/sysinternals/bb545046.aspx Drop into a c:\tools folder then run it twice from an elevated CMD prompt: C:\Tools>du /v c:\ >Files.txt This should show all the folder sizes on the disk.Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en

Sorry for late reply, was occupied with other stuff. Output of DU: 88 U:\RECYCLER\S-1-5-21-1744685988-1532578421-1399303167-6959 88 U:\RECYCLER 16,990,208 U:\Sqldata 16,990,511 U:\ Totals: Files: 16 Directories: 4 Size: 17,398,283,356 bytes Size on disk: 17,398,283,356 bytes I already checked the thread mentioned by Dale for possible solutions to the problem, but could not find anything.

Check whether the virtual memory/page file is using the remaining space.

Page File is only on C:\ but not on this drive.