You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The same file can appear in multiple places in a directory hierarchy. This includes things like Rust's own build directories, /rescue partitions with tools like busybox, backups using rsync --link-dest, and so forth.
Traditional du's deal with this by keeping a map of seen inodes and their link counts, and avoid counting additional copies of the same inode - decrementing the link count until all have been seen and the inode can be forgotten. This may not be perfect for an interactive tool like this, but it would probably be better than nothing.
The text was updated successfully, but these errors were encountered:
Thanks a lot for posting your insights on how this is actually implemented in du. This might be helpful when trying to resolve this issue.
Performance-wise it might be OK to implement it, even though the memory consumption might go up visibly. However, being correct AND fast (enough) by default is my preference, too, and as long as hardlink tracking can be disabled I would be happy to see this fixed.
The same file can appear in multiple places in a directory hierarchy. This includes things like Rust's own build directories,
/rescue
partitions with tools like busybox, backups using rsync--link-dest
, and so forth.Traditional
du
's deal with this by keeping a map of seen inodes and their link counts, and avoid counting additional copies of the same inode - decrementing the link count until all have been seen and the inode can be forgotten. This may not be perfect for an interactive tool like this, but it would probably be better than nothing.The text was updated successfully, but these errors were encountered: