RTEMS VM corrupt?

[Scott Newell]

Has anyone noticed any disk corruption with the Fedora VM?
http://www.rtems.com/wiki/index.php/Virtual_Machines_for_RTEMS_Development

I've been seeing odd errors and lockups.  I thought it might be from 
the failed "yum -y update" (ran out of disk space), so I went back 
and unzipped a fresh copy, ran md5sum on it, then booted it and did a 
fsck.  Results below.

Comments?

$ md5sum C++.vmdk
e258ad60c3bcd3e82f4b0d6484fc9a51 *C++.vmdk

Here's the output from fsck -n:

fsck from util-linux-ng 2.16.2
Warning!  /dev/mapper/VolGroup-lv_root is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/mapper/VolGroup-lv_root contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (2371714, counted=2372087).
Fix? no

Free inodes count wrong (685078, counted=684969).
Fix? no


/dev/mapper/VolGroup-lv_root: ********** WARNING: Filesystem still 
has errors **********

/dev/mapper/VolGroup-lv_root: 222458/907536 files (0.1% 
non-contiguous), 1253246/3624960 blocks