Hi all,
Since few days I’m fighting with Siril disk space management, which seems not working properly. Not depending which HD I select as a current working position, either internal, external, NAS, etc, the disk space available is always wrongly displayed and pretty smaller than the actual size. I tried all the few tips I found browsing the web, such as disconnecting and connecting again, or empty the trash folder (of course), but noting fixes the issue. I currently working with an internal 2Tb SSD which is supposed to be 50% free - as system and all the the applications report the right way - and Siril reports only 400Gb available, and a 14Tb NAS with 9Tb fo free space, while Siril reports only 700Gb of free space available, that is totally absurd.
Until some days ago everything worked fine. Siril seems got crazy after massive file deletions on my hard drives. In spite of having emptied the trash folders, Siril still reports wrong free space available.
I work with a couple of Mac, OS X 12.2.1 (Monterey) and 10.15.7 (Catalina), and Siril last release (1.0.0.rc2, but I also tried with previous release and the issue is still there).
Thank you,
Carlo
Siril calculates the free space of the working directory which may be different from the free space of the hard disk.
As far as I know, there is no problem in estimating the disk space, however, if you have macOS, there is the purgeable disk space that must be purged.
I would say it’s not the point. In this case, the working directory free space coincides with the volume free space given the disk format structure (and on the other hand the system tools report the same status). Also, system SSD and NAS work and are managed differently since one is directly managed by OS X and it’s formatted as an APFS disk, while the NAS is HFS+ managed under DMS.
Meanwhile, I’ve discovered something interesting: sounds everything works fine with the NAS provided it’s mounted via AFP and not SMB. As a standard method, the OS X access the NAS via SMB, but I forced an AFP mount and now Siril reports the right free space being almost 9Tb. As soon as I mount the NAS via SMB, Siril reports only 700Gb of free space.
So, I guess it’s a matter of how Siril communicates with OS X, and seems particularly in trouble with new APFS formats and M1 chip, since it works fine with local HDD on my Intel iMac, it’s wrong with local SSD on my M1 MBP. Same Siril version on both the computers, different behavior.
For computing remaining free disk space we use a standard function. Of course, this is not dedicated for MacOS use case as none of the Siril devs are using MacOS.
So I don’t know if there is a way to get a better computation on MacOS, but if it exists, we would really appreciate any help.