WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Filesystem Corruption

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Filesystem Corruption
From: Roman ZARAGOCI <roman.zaragoci@xxxxxxxxxxxxx>
Date: Fri, 07 Sep 2007 11:49:20 +0200
Delivery-date: Fri, 07 Sep 2007 02:50:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46DED8EA.6050301@xxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <46DED8EA.6050301@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (Windows/20070728)
Nobody can help me about this fatal problems ? Our servers are all in a production network.

I can give more information about whatever you want.

Roman ZARAGOCI a écrit :
Hi,

Our virtual machines have some filesystem corruption problems.
The filesystem is being mounted on read-only mode. When running fsck
command, everything goes ok.

Our configuration
Dom0 :
RHEL4 Update 3
Xen : 3.0.2.2, compiled from sources.
Linux Xen kernel : 2.6.16
File-System : ext3 w/ LVM

DomU :
Fedora Core 4 ou 6
Xen : 3.0.2.2, compiled from sources.
Linux Xen Kernel : 2.6.16
File-System : ext3, w/o LVM

I've read some stuff about risks using an ext3 filesystem with loop
devices, we cannot guarantee the write order on disk between vm's
filesystem and Dom0's filesystem.


Does everybody encounters this problem before ?

Do you think that should be caused by using an ext3 (with journaling on) for
vm's filesystem (wich are using .img files) ?

Any suggestions about using caches management for DomU and Dom0 ? (do we
need to delete cache and ext3 logging on DomUs)


Thanks in advance for your answers.


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



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

<Prev in Thread] Current Thread [Next in Thread>