Author Topic: Repair behavior  (Read 2328 times)

Offline AimHere

  • Contributor
  • ***
  • Posts: 17
Repair behavior
« on: September 21, 2010, 03:30:40 pm »
Hi,

I'm finding the behavior of the automatic Repair function to be inconsistent. I'll start a bunch of downloads and walk away... come back later, the downloads are 100% complete. Then I switch to the PAR2 tab, and see that while many of the files unRARed successfully, there are some that say "repair failed" (and clicking on them to expand the display might show that "something.r08" was missing a few blocks).

Thing is, I switch back to the Download Queue and expand the entry for that item, only to find that most of the PAR2s for the item have NOT been downloaded (that is, they are still paused in the queue). If I manually UNpause all the PAR2s and let it finish, alt.binz tries to repair the files again... only THIS time, the repair is SUCCESSFUL and alt.binz goes on to unrar the files.

My question is, when it determines a file needs to be repaired, how does alt.binz determine which PAR2s to download, and which ones to skip? Because it doesn't seem to be picking the RIGHT ones needed for the repair, since if I force it to download them all, the repairs do work.

Mind you, there are other items I download which also end up needing repair, and alt.binz seems to do the job on its own. That is, it correctly determines which PAR2s are needed, unpauses only those, downloads them, and completes the repair and unrar. But it's maddening that it can't do this all the time.

I'm thinking the way to get around this problem would be to just go into alt.binz' setup and uncheck the "import as paused" option for PAR2 recovery files, so that it always downloads them whether they are needed or not. But this seems like a waste of bandwidth and time, since they aren't always needed. I'd like to leave "import as paused" checked, but I just wish the repair function was smarter about auto-downloading PAR2s.

Aimhere

Offline davidq666

  • Contributor
  • ***
  • Posts: 1302
  • Watashi Wa Ero Desu!
Re: Repair behavior
« Reply #1 on: September 21, 2010, 04:39:43 pm »
yeah i noticed that, too sometimes the amount of pars files needed seems to be miscalculated. i will try to find some logs to document the bug more properly, i'd suggest u do the same. the better reproducable it is the better the chances are to get it fixed...

Offline Hecks

  • Contributor
  • ***
  • Posts: 2011
  • naughty cop
Re: Repair behavior
« Reply #2 on: September 21, 2010, 08:10:49 pm »
Yep, seen this too a few times recently: miscounting of par2s needed and/or available, but works fine when they're manually downloaded.

Alt.Binz fails at math! :P

Offline AimHere

  • Contributor
  • ***
  • Posts: 17
Re: Repair behavior
« Reply #3 on: October 11, 2010, 05:12:22 pm »

Alt.Binz fails at math! :P


This does not inspire confidence...  ;D

Offline Rdl

  • Administrator
  • *****
  • Posts: 4050
Re: Repair behavior
« Reply #4 on: October 18, 2010, 10:00:38 pm »
Heh, not really. The problem lies in collections with multiple par2 sets with sfv or nfo included in sets and delete nfo/sfv option ticked.
However I agree it's a bug.