[Bug 242448] Re: Hardy ecryptfs can cause data loss

Serge Hallyn serge.hallyn at gmail.com
Tue Aug 12 13:59:49 UTC 2008

On Tue, Aug 12, 2008 at 8:42 AM, Adam Wood <adamwood at xephi.co.uk> wrote:
> I've just gone back to test it again and have discovered there may be a
> time element involved.
> After my earlier test I accidentally forgot to unmount /tmp/dir2
> I've just unmounted and re-mounted it and there was file corruption.
> I've just repeated the test using 2 new directories, /tmp/dir3 and
> /tmp/dir4. Unmounting and remounting immediately shows that they are
> decrypting fine.

Just to be clear, since you said 'decrypting fine':  if you read the
files, they will decrypt fine.  It is only if you append to the file
immediately after mount, and the file is more than one block in size
and not an exact multiple of blocksize (iirc).

If you did mean using append, then that is interesting, bc I've never
had it fail to corrupt a file :)  (or is that :( ).


Hardy ecryptfs can cause data loss
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.

More information about the kernel-bugs mailing list