Hi, no, it is not about the files which are 0bytes in your mounted ecryptfs under /home/user/..., but those encrypted-file-containers that are 0bytes in /home/user/.Private, i.e. intheir encrypted state where something went terribly wrong, and which can't be decrypted anyhow.
What's really missing is a simple option to find out *which* files are broken, so you can restore them from your Backup. (You do backup, don't you ?) Yours, Steffen -----Ursprüngliche Nachricht----- Von: [email protected] im Auftrag von jeyno Gesendet: So 11/14/2010 00:34 An: Neumann, Steffen Betreff: [Bug 372014] Re: errors in dmesg I have this issue too; running Lucid. I'm struggling with the concept that all zero-length files should be deleted. This sounds like ... make sure all the software you design fits the limitation of my filesystem... In my world, zero length files are fairly commonplace. And removing them screws up the systems that depend on them being there. Does this mean ecryptfs is not ready for prime-time? -- errors in dmesg https://bugs.launchpad.net/bugs/372014 You received this bug notification because you are a direct subscriber of the bug. -- errors in dmesg https://bugs.launchpad.net/bugs/372014 You received this bug notification because you are a member of Registry Administrators, which is the registrant for NULL Project. _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : [email protected] Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
