Is it possible for extra-long filenames of a release to cause extraction/repair to "choke"?
Posted: August 5th, 2025, 4:15 pm
I ran into a thing yesterday where right up to the very last second the download seemed to be going swimmingly (the release was maybe three years old), and indeed all the files and the par2 volumes seemed to be there later in the "incomplete" folder, but there seemed no way to repair the download. "Retry" with the original .nzb did nothing either.
Now these file names were crazy long. Could that have something to do with why unpacking/repair failed?
Thanks for any enlightenment.
Now these file names were crazy long. Could that have something to do with why unpacking/repair failed?
Thanks for any enlightenment.