Same problem here. Using an ecryptfs folder on a btrfs filesystem. Running on Arch Linux though.
When copying files using nautilus or nemo into the ecryptfs folder, they often seem to get truncated to 0 bytes length. This does not happen when using "cp" from the terminal.
I get the following error when trying to read such a file:
Valid eCryptfs headers not found in file header region or xattr region, inode xxxxx
Unmounting and remounting the encrypted filesystem makes broken files show with the correct filesize again. But opening them gives an I/O read error then. So I have to delete them finally.
Same problem here. Using an ecryptfs folder on a btrfs filesystem. Running on Arch Linux though.
When copying files using nautilus or nemo into the ecryptfs folder, they often seem to get truncated to 0 bytes length. This does not happen when using "cp" from the terminal.
I get the following error when trying to read such a file:
Valid eCryptfs headers not found in file header region or xattr region, inode xxxxx
I have to delete the file in order to get rid of the error message, just as described at http:// blog.stephenn. com/2012/ 04/problem- with-corrupt- files-and- ecrypt. html.
Unmounting and remounting the encrypted filesystem makes broken files show with the correct filesize again. But opening them gives an I/O read error then. So I have to delete them finally.
Kernel 3.15.8-1-ARCH (x86_64)
ecryptfs-utils 103-2