Exclude junctions from calculated folder size
Posted: 04 Feb 2009 11:09
It would be nice to exclude junctions from the calculated folder size. (must not be the default, an option should be enougth)
Logicaly a junctions is only a link to somewhere else so the space of the files and folders in it is calulated somewhere else.
I use a junction to place my APPS-Folder from another disk into my every-day-working-directory called "C:\DATEN\".
When I now want to know how big "C:\DATEN" is, XY returns about 100GB but only about 50GB are stored on the C:-Partition.
The other 50GB are stored on another partition an another physical hardddisk.
Its very confusing for me to get a folder-size from data which is spread over two physical harddisks.
So I have to go into my folder and select everything except the junction(s) and calulate here.
Another more practical example why to use junctions or hardlinks:
I have a mapping from "C:\xampplite\htdocs" to "C:\DATEN\htdocs", this is a junction now, but I want to have the space counted for this item, so I better convert this to a hardlink for future purposes. I collect several folders in "C:\DATEN" but theres also a bit of data directly stored in it. (about 50GB)
You might ask, why do I collect all these folders together, and not use individual entries in the catalog? Answer is simple, having all these in a single folder makes it very easy to use for external application for example: Sync this folder between my home-computer and my laptop. It also makes the MiniTree as compact as possible. And it also works in network, which allows me to reduce the amount of shared-folders needed.
I checked the behavior of WindowsExplorer and it simply ignores the junctions when calculating the folder-size.
I think, we have the same issue with hardlinks, but hardlinks, don't have a attribute ore something that can tell you, "hey I'm number 1 file" and "hey I'm only a second link", so I don't see a solution for hardlinks, but junctions should be easy to detect, what XY allready do (Attr-Col, FileInfoTips, InfoPanel)
Logicaly a junctions is only a link to somewhere else so the space of the files and folders in it is calulated somewhere else.
I use a junction to place my APPS-Folder from another disk into my every-day-working-directory called "C:\DATEN\".
When I now want to know how big "C:\DATEN" is, XY returns about 100GB but only about 50GB are stored on the C:-Partition.
The other 50GB are stored on another partition an another physical hardddisk.
Its very confusing for me to get a folder-size from data which is spread over two physical harddisks.
So I have to go into my folder and select everything except the junction(s) and calulate here.
Another more practical example why to use junctions or hardlinks:
I have a mapping from "C:\xampplite\htdocs" to "C:\DATEN\htdocs", this is a junction now, but I want to have the space counted for this item, so I better convert this to a hardlink for future purposes. I collect several folders in "C:\DATEN" but theres also a bit of data directly stored in it. (about 50GB)
You might ask, why do I collect all these folders together, and not use individual entries in the catalog? Answer is simple, having all these in a single folder makes it very easy to use for external application for example: Sync this folder between my home-computer and my laptop. It also makes the MiniTree as compact as possible. And it also works in network, which allows me to reduce the amount of shared-folders needed.
I checked the behavior of WindowsExplorer and it simply ignores the junctions when calculating the folder-size.
I think, we have the same issue with hardlinks, but hardlinks, don't have a attribute ore something that can tell you, "hey I'm number 1 file" and "hey I'm only a second link", so I don't see a solution for hardlinks, but junctions should be easy to detect, what XY allready do (Attr-Col, FileInfoTips, InfoPanel)
Just checked: everything like Explorer.