-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rules regarding maximum filename length are confusing, documentation could be improved #183
Comments
The limit is 176 characters and I will fix up the man page. |
Is it because filenames are encoded in Base64? It would help if the man page stated that. |
Here I can create file with 175-byte name, not 176. Is this intended? Using fuse-encfs-1.9.5-1.el7 on ext4 fs. |
Be sure your filename does not contain special characters :
|
It was this file: '0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234' |
Yep, 175 it is. Looks like I got it right in the table: https://nuetzlich.net/gocryptfs/comparison/#file-names |
see #540 for a man page fix. |
Hello.
Recently I faced a strange problem with EncFS. You can find all the details here:
syncthing/syncthing#3338
syncthing/syncthing#3355
Long story short - according to encfs man page it should handle file names up to "approximately" 189 characters since underlying ext4 FS handles up to 255 characters (formula: 3*(N-2)/4). But in practice I couldn't create a file with name containing 145 characters. Syncthing developers and I couldn't figure out why.
I believe it's because by file name you mean absolute file name, but I'm not sure about it and it's not clear from the documentation. Perhaps you could give more details on what are limits on maximum file name length and absolute file name length.
The text was updated successfully, but these errors were encountered: