0.7.12 (and probably earlier) - Filename length [Win7]

Report & discuss bugs found in SABnzbd
Forum rules
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.
Post Reply
evolu
Newbie
Newbie
Posts: 3
Joined: October 24th, 2012, 7:17 am

0.7.12 (and probably earlier) - Filename length [Win7]

Post by evolu »

Well, it's not really a sabnzbd bug, but rather NTFS filesystem restrictions.
So I've got this error:

http://puu.sh/38gsx.png

Download itself is stucked at like 99% percents. My guess it's because of long filename, and Windows just can't handle those files. No matter how much I try to redownload, it's being stucked.
So, there is a feature to request (if it's not implemented yet, never found it): to automatically cut off/rename long filenames to something shorter, to let Windows unpack everything properly.

TIA
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: 0.7.12 (and probably earlier) - Filename length [Win7]

Post by shypike »

You simply have to make your paths shorter (below 260).
One aide is to set the Config->Special->folder_max_length to something like 50.
The problem will not be solved before release 0.8.0.
intel352
Newbie
Newbie
Posts: 3
Joined: June 24th, 2013, 8:11 am

Re: 0.7.12 (and probably earlier) - Filename length [Win7]

Post by intel352 »

shypike wrote:You simply have to make your paths shorter (below 260).
One aide is to set the Config->Special->folder_max_length to something like 50.
The problem will not be solved before release 0.8.0.
Thanks for this suggestion, trying it now. This issue has plagued me on multiple releases, had been just deleting and finding alternate release previously.
Post Reply