Calculate real directory size on HDD (no links)

[Nux]

With Windows 7 symlinks and hardlinks all over the place it's very hard to tell what the real size of the a given folder is. For example Windows directory seem to take a LOT of space while in fact there are many internal links doubling it's apparent size. I also have many links from SSD to other, bigger drives and it makes the job to optimize space even more difficult...

So the request is to be able to run dir size calculation (similar to cm_CountDirContent) omiting any hard/soft links and junctions.

[MVV]

You can open properties dialog to get Windows size w/o junctions.

But it is impossible to count size w/o hardlinks because every file hardlink is a usual file record. E.g. if file has 3 hardlinks, 2 under Windows and third under Program Files, it is a big question where to count its size because all 3 file records point to single file data...

[Nux]

You can open properties dialog to get Windows size w/o junctions.

But it is impossible to count size w/o hardlinks because every file hardlink is a usual file record. E.g. if file has 3 hardlinks, 2 under Windows and third under Program Files, it is a big question where to count its size because all 3 file records point to single file data...

In this case TC should only count it where it originally is, not where it's NTFS links are. Link size is small to none so not important when one needs to know if some folder should be moved to other HDD or not.

[MVV]

Please search the board, it was discussed many times why TC counts junctions like folders.

[Nux]

Please search the board, it was discussed many times why TC counts junctions like folders.

My use case is I need to know the HDD size of all sub-folders. This is my feature request. Not interested what will be default behavior.

[Hacker]

Hello Nux,

TC should only count it where it originally is, not where it's NTFS links are.

Is there a difference between those two?

Roman

[Nux]

Hello Nux,

TC should only count it where it originally is, not where it's NTFS links are.

Is there a difference between those two?

Roman

Example:
* You have a folder on D:\Data\Netbeans\
* The folder is mounted to: C:\Users\MyUser\AppData\Local\NetBeans\

I want to check physical size of all sub-folders in:
C:\Users\MyUser\AppData\
But I don't care about size that is taken from D.

[Hacker]

Nux,
How would you differ between data on C and data on D?

Roman

[Nux]

Nux,
How would you differ between data on C and data on D?

Roman

Code: Select all

int calculateRealDirSize(rootDir)
{
	size = 0;
	foreach(dir in rootDir.subdirs)
	{
		if (dir.isNtfsLink)
		{
			continue;
		}
		size += calculateRealDirSize(dir);
	}
	size += fileSize(rootDir);
	return size;
}

[MVV]

Nux, as I said it was discussed already, you can use Alt+Enter to open system Properties window with size w/o counting junctions. Or maybe some plugin can count sizes in such way.

[Lefteous]

DirSizeCalc has an option to continue calculation for mount points and junctions or stopping there.

http://www.totalcmd.net/plugring/dirsizecalc.html

[Nux]

DirSizeCalc has an option to continue calculation for mount points and junctions or stopping there.

http://www.totalcmd.net/plugring/dirsizecalc.html

Thank you! You just saved me from witting a Python script for that . Now I have a custom view which includes real size column.

Still would be nice to have this built in for some command or configurable. I don't see a problem really. Shouldn't be much of an effort NTFS link discovery is already there, on-demand size calculation for many files too. Just add one new configuration option (even in ini alone) and use one or two ifs.