Comment 6 for bug 209346

Hi,

I can confirm this on Jaunty 2.6.28-11 fully updated...
it had been a week and I have data corruptions each time it happens!!
Once I totally lost "/etc" and had to reinstall. I first thought it was related to the ext4 data loss problem but I reinstalled yesterday everything with ext3 again and even if the result is not as dramatic I still have those random crash-up...
I cannot find a way to reproduce, it just happens after a while...
I haven't lost any personal data yet but that might happened...

in syslog/dmesg the report is this:
[ 5109.838850] EXT3-fs error (device sda1): ext3_free_blocks_sb: bit already cleared for block 9224201
[ 5109.838865] Aborting journal on device sda1.
[ 5109.839318] Remounting filesystem read-only
[ 5109.839558] EXT3-fs error (device sda1) in ext3_free_blocks_sb: Journal has aborted
[ 5109.839567] EXT3-fs error (device sda1) in ext3_reserve_inode_write: Journal has aborted
[ 5109.839572] EXT3-fs error (device sda1) in ext3_truncate: Journal has aborted
[ 5109.839578] EXT3-fs error (device sda1) in ext3_reserve_inode_write: Journal has aborted
[ 5109.839583] EXT3-fs error (device sda1) in ext3_orphan_del: Journal has aborted
[ 5109.839588] EXT3-fs error (device sda1) in ext3_reserve_inode_write: Journal has aborted
[ 5109.852220] __journal_remove_journal_head: freeing b_committed_data

please help!