par2 verify after repair fails if sfv renames the files
Posted: May 19th, 2015, 7:46 pm
I am not sure if this is even "welcome" in this forum, as i am running SABnzbd 0.7.20 on CentOS 7 installed from yum using https://dl.dropboxusercontent.com/u/145 ... -CentOS/7/
I have noticed, whenever a NZB with "scrambled" filenames (and a sfv with the real filenames) is missing/failed at least 1 article, thus triggering a par2 repair, it will falsely "fail" the download, as the files get renamed and par2 is no longer able to find/verify his repaired files.
So the frontend shows the NZB as "verify failed"
Yet all - repaired - files are in the incomplete folder with there proper - sfv renamed - filename.
A separate sfv check, as well as archive test, from within the incomplete folder shows that all files are healthy.
Now if no renaming takes place the download will succeed.
I have "Post-Process Only Verified Jobs" enabled (factory default, i didn't touch anything)
I haven't created any debug logs yet, so i am not really able to tell if/were SABnzbd/par2 or sfv gets out of its mind or what switch i should change.
Thanks
Cheers
I have noticed, whenever a NZB with "scrambled" filenames (and a sfv with the real filenames) is missing/failed at least 1 article, thus triggering a par2 repair, it will falsely "fail" the download, as the files get renamed and par2 is no longer able to find/verify his repaired files.
So the frontend shows the NZB as "verify failed"
Yet all - repaired - files are in the incomplete folder with there proper - sfv renamed - filename.
A separate sfv check, as well as archive test, from within the incomplete folder shows that all files are healthy.
Now if no renaming takes place the download will succeed.
I have "Post-Process Only Verified Jobs" enabled (factory default, i didn't touch anything)
I haven't created any debug logs yet, so i am not really able to tell if/were SABnzbd/par2 or sfv gets out of its mind or what switch i should change.
Thanks
Cheers