I have now tested mainline kernel 2.6.33-999.201003071003 (i386) and have experienced absolutely NO filesystem corruption under it.
Rebooting from 2.6.33 to 2.6.32-16.24 resulted in the following error:
EXT4-fs error (device sda1): ext4_lookup; deleted inode referenced: 3409181 Aborting journal on device sda1-8. EXT4-fs error (device sda1): ext4_journal_start_sb: Detected aborted journal EXT4-fs (sda1): Remounting filesystem read-only EXT4-fs (sda1): Remounting filesystem read-only
This last error has occurred only once, and followed a clean shutdown. Using the Alternate CD recovery mode to run e2fsck allowed journal replay, and no further errors have been detected under 2.6.32-16.24.
I have now tested mainline kernel 2.6.33- 999.20100307100 3 (i386) and have experienced absolutely NO filesystem corruption under it.
Rebooting from 2.6.33 to 2.6.32-16.24 resulted in the following error:
EXT4-fs error (device sda1): ext4_lookup; deleted inode referenced: 3409181 start_sb: Detected aborted journal
Aborting journal on device sda1-8.
EXT4-fs error (device sda1): ext4_journal_
EXT4-fs (sda1): Remounting filesystem read-only
EXT4-fs (sda1): Remounting filesystem read-only
This last error has occurred only once, and followed a clean shutdown. Using the Alternate CD recovery mode to run e2fsck allowed journal replay, and no further errors have been detected under 2.6.32-16.24.