newsbin.com

Hi, I don't know whats going on with this one, so I'll describe it.

Build 5068.

Download is sitting at 8.55/9.41GB (for hours).
Half the downloaded files are named correctly, half are still obfuscated.
par file hasn't downloaded.
Agressive assembly and automatically unrar is enabled.
Log: https://pastebin.com/jbqh8r86

If you gave me permissions to attach files I can provide the nzb.

I too have been getting this problem where the download stops short. After trying a bunch of things, it appears now that Newsbin is looking for much more space on the drive than is actually needed by the download size. For example: the nzb lists a download size of 1gb. I check my drive, there's 2.5gb available. Previously, this was fine. NOW, Newsbin wants THREE TIMES the download file size. So in this math case, if I go and clear up another 500mb on the drive, Newsbin resumes the download / unrar.
Anyone else finding the same thing?

I have 1.9TB free, so I don't think that is related to my issue.

NOW, Newsbin wants THREE TIMES the download file size.

It can take as much as 3 times the set size in order to complete a repair and unrar. 2 times is the absolute minimum because for a short time the unrared files and the rar files will both exist on disk. If Newsbin has to do a significant repair then it'll be > 2 times before cleanup kicks in and removes the disposable files. Newsbin was fairly casual about disk free space before because I assumed (incorrectly as it turns out) that people would keep track of their disk space and seldom run low. I had one user though with 50 gigs of free space but terabytes of files in his download list. He was running out of space multiple times a day. So, now Newsbin is strict about free space checking.

I have 1.9TB free, so I don't think that is related to my issue.

The log file will always show errors if you're out of disk space. I'm not sure what to think about your issue. If it's just one set of files then it might just be a "posted wrong". The errors in your log are fairly weird.

If you restart Newsbin what happens?

That log was from a restart. I've restarted 3 or 4 times and it never completes. The size increments from 0/9.41GB up to 8.55/9.41GB and then sits there.
All files say Downloaded, except for the pars which say paused.
The only par to download was: "<some shit>-drones.subs.par2"
No other pars downloaded, not even the main par "<some shit>-drones.subs.par2"

Are there enough par2 blocks to repair the file set? If not then I do not think Newsbin even tries to automatically download the par2 files.

If the subs are mixed in with the main files, the download will probably require manual intervention. I'd unpause all the pars then use quickpar and winrar to complete the download after the pars download.

Was this an NZB?

Yes, there seems to be plenty of pars.
If I unpause & download them, I am pretty sure I can validate with quickpar and then unrar the file without issues.
I just didn't want to do this manually.

Yes, it was a NZB and I still have it.

I just didn't want to do this manually.

Sure nobody does. On the other hand there's no "standard" for posting so, Usenet it always "best effort". It works as long as people follow certain rules and when they don't, it might need you to mess with it manually.

You can send me the NZB to look at. ts at newsbin.com

Quade wrote:

NOW, Newsbin wants THREE TIMES the download file size.

It can take as much as 3 times the set size in order to complete a repair and unrar. 2 times is the absolute minimum because for a short time the unrared files and the rar files will both exist on disk. If Newsbin has to do a significant repair then it'll be > 2 times before cleanup kicks in and removes the disposable files. Newsbin was fairly casual about disk free space before because I assumed (incorrectly as it turns out) that people would keep track of their disk space and seldom run low. I had one user though with 50 gigs of free space but terabytes of files in his download list. He was running out of space multiple times a day. So, now Newsbin is strict about free space checking.

Ok, that makes sense - thanks for clearing that up

I'm removed the 2 times space thing in B4. I think the "Pause unrars when they run out of space" will work just as well.

There's never a solution that pleases everyone. So now you'll see an unrar stall in the middle if the unrar runs out of space. Download will stall the same way.