Ticket #388 (Open)Sun May 18 19:25:40 UTC 2014
ShareFS doesn't handle files > 2GB
| Reported by: | Sprow (202) | Severity: | Normal |
| Part: | RISC OS: Module | Release: | |
| Milestone: | Status | Open |
Details by Sprow (202):
Impirical testing suggests a number of signed int or round-up-and-overflow problems within ShareFS, though as this is a closed source component this will require an NDA to resolve.
It’s also made more tricky because the remote client may be running a version of RISC OS that itself cannot handle files > 2GB, so some means of detecting this (eg. FileCore reports “File too big”) will be needed. Does the ShareFS protocol include a capabilities negotiation? If so, a flag bit could be assigned to denote ShareFS is happy with 32 bit extents.
Changelog:
Modified by Sprow (202) Sun, May 21 2017 - 08:21:15 GMT
Additionally I just spotted that it’s Free reporting is limited to 32 bits.
So, if you share a 200GB drive, when viewed at the remote end it says “Free 4G, Used 0, Total 4G” both from desktop free and at the command line.
Modified by Sprow (202) Sun, January 12 2025 - 11:53:02 GMT
Additionally I just spotted that it’s Free reporting is limited to 32 bits.
Further testing of this case reveals that ShareFS 3.48 or later does display free space for discs >= 4GB. I was using a Risc PC with RISC OS 4.02 previously and the ROM version of ShareFS (3.43) is indeed limited to the 32 bit calls.
