Ext4 Journal checksumming has been a feature for a while but it's been disabled by default, meaning hardly anyone uses it. The developers made it default in 2.6.32-rc. Unfortunately, it is broken, and people have been getting filesystem corruption after a crash or other unclean shutdown (whenever the filesystem journal has corruption).
If you don't understand any of that, this probably does not affect you.
Anyone using ext4 with journal checksumming, including:
- people with stable kernels who have an ext4 fs mounted with the journal_checksum option
- people using 2.6.32-rc*
need to IMMEDIATELY disable it.
- if running 2.6.32-rc, do a controlled reboot into either a) 2.6.31.x or lower, or b) 2.6.32-rc5-git6 or later
- make sure no ext4 filesystems are mounted with the journal_checksum mount option
And, if you've gone through an unclean reboot since booting 2.6.32-rc[1-5], you need to reboot and force a filesystem check by touching /forcefsck.
Long details:
http://bugzilla.kernel.org/show_bug.cgi?id=14354#c167There is an additional patch in comment 123 that's not clearly related but still might be a good idea anyway.