ecryptfs team mailing list archive

[Dustin Kirkland <dustin.kirkland@xxxxxxxxx>]

Hello, thanks for the bug report.

I'll leave the definitive answer to Tyler Hicks, the upstream kernel
maintainer, but I'll try to field this question as best as I can.

Basically, there is a bit of time where the new file exists only in
kernel memory, before it gets synced to disk.  You might try running
"sync", and seeing if it gets flushed.

Tyler, can you provide some more information?

:-Dustin

** Package changed: ubuntu => ecryptfs-utils (Ubuntu)

** Changed in: ecryptfs-utils (Ubuntu)
       Status: New => Invalid

** Changed in: ecryptfs
       Status: New => Invalid

** Changed in: ecryptfs
       Status: Invalid => New

** Changed in: ecryptfs
       Status: New => Invalid

** Converted to question:
   https://answers.edge.launchpad.net/ecryptfs/+question/75055

-- 
du reports newly created files on ecryptfs as empty
https://bugs.launchpad.net/bugs/390833
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in eCryptfs - Enterprise Cryptographic Filesystem: Invalid
Status in “ecryptfs-utils” source package in Ubuntu: Invalid

Bug description:
I'm using an encrypted home directory on Ubuntu Jaunty. When I create a new file in my home directory or copy and existing file/folder, du shows its size as zero bytes:

das@serenity ~ > dd if=/dev/zero of=test bs=1024 count=1024
1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB) copied, 0.114302 s, 9.2 MB/s
das@serenity ~ > du test
0	test
das@serenity ~ > ll test
-rw-r--r-- 1 das das 1048576 2009-06-22 22:14 test

du keeps reporting a size of zero bytes until the encrypted directory is remounted. After that, the output seems to be correct.