SABnzbd Forums

I have a lot of directories in my system which I don't know if were processed or not. They accumulate to more than 200 every week or so. Checking each of them manually takes a ridiculous amount of time.

I wrote a script to go in each directory, find par, rar, sfv, srr, srs, etc and try to do something with it. If everything fails, then delete the whole thing.

But of course the devil is the details.

In many cases I found dirs that have *.partXY.rar AND *.partXY.rar.1 files, besides the par2 files (and even *.par2.1 files). The .rar files have different sizes and date/times to the .rar.1 files.

What creates these .1 files? They are an attempt of sabnzbd to download correct files? Do they come to the system from the same nzb as the regular files or from another lets-try-fix-it nzb?

Regards,

There are two possibilities.
The NZB contains double file records, the second file will get .1 added to prevent overwriting the first.
The other (most likely) cause is par2 repair. par2 will rename the original damaged file to .1
Normally SABnzbd will remove these, but sometimes one manages to slip through.

Hi Shypike, thank you so much for helping. I'm lost here. I found out dozens of directories with this situation: Like 50 files .rar and the files with the same exact name but named .rar.1...I hadn't considered par2 as the source of the .1 (as to avoid overwrite of original file). I will try to test it.

EDIT:

- Par2 seems to not be the cause: I tried to par2 repair in these directories and found out that there are not enough par2 parts to attempt repair in any of them.

- Tried to unrar the .rar sets and found out many of them are corrupted.
- Then I tried the .rar.1 sets and found out they are not even recognized as valid .rar files by unrar-paid and unrar-free. Attemped to rename the .1 extension, but it was not enough.

Man, I hate users, how do people do these things??

Check the NZBs. Do they contain double entries for files?

No, they look ok so far (could not check them all, looked at like 50 of them and didn't find anything unusual.

Is this situation possible:

- sabnzbd had the "Detect Duplicate" option set as ignore.
- Jobs got orphaned in the download folder after failed / poorly done upgrades, cleared queue, who knows what.
- All same jobs were re-added to queue via the "Status/Queue Repair/Orphaned" list. Or even the backup nzbs were copied again to the watch folder.
- Same jobs were re-downloaded to same locations, however sabnzbd had no option but to rename them to *.1 in order to be able to accommodate them in the directories?

OBS: Sabnzbd has the permission to overwrite at the downloads/* folder actually, but I don't know if it would prefer that as a standard behavior over renaming.

Thanks,

If you're talking about release 0.5.6, then it's not possible that
existing folders in "incomplete" are a problem.
The new NZB would just get a folder with .1 or .2 appended.

If it's about 0.6.0, you're in the wrong board.