Comment 2 for bug 390833
Revision history for this message
| Tyler A (alias-ecryptsfs) wrote Re: du reports newly created files on ecryptfs as empty | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I just wanted to add to this discussion/report my own experience with this bug. It seems that the issue occurs not just between sync, but even after a reboot/remount.
I have an ecryptfs-mounted home directory, within which everything appears to be 0 bytes. However, I *can* read the files and they appear to have valid contents, it's just that they're misreported by "du" etc
However, as a test I did a similar "dd" from /dev/zero and created a file of approx 2mb. Even after rebooting the machine and remounting the cryptfs partition, "du" still displays the filesize as 0 bytes. As such, it would appear that this issue isn't related to just new files still in memory, as it was long since flushed to disk.
The machine I'm testing on at this particular moment has a kernel that's a few versions behind the latest, so I'll re-post here if the bug goes away after I finish compiling/
Cheers,
Tyler