"Not enough free space (0) to import" with NFS share

I have NzbDrone installed on Ubuntu Server 12.04.4 LTS w/ Mono v3.2.1. The destination directory for the processed media files is on an NFS share mounted through Autofs. NzbDrone mistakenly throws a “Not enough free space (0) to import” error for every downloaded file.

Ubuntu is accurately reporting the free space on the mounted share:

redacted@nzbdrone:/mnt/downloads$ df .
Filesystem 1K-blocks Used Available Use% Mounted on
192.168.1.20:/mnt/Volume1/Downloads 3301251072 2684574336 616676736 82% /mnt/downloads

Thanks in advance for the help!

Known issue, it is likely pulling the free space from / Don’t yet have a solution.

Thanks for the prompt response. Perhaps a tickbox to disable free space validation could be added to advanced settings?

Yeah, not a bad idea. Added to the board: https://trello.com/c/l6qbGtE2/614-advanced-option-disable-free-space-check

Quick update regarding this issue. Nzbdrone does appear to detect free space in /:

Location	Free Space	Total Space
/ (/)	12.0 GB	14.4 GB
/boot (/boot)	185.6 MB	227.7 MB

Not sure why it would report the error if it’s pulling the free space from the root directory.

I see the feature is in development now. (thx!)

In the meantime - is there some workaround? Experiencing exactly the same issue on Ubuntu 13.10 after upgrade from mono 2.x to 3.x and latest nzbdrone.

Switching to develop is the only option. Should be pushing the release in the next day or two assuming things are still working well.

Thx and just did. Now I’m pulling my hairs out trying to find where to set this new advanced option (2.0.1309 confirmed up & running) …

From the github source of SortingViewTemplate.html I understand this option should be found at /settings/mediamanagement (w/show advanced options set to yes), but it’s not showing.

Line 26 states: {{#isMono}} and line 51 states {{/isMono}}.

Based from what I see in the source of other html files like PermissionsViewTemplate.html, shouldn’t this be: {{#if_mono}} and {{/if_mono}} ??

@funbase yup, messed that one up. Pushed a fix, should be available in a few minutes.

@markus101 Thanks for the quick fix. However, seems setting doesn’t get actually saved to DB :frowning: (saw the same behaviour while injecting the HTML code for the setting) so there must be something else wrong as well. Something that goes way beyond my code-reading skills :wink:

Save of other settings are sticky - just not this specific setting…

@funbase another dull moment for me, forgot to add it to the API. Pushing is up again. Same deal, give it a few minutes and then try again, please.

@markus101 And that fixed it! Thx!