NZBget also shows it wrong.
The nzbget code is pure C, see these few lines: https://github.com/nzbget/nzbget/blob/0 ... #L675-L679
so that proves the root cause is at the MacOS-system-level. Not in python, not in SABnzbd.
Furthermore, it seems something specific to you: I've let a Mac friend test it (SMB mounted NAS, 6TB) and there is no problem there:
Code: Select all
thelema:Desktop frank$ python disk_space.py /Volumes/Data/
python version: 2.7.10 (default, Feb 7 2017, 00:08:15)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)]
statvfs posix.statvfs_result(f_bsize=1048576, f_frsize=8192, f_blocks=732482664, f_bfree=620759038, f_bavail=620759038, f_files=732482662, f_ffree=620759038, f_favail=620759038, f_flag=2, f_namemax=255)
disk_size [GB] 5588.39923096
available [GB] 4736.01560974
The df took [ms]: 6
//com.apple.idms.appleid.prd.444a357blabla/Data 5722520 872840 4849679 16% 111723624 620759038 15% /Volumes/Data
Available [MB]: 4849679
Correct sizes reported. Which means we can't reproduce it.
The other Mac user with SABnzbd did not have a problem after all. A false alarm.
So ... IMHO there is not something we should & could in SABnzbd.