Directory Junctions and Symlinks not ignored (also hardlinks)

avogelba / WinDirStats

WinDirStats - Windows Directory Statistics, private clone from:

https://bitbucket.org/windirstat/windirstat

GNU General Public License v2.0

5 stars 0 forks source link

Directory Junctions and Symlinks not ignored (also hardlinks) #5

Open avogelba opened 10 years ago

avogelba commented 10 years ago

Originally reported by: Oliver (Bitbucket: assarbad, GitHub: assarbad)

Reported by https://sourceforge.net/u/zz2/

There is the problem: WinDirStat not ingnored Directory Junctions and Symlinks on NTFS file system. These pseudo-directories and pseudo-files added to a statistics of a disk size, but they should be ignored because they are virtual objects.

https://sourceforge.net/u/sebbu/ remarked:

on NTFS file systems, hardlinks should be ignored too

Anonymous remarked:

Hardlinks should not be ignored, but hardlink should be counted one time only instead of all.hardlinks to one file. Optionally WDS can count all instances of a hardlink to estimate how much space files will have after copying to an other disk.

Bitbucket: https://bitbucket.org/windirstat/windirstat/issue/5

avogelba commented 7 years ago

Original comment by mirh (Bitbucket: [mirh](https://bitbucket.org/mirh_), GitHub: Unknown):

Some ideas btw https://blogs.msdn.microsoft.com/oldnewthing/20041228-00/?p=36863

avogelba commented 7 years ago

Original comment by Dimo (Bitbucket: nwod, GitHub: Unknown):

Any chance of getting a new stable release with this any time soon?

avogelba commented 10 years ago

Original comment by InfernoZeus (Bitbucket: InfernoZeus, GitHub: InfernoZeus):

I just cloned master to try and work on this issue, but as far as I can tell it's already been solved. Here's a couple of screenshots to demonstrate:

Here's the behaviour in the stable release 1.1.2 - both the target file and the symbolic link show as the same size:

Here's the new behaviour in master - the target file shows the original size, but the symbolic link has a size of 0:

Personally, I'll start using my own version built from master, but is there any chance of this fix being pushed to a stable release? (As far as I can tell, the last stable release of WDS was in 2005.)

avogelba commented 10 years ago

Original comment by Oliver (Bitbucket: assarbad, GitHub: assarbad):

Jason compared WDS behavior to that of DU from Sysinternals (in emails in Dec 2013). The comparison isn't 100% proper, but there are some valuable hints.

One is that WDS should show on-disk and logical size separately.