Space used indicator is bigger than disk size

[leapacho]

Description

The space used indicator says 128 TBs of space have been used, which is false.
This was tested on v0.7.12-beta.

Expected behaviour

I want to be able to see the actual space used, which is about 50 GB, not 128 TB.

What is happening instead?

I couldn't find any error messages:

filebrowser-1  | 2025/07/05 20:59:10 [INFO] Using admin password from FILEBROWSER_ADMIN_PASSWORD environment variable
filebrowser-1  | 2025/07/05 20:59:10 [INFO ] Initializing FileBrowser Quantum (v0.7.12-beta)
filebrowser-1  | 2025/07/05 20:59:10 [INFO ] Using Config file        : data/config.yaml
filebrowser-1  | 2025/07/05 20:59:10 [INFO ] Auth Methods             : [password]
filebrowser-1  | 2025/07/05 20:59:10 [INFO ] Using existing database  : /home/filebrowser/data/database.db
filebrowser-1  | 2025/07/05 20:59:10 [INFO ] Sources                  : [folder: /folder]
filebrowser-1  | 2025/07/05 20:59:10 [INFO ] Resetting admin user to default username and password.
filebrowser-1  | 2025/07/05 20:59:10 [INFO ] Media Enabled            : true
filebrowser-1  | 2025/07/05 20:59:10 [INFO ] MuPDF Enabled            : true
filebrowser-1  | 2025/07/05 20:59:10 [INFO ] Running at               : http://localhost/filebrowser/
filebrowser-1  | 2025/07/05 20:59:11 [INFO ] initializing index: [folder]
filebrowser-1  | 2025/07/05 20:59:14 [INFO ] Index assessment         : [folder] complexity=normal directories=39204 files=229667

This is from a fresh start.

Additional context

Mounted in a different folder.

How to reproduce?

I believe it's an issue with some Docker files being read as being bigger than actual space used in disk. I have Docker stuff in the same folder File Browser uses. As seen in the second screenshot, I set the folder for File Browser somewhere else, and the indicator seems to function correctly.

Here is an example of a Docker raw file reportedly being 1 TB on a system with 256 GB of storage.

I still don't know for sure, since the example above is for Docker Desktop with the file confusing even the filesystem itself, but in my case it's just FB.

Files

N/A

[gtsteffaniak]

Hmm interesting. The size is the index size calculation. Do you have hard-linked files? I know those can be reported incorrectly

[leapacho]

Further investigation reveals that, indeed, Docker could be the culprit with a bunch of hard links... Here's an example:

root@codexmaestro:(...)docker/docker_files/overlay2/fea3595c5849a25e4e72c0579f1c88e6bb84215b4adbdc70a00a737c6aae6b55/diff/usr/share/zoneinfo# find -type f -links +1
./Canada/Atlantic
./Canada/Pacific
./Canada/Central
./Canada/Mountain
./Canada/Newfoundland
./Canada/Saskatchewan
... hundreds more

The command find -type f -links +1 supposedly finds all files with more than one link to them. Docker has about 700 of those. I suppose the fix would require telling the index size calculation to ignore Docker's directory?

[mordilloSan]

Same problem here...

[gtsteffaniak]

Thanks I think I have an idea now how to keep hardlinks from duplicating space calculations.

[gtsteffaniak]

this has been fixed in 0.7.13