Filesystem looks OK, but log messages "Valid eCryptfs headers not found in file header region or xattr region"

Asked by Steffen Neumann on 2009-11-25

Binary package hint: ecryptfs-utils

Hi,

I keep accumulating messages about eCryptfs in the logs,
although the filesystem works as expected. But I guess
the constant writes slow down my system quite a lot.

The closest related bug report seems to be "#372014 errors in dmesg",
but that was closed with "fix released", so I am opening a new report here.

Yours,
Steffen

Partition is mounted as:
/home/.../Private on /home/... type ecryptfs (ecryptfs_sig=bd...f7,ecryptfs_fnek_sig=8b..db,ecryptfs_cipher=aes,ecryptfs_key_bytes=16)

System is an up-to-date (including karmic-proposed) karmic:
Linux paddy 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:53:52 UTC 2009 x86_64 GNU/Linux
ecryptfs-utils_81-0ubuntu3

Nov 25 14:32:54 paddy kernel: [27542.011682] Valid eCryptfs headers not found in file header region or xattr region
Nov 25 14:32:54 paddy kernel: [27542.011693] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO
Nov 25 14:32:56 paddy kernel: [27544.012088] Valid eCryptfs headers not found in file header region or xattr region
Nov 25 14:32:56 paddy kernel: [27544.012099] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO
Nov 25 14:32:58 paddy kernel: [27546.012529] Valid eCryptfs headers not found in file header region or xattr region
Nov 25 14:32:58 paddy kernel: [27546.012540] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu ecryptfs-utils Edit question
Assignee:
No assignee Edit question
Last query:
2009-11-25
Last reply:
2012-08-29
Dustin Kirkland  (kirkland) said : #1

You have some zero byte files, most likely.

find $HOME/.Private -size 0

You can probably remove these, as they are empty, and likely trash at this point.

Dustin Kirkland  (kirkland) said : #2

You have some zero byte files, most likely.

find $HOME/.Private -size 0

You can probably remove these, as they are empty, and likely trash at this point.

Casey Marshall (cmars) said : #3

Just got bit by this one. Should eCryptfs be improved to autorecover and delete these empty files automatically? I could see this causing intermittent problems in a production environment once a volume runs out of space.

Can you help with this problem?

Provide an answer of your own, or ask Steffen Neumann for more information if necessary.

To post a message you must log in.