Nemo does count multiple fileentrys with the same inode multiple times twoards the memory usage.

[ygerlach]

 * Nemo version 5.2.4
 * Is issue with desktop or windowed nemo? windowed
 * Distribution - Mint 20.3 Cinamon
 * Graphics hardware *and* driver used - general problem, not important
 * 64 bit

Issue
Selecting two hardlinks of the same file shows twice the hardware useage and not the actual usage

Steps to reproduce

# create a testfile
truncate -s 1G testfile

# create a hardlink
ln testfile testfile2

Select both fileentrys with nemo.
Nemo shows those files with "2 Items selected (2,1GB)"

Rightclick -> Properties also shows 2,1GB

Expected behaviour
Nemo shows the same harddrive usage as only one file selected (1GiB).
Deleting both file would only freeup 1GiB not two.

Other Information
I did observe the same bug with nautilus.

[Jeremy7701]

Not a bug.

Each hardlink refers to the same dataspace.
So deleting both hardlinks only deletes one file.

[ygerlach]

Thats exactly what i mean.

I have a 1GB testfile.
So when i create a hardlink i have 2 files with 1GB total space consumption (as you said yourself) (ignoring the space required for the second filename).
So when i click on both files nemo should show 1GB of usage, but it shows 2GB of usage.

[Jeremy7701]

You would get the same behaviour with symbolic links.

# Create a testfile
truncate -s 1G testfile

# Create a symbolic link
ln -s testfile testfile2

nemo will see each of these files as 1 GB, just like the hardlink case.
But if you effectively select a file twice, it would be a bit weird if you didn't see double.

[ygerlach]

just because the behavior with symbolic links is also broken, doesnt make it right. When i select some files to delete thinking i would free up what ever amount of space, just to find out they where all hardlinked is the same confusion by lying about the selection.

[ygerlach]

The way to solve that would be to implement a set, that holds all already found inode numbers, so the same inode is not counted twice. In theory easy to implement.

[Jeremy7701]

This would only work for hardlinks - which are typically created by software installers and backup software, so not something you would want to consider deleting just to free up space.

[ygerlach]

Its still wrong information. And softlinks can be created by nemo on the command of users as well. Why do you rather want to have broken software that gives false information, than a one that gives information, that is correct? Having a set of inodes, that was already scanned isn't even that complicated concept. du does the same. If someone points me to the right resources i would try implementing it myself. But i have never worked with the nemo source code before.

[github-actions]

This issue has been automatically marked as stale because it has not had
any activity in over 2 years.

If this issue is still relevant:

• Please test on a current version of this package.
• Add a comment with your findings

If no activity occurs in the next 30 days, this issue will be
automatically closed. Issues can be reopened if needed.

[ygerlach]

Was just able to reproduce it on nemo 6.4.5.
So i think its still relevant.