> What about the damage that's already been done to files
The damage is temporary and disappears as soon as you unmount the ecryptfs volume, unless you for some reason read the file and write it back to disk.
I wrote a script that fixes up git objects broken by this bug: https://bugs.launchpad.net/ecryptfs/+bug/509180/comments/41
If you have any non-git files that are affected by this, you might want to do something similar based on the script.
> Mine is. I've upgraded to natty and my dmesg is still full of those errors.
I think the dmesg errors are just one symptom of the bug; trailing garbage is another. Can you still see trailing garbage in any of your files?
> What about the damage that's already been done to files
The damage is temporary and disappears as soon as you unmount the ecryptfs volume, unless you for some reason read the file and write it back to disk.
I wrote a script that fixes up git objects broken by this bug: https:/ /bugs.launchpad .net/ecryptfs/ +bug/509180/ comments/ 41
If you have any non-git files that are affected by this, you might want to do something similar based on the script.
> Mine is. I've upgraded to natty and my dmesg is still full of those errors.
I think the dmesg errors are just one symptom of the bug; trailing garbage is another. Can you still see trailing garbage in any of your files?