SABnzbd Forums

I used the packages from this website :
http://synoblog.superzebulon.org/2011/0 ... 6-5-1-spk/

In that case it looks like the porter did a poor job.
I cannot check whether Ubuntu does it really right, because I don't happen to have a >8T array lying around.

shypike wrote:I'm just going to limit the numbers to the highest possible values.
So in your case 8T would be shown as disk size.
BTW: whoever ported Python to the Synology platform made an error.
The amount of free/total blocks should be returned as long integers, not standard integers.
(1000L vs. 1000).

Shypike, out of curiosity:
is the negative value a result of two's complement?
is the 8T disk size the product of 2G x 4k block size? Or 4G x 2k block size?
as a (better?) hack, can't you calculate from the negative value back to the most probable postive value? So: convert the int to longint, and then add 2G (or 4G)? And then multiply by the block size?

sander wrote: is the negative value a result of two's complement?
is the 8T disk size the product of 2G x 4k block size? Or 4G x 2k block size?
as a (better?) hack, can't you calculate from the negative value back to the most probable postive value? So: convert the int to longint, and then add 2G (or 4G)? And then multiply by the block size?

Maybe, but I cannot test properly.
Anyway things will break down even worse after 16T.

Hiho
same problem here, is there now a fix?

You can disable the free disk check in Config->Folders.

I cant find it in my config??

thx
grz

Just don't fill in a value or remove an existing one.

"Minimum Free Space for Temporary Download Folder"
this?

There is no value

In that case, no check is done.
SABnzbd 0.6.6 will stop the numbers from becoming negative.

great
im so excited to run this great software on my big bertha,
is a release date out?

Any day now.

Are there any news yet on how to fix this annoying bug? The frustration is growing and this thread is the only one I've been able to find on the subject. Is it Python or something else causing the problem?

I'm running the following config:
Hardware: DS211+ with DSM version
DSM version: 3.2-1955
Disks: 2x1.5 TB disks in a RAID 1.
Python version: 2.6.6-5
SABnzbd version: 0.6.14-1
(The packages has been downloaded from the SuperZebulon Repository at http://synopkg.superzebulon.org/spkrepo/packages)

############# UPDATED ###############
Only five minutes after posting my question I actually came up with a solution for my own and hopefully others problem as well.

Background: I'm from Sweden and was stupid enough to set swedish as default language for my DS211+. Generally, this is never a good choice since there is always an idiot involved in the language translation process. In this case, the disk volume name created, "volume1", was translated to "Volym 1" when I checked the volume name in the Storage Manager. Fooled me!

So, in DSM/File Manager I first created a new folder called nzb with two subfolders, incomplete and complete, using the File Browser. In the SABnzbd web config interface I then set the Temporary Download Folder to Volym 1/nzb/incomplete and the Completed Download Folder to Volym 1/nzb/complete. Once saving the settings and downloading a movie I noticed the incorrect disk space. I downloaded Putty for checking all folders on the NAS via SSH, and found the correct volume name to be "volume1". Nothing else.

Changing the locations to /volume1/nzb/incomplete and /volume1/nzb/complete solved my problem.

I hope this will help at least some of you.

/Totally retard as far as Linux goes

Hi there,

I just installed SABnzbd on my new DS212+
The same problem happened here with the "cannot create...."

I found out that the default "/volume1/downloads/incomplete" and the "/volume1/download/completed" didnt work as mentioned.

So I telnet to my DS and saw that the correct path in my case was "/volume1/Disk1/Download/incomplete" and "/volume1/Disk1/Download/completed" works.

During installation of my two disks I named the first disk " Disk1" (case sensitive!) and I already made a Download folder (again case sensitive). SABnzbd (or Python in that case) made the directories "incomplete" and " completed".

So try it with your own Harddisk name and watch for case sensitive directory-names.

Hope this helps, please let me know.