I'm not 100% of the scenario that led up to this but what i know happened was:
I shut down the server while it was repairing a file (not verifying but actually repairing)
After it started up it was semilocked up. I can't change my download speed, it refuses to add NZBs from the watch folder, it won't make any connections and it's still repairing while this is all going on.
It's almost done repairing so I'll see what happens when it's done, but it's a large file so it's been doing this for over and hour now which is a big loss in download time for me.
Also I have "Pause downloading during post processing" disabled currently.
Windows 7 64bit, latest updates.
EDIT: after it was done repairing it varified another download and then I was able to adjust the speed and connections started again. I forgot to note previously that pausing and resuming had no effect besides it just changing the status from "Downloading" to "Paused". Even though there was no connections it did not switch to "Idle".
Unresponsive while repairing
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Unresponsive while repairing
Last edited by tedrock on January 21st, 2010, 12:21 am, edited 1 time in total.
Re: Unresponsive while repairing
Windows isn't very good at distributing disk access over applications.
It's perfectly feasible for a low-priority program to completely saturate the disk channel.
par2 in repair mode is perfectly capable of this.
Windows performance immediately drops dramatically, to the point of being unusable.
Windows Vista and later have some disk priority options
which we will attempt to use in a later release.
It's perfectly feasible for a low-priority program to completely saturate the disk channel.
par2 in repair mode is perfectly capable of this.
Windows performance immediately drops dramatically, to the point of being unusable.
Windows Vista and later have some disk priority options
which we will attempt to use in a later release.