Comment 47 for bug 344878
Revision history for this message
| Jakob Unterwurzacher (jakobunt) wrote Re: file name to long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry) | #47 |
@Compression: This may work for english, but will then fail for arabic, chinese etc. filenames. The strings are just too short I'm afraid.
Disabling the base64-style encoding and removing the prefix would give us an average limit of > 250 chars (not 255 because we'd need to encode / and NULL). Worst-case (all / or NULL) would be 127. I understand that the encoding is for portability, but couldn't it be made optional? Standard Linux filesystems don't care as long as the file name does not contain / and NULL.