Comment 15 for bug 198125

Any chance this might be related to disk image corruption issues when running Hardy in VmWare Fusion?

I have lost numerous VmWare Fusion images with what seems to be a similar problem. Typically in the middle of a large project build, everything will come to a grinding halt with (something like) the following error:

[ 3380.587304] EXT3-fs error (device sda1): htree_dirblock_to_tree: bad entry in directory #1777878: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
[ 3380.587411] Aborting journal on device sda1.
[ 3380.588457] Remounting filesystem read-only
[ 3380.664339] __journal_remove_journal_head: freeing b_committed_data

After rebooting the virtual Hardy machine, the disk is generally unbootable. I use suspend/resume all the time in VmWare, but thought this was some strange VmWare I/O problem happening during my build. Now I'm wondering if it's a Hardy bug?