I'm getting a bunch of these
09/11/2020 15:09:20: Hashing file: ""
09/11/2020 15:09:20: Failed to open really.long.file.name.with.lots.of.dots.1x01.in.which.an.even.longer.title.name.is.buried.avi
These filenames are > 122 characters, and the directory path is 138 characters at 7 levels deep
Files with slightly shorter names in the same directories are read fine
Most other files are also at 7 levels of nesting, so I don't think that's the issue
Is there an arbitrary limit on file name length?
(Running 0.60a inside wine on Ubuntu)
Page 1 of 1
Overly Long File Name Issue?
#2
Posted 09 November 2020 - 09:32 PM
#3
Posted 19 November 2020 - 10:07 AM
This is the 260 character limit enforced by NTFS. Apparently it's been removed but apps need to use the new API calls.
#4
Posted 27 December 2020 - 02:21 PM
antonymous, on 19 November 2020 - 08:07 PM, said:
This is the 260 character limit enforced by NTFS. Apparently it's been removed but apps need to use the new API calls.
Workaround: Use shorter paths, or move your files and pointers!
This post has been edited by emule_user_downunder: 27 December 2020 - 02:23 PM
#5
Posted 05 January 2021 - 11:46 AM
This error represents that the file name is either too long to open, delete, or edit considering the given file location or path on your hard drive. Windows by rule only allows a file path to be up to 260 characters long. Keep it under that and you should be fine!
Page 1 of 1