Bug 503640 - Dolphin Not Calculating Space Correctly for Extremely Large Mounts
Summary: Dolphin Not Calculating Space Correctly for Extremely Large Mounts
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.04.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-02 02:44 UTC by asimmons153
Modified: 2025-05-05 05:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description asimmons153 2025-05-02 02:44:55 UTC
SUMMARY
I am working with a cloud backed NFS mount that reports the available space as 16 Exabytes. When I mounted it and tried to access it via dolphin it reports 0B free of 0B and a usage of -2,147,483,648%. When I try and copy or move a file it reports that their is not enough free space to write the file. The mount works fine in command line utilities like mv, cp, ls, and df. I can also open files on the mount via dolphin but not write.

STEPS TO REPRODUCE
1. Mount a NFS share that reports a total space of 16 Exabytes
2. Copy or move a file to a directory on the share via dolphin and check mount properties.

OBSERVED RESULT
I receive the error that there is not enough free space and properties of the mount show 0B free of 0B and a usage of -2,147,483,648%.

EXPECTED RESULT
The move or copy to the mount is successful and properties shows the correct usage.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.4-arch1-2 (64-bit)

ADDITIONAL INFORMATION
This is what the share looks like with df -h
Filesystem                Size  Used Avail Use% Mounted on
192.168.124.3:/srv/share   16E  128K   16E   1% /mnt
Comment 1 John Kizer 2025-05-05 05:27:45 UTC
I don't know enough about the subject and can't personally try to reproduce, but this seems possibly related to https://bugs.kde.org/show_bug.cgi?id=440123 ?