Page 1 of 1

Incorrect disk space reported on Mac Catalina

Posted: November 3rd, 2019, 7:36 am
by Deamon1234
Hi, I am having issues with disk space since upgrading to Catalina. I have about 300GB free on my internal drive but Sabnzdb reports out of disk space.

Traceback (most recent call last):
File "cherrypy/_cprequest.pyc", line 663, in respond
File "cherrypy/_cpreqbody.pyc", line 989, in process
File "cherrypy/_cpreqbody.pyc", line 558, in process
File "cherrypy/_cpreqbody.pyc", line 223, in process_multipart_form_data
File "cherrypy/_cpreqbody.pyc", line 215, in process_multipart
File "cherrypy/_cpreqbody.pyc", line 556, in process
File "cherrypy/_cpreqbody.pyc", line 715, in default_proc
File "cherrypy/_cpreqbody.pyc", line 730, in read_into_file
File "cherrypy/_cpreqbody.pyc", line 700, in read_lines_to_boundary
IOError: [Errno 28] No space left on device

Anyone seen this, Sabnzdb has full access to my drive so its 100% NOT a permission thing.

Re: Incorrect disk space reported on Mac Catalina

Posted: November 3rd, 2019, 8:16 am
by Deamon1234
Just to add to this, i added an external drive. That works fine, so this is an issue of reporting an internal drive size.

Re: Incorrect disk space reported on Mac Catalina

Posted: November 5th, 2019, 1:59 am
by safihre
This error is reported by the OS.
So this part of the code seems to be triggered when uploading an NZB, not the actual download process. When you upload an NZB it's first stored in a temporary folder, provided by your OS after which it's imported by SAB. It could be that Catalina is more strict on this?
In the logging it will write where this temporary directory is, usually somewhere in your OS disk.

Re: Incorrect disk space reported on Mac Catalina

Posted: November 8th, 2019, 3:05 pm
by Deamon1234
Its only related to the internal system drive. I have connected an external drive and the issue does not happen. Even if I create APFS volume it still reports no disk space when there is over 300 GB.

Re: Incorrect disk space reported on Mac Catalina

Posted: November 8th, 2019, 4:10 pm
by safihre
Again, this is not some check we do. It's the lower level system code that tells us it can't write files because the disk is full. No higher level special checks, just low level IO error.. We can't do anything about that.