The relation to that upstream bug is tenuous at best. The upstream bug:
- is reported against a newer kernel than the one we're shipping
- is reported to only happen when ext4 is on top of the DM layer, whereas Scott's case was ext4 on a raw device
- is reported in connection with an unclean shutdown and subsequent fsck, whereas Scott reported corruption of files without an unclean shutdown (but no mention in this bug of whether the corruption requires an intervening reboot/fsck to appear - Scott, please clarify)
So that upstream bug link should be dropped; it really doesn't look like the same bug.
Neumarke,
The relation to that upstream bug is tenuous at best. The upstream bug:
- is reported against a newer kernel than the one we're shipping
- is reported to only happen when ext4 is on top of the DM layer, whereas Scott's case was ext4 on a raw device
- is reported in connection with an unclean shutdown and subsequent fsck, whereas Scott reported corruption of files without an unclean shutdown (but no mention in this bug of whether the corruption requires an intervening reboot/fsck to appear - Scott, please clarify)
So that upstream bug link should be dropped; it really doesn't look like the same bug.