← Back to team overview

ecryptfs team mailing list archive

[Bug 390833] Re: du reports newly created files on ecryptfs as empty

 

I'm also having this problem on Jaunty:

$ mount | grep home
/dev/mapper/MAIN_VG-HOME_LV_crypt on /home type ext3 (rw)
/home/user/.Private on /home/user type ecryptfs (ecryptfs_sig=ace5d3dc7966c556,ecryptfs_fnek_sig=c0bd3cca6d89c7fd,ecryptfs_cipher=aes,ecryptfs_key_bytes=16)
gvfs-fuse-daemon on /home/user/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=user)
$ dd if=/dev/zero of=test123 count=234333
234333+0 records in
234333+0 records out
119978496 bytes (120 MB) copied, 10.1632 s, 11.8 MB/s
$ du -sh test123
0	test123

Note, it happens with newly created files or directories. It doesn't
matter what they're created by...I noticed this when I was creating a
very large Lucene index yet du was telling me the directory was empty.

In my case, the index directory actually did show size after a
reboot...but it took the reboot to make it happen.

Please, please, if there's any way, issue a patch for this. It's very
frustrating, and I really don't have the option of redoing my home
directory at the moment.

Thanks!

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

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.