Skip to content
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

encfs reverse: filter out useless "Filename too small to decode" error messages #121

Open
dakkusingh opened this issue Oct 29, 2015 · 5 comments

Comments

@dakkusingh
Copy link

Hi All,
I am running encfs on OSX 10.11.1 using brew.. encfs version 1.8.1
I created a Reverse ENCFS but i get a lot of errors like:

(encfs.cpp:138) withFileNode: error caught in getattr: Filename too small to decode

and

(encfs.cpp:138) withFileNode: error caught in getattr: Invalid data size, not multiple of block size

Could someone help please?

@rfjakob
Copy link
Collaborator

rfjakob commented Oct 30, 2015

Does it work otherwise? This is perfectly normal.

@dakkusingh
Copy link
Author

it appears to work fine other than the errors. But as the errors worried me somewhat, I have not tested it fully

@vgough
Copy link
Owner

vgough commented Oct 31, 2015

Yes, they are normal. These errors should be dropped, or at a minimum filter out the expected patterns.

@rfjakob rfjakob changed the title encfs reverse - Filename too small to decode and Invalid data size, not multiple of block size encfs reverse: filter out useless "Filename too small to decode" error messages Nov 30, 2015
@hexadecagram
Copy link

If these messages are in fact benign (when using --reverse), why are they sent to syslog with LOG_ERR priority and not LOG_WARNING or better yet LOG_INFO?

@hexadecagram
Copy link

  1. I am seeing this behavior on ArchLinux, not OSX.
  2. To my knowledge, there aren't any particular files that produce these messages. Syslog is being flooded with them as Crashplan scans the entire reversed encfs path recursively and backs up all of the files to the cloud. If I had to guess, I would be seeing the same pair of log messages for any and all files in that path.
  3. The underlying filesystem that I am mounting encfs --reverse on top of is ZFS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants