This has been tracked in various other bugs and is fixed in recent
kernels. Sorry for the confusion of this bug not being marked as a dupe
of one of the others. There were a few specific bugs that culminated
into the broader problem reported in this bug.
The way eCryptfs handled full disk situations and opening lower files
that didn't contain the proper eCryptfs metadata has changed over the
course of time but here are the relevant patches that have went upstream
to address the issues mentioned in this bug report:
821f749 eCryptfs: Revert to a writethrough cache model
e3ccaa9 eCryptfs: Initialize empty lower files when opening them
8bc2d3c eCryptfs: Unlink lower inode when ecryptfs_create() fails
For Ubuntu users, these fixes have all been picked up in the 12.04 LTS
kernels.
** Changed in: ecryptfs
Importance: Undecided => High
** Changed in: ecryptfs
Status: New => Fix Released
** Changed in: ecryptfs-utils (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957843
Title:
files in eCryptFS Private directory get corrupted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ecryptfs/+bug/957843/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
