3/29/2024 0 Comments Windirstat command line– TreeSize free says that C:\Windows is 28.8 Gb, but “only” 23.1 Gb “allocated” – GDU says that my C:\Windows uses 29.2 Gb (which is WRONG) Any subsequent files that are hard linked to that original file get flagged as zero allocated space. The only limitation of WizTree is that when such hard link exist, it has to “grant” the disk usage to one of the “copies” (and count others as 0), and it is not “manageable” to define which one is privilegied :ġ) to be effective, WizTree has to be launched as admin, and on the drive itself (not on a directory a/o sub-directory)Ģ) the first instance of a file WizTree finds in the $MFT file gets the “allocated” space. This is in particular widely used by Windows files, a lot of them being defined once in C:\Windows\system32\… and once C:\Windows\winsxs\…. files defined several times in the structure, but sharing the same data, present only once on the disk. Why this difference : Because Wiztree (and only Wiztree) manages “hard links”, ie. At least on Windows, among the three tools mentioned here (TreeSize, WizTree and GDU) only ONE provides accurate view of disk usage….
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |