Comment 69 for bug 509180
Revision history for this message
| Serge Hallyn (serge-hallyn) wrote Re: [Bug 509180] Re: ecryptfs sometimes seems to add trailing garbage to encrypted files | #69 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Quoting Tomi Pieviläinen (<email address hidden>):
> While it doesn't seem to be the focus of this bug, the relevant bugs
> have been marked as duplicates of this one.
>
> I'm running 2.6.38-8 in Natty beta, and still getting a lot of
>
> Apr 12 14:46:32 puppy-ubuntu kernel: [31106.234038] Valid eCryptfs headers not found in file header region or xattr region
> Apr 12 14:46:32 puppy-ubuntu kernel: [31106.234047] 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
>
> so it would seem that either the patch hasn't fixed this, or #372014 is
> not actually a duplicate.
Is this with clean underlying fs? If non-ecryptfs or corrupted files are
already there, you'll keep getting those warning until you remove them.
The bug would only be the creation of new files.
It seems like it might be helpful to log the underlying inode number
in these printks.