I have not been able to pinpoint the problem, but can
usually reproduce it with the following actions:
1. Create 2 unique eCryptfs symmetric key mount points
2. Write a new file into the first mount point
3. Write a new file into the second mount point
4. Write a new file into the first mount point
Step 4 should return with EINVAL (invalid argument) and
a zero length file will be...
2006-07-19 19:14:04 UTC in eCryptfs
