Comment 42 for bug 870326

Update: I experienced this bug again today. I had a pretty heavy workload with virtual machines and rdp sessions active. Once again, my dmesg log was flooded to the point where I was alerted to "0 disk space remaining" error, and system was unresponsive.

This required an REISUB since all my tty's were flooded with the error and I was unable to shutdown more gracefully.

I've reverted to the stock natty kernel:

$ uname -r
2.6.38-11-generic

temporarily in hopes that that it is not affected. What really bothers me about this bug is that I'd been running the oneiric kernel 3.0.0-11.18 (based on upstream 3.0.4) for some time now without issue. The ecryptfs corruption happened suddenly and in the same timeframe as other users on here and on the ubuntu forums.

See:
http://ubuntuforums.org/showthread.php?t=1857352

Of course the forum closed before we could discuss further!