[Xen-users] Corrupted image file and fsck gives up with "exited with signal 11"

["Juan Rodriguez" <juan.fco.rodriguez@xxxxxxxxx>]

Hello,

I am using a sparse file to hold a Centos5.1 system.

I've got the image file exported to two Xen machines through NSF, and
erroneusly I executed both virtual machines at the same time, I mean,
I executed "xm create <imagefile>" on both machines which I guess mean
that both machines started working on the same image file.

The problem is that the image file now seems to be corrupted and the
VM doesn't boot:

Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VolGroup00/LogVol00
/dev/VolGroup00/LogVol00 contains a file system with errors, check forced.
/dev/VolGroup00/LogVol00: Inode 96339 has a bad extended attribute block 105708.

/dev/VolGroup00/LogVol00: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)
[FAILED]

*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
*** Warning -- SELinux is active
*** Disabling security enforcement for system recovery.
*** Run 'setenforce 1' to reenable.
Give root password for maintenance
(or type Control-D to continue):
(Repair filesystem) 1 #
(Repair filesystem) 1 #
(Repair filesystem) 1 #
(Repair filesystem) 1 #
(Repair filesystem) 1 #
(Repair filesystem) 1 # fsck
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
/dev/VolGroup00/LogVol00 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 96339 has a bad extended attribute block 105708.  Clear<y>? yes

Warning... fsck.ext3 for device /dev/VolGroup00/LogVol00 exited with signal 11.



So, I can not fix the ext3 problem.

What else can I try ?

Thanks in advance



-- 
JFRH

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users