ecryptfs team mailing list archive

[Mikko Rantalainen <mikko.rantalainen@xxxxxxxx>]

Thanks for the explanation, Tyler. If the st_blocks field is changed to
reflect the space taken by the underlying (lower) file system, I think
that the header should be definately included in the count. The header
may be "only" 8KB, but it's per file so if you have a huge collection of
small files, the total space taken will be much higher with headers
counted in. For example, the linux-2.6.32-rc6 kernel source contains
30477 files. With overhead of 8 KB per file, the total difference with
and without headers will be 30477*8 KB or about 240MB (the apparent size
for the kernel is 349MB). I'd hope differences that big to be reflected
on the "du" output.

-- 
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: In Progress
Status in “ecryptfs-utils” package in Ubuntu: Triaged

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.