ecryptfs fails sporadically
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eCryptfs |
Incomplete
|
High
|
Unassigned | ||
ecryptfs-utils (Ubuntu) |
Incomplete
|
High
|
Unassigned |
Bug Description
Binary package hint: ecryptfs-utils
ecryptfs seems unreliable. In a recent case I performed a git fsck on a large samba4 repo, like this:
git fsck --full --verbose --strict
it failed with a corrupt dangling commit, and dmesg showed:
[961417.528106] ecryptfs_
[961417.528150] Valid eCryptfs headers not found in file header region or xattr region
[961417.528156] 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
I repeated the git fsck and it worked without problem, and dmesg showed nothing.
as git fsck does not repair, we can clude that different data was read the second time. The chance of a bad git appearing good by accident is very small. The fact that the dmesg error shows when git fsck fails suggests that the failure occured the first time and not the second time.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libecryptfs0 83-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.35-
NonfreeKernelMo
Architecture: i386
Date: Thu Feb 10 09:13:38 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: ecryptfs-utils
Hi Sam,
Thanks for the bug report, and reproduce instructions.
For what it's worth, I just cloned samba4, and did the fsck (which took ~7 minutes), but it completed without error, and without any dmesg noise. Was just one test, and I'll retest now, but I wanted to confirm that at least my first run completed without error.
This is:
Linux x201 2.6.38-2-generic #29-Ubuntu SMP Fri Feb 4 13:03:04 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
ecryptfs-utils 85-0ubuntu1