Comment 150 for bug 509180

I'd like to point out that I am seeing data corruption events due to this issue. It appears that once the files are mangled they cannot be decrypted and end up showing up as null. This is a very serious problem as there is no way to retrieve the data.

A quick search with `find ~ -type f -exec tail -n1 {} \; > /dev/null' indicates a large number of frequently written configuration files, database files and temporary lock files which are now unreadable with -EIO error returned.