[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Filesystem Corruption

  • To: Roman ZARAGOCI <roman.zaragoci@xxxxxxxxxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Mon, 10 Sep 2007 17:27:32 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 10 Sep 2007 09:22:26 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=fjPGN8At57V9IQ0MyVBBxV1B2Csm/nQRc6R3HZas9sB2o2Re/GZDue6R0vxsJPy5pp4VuY9yAdfgMk9ZPg7Gg38/pdGp9wQF0hQv10A5KGPBDUrNRffWF4KUNJ8/rvMFxR8rQYaSlF1UoDw1cO77VuViiFkbw7DovefYpdzRTnM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Roman ZARAGOCI wrote:

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 :, compiled from sources.
Linux Xen kernel : 2.6.16
File-System : ext3 w/ LVM
You should be at update 4, or switch directly to RHEL 5 or CentOS 5. Seriously, it's a big improvement in running Xen.

If you *HAVE* to run Xen on RHEL 4 as Dom0, use Xen 3.1.0 from Xensource or something more up to date. Don't consult from sources unless you have to, and unless you feel like upgrading these things yourself all the time.

DomU :
Fedora Core 4 ou 6
Xen :, 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.
What? OK, shut *down* the DomU. Use kpartx to split the file or partition into the filesystems that are on it, if necessary, then mount them directly on the Dom0 to examine. And run fsck on those enabled partitions, as needed.

Does everybody encounters this problem before ?

Do you think that should be caused by using an ext3 (with logging) for
vm's filesystem (wich are using .img files) ?
Unlikely. But why are you doing this instead of using LVM partitions directly, and mounting those either as /dev/sda or as /dev/sda1?

Any suggestions about using caches management for DomU and Dom0 ? (do we
need to delete cache and ext3 logging on DomUs)
It sounds like you need to run fsck.ext3 on the partitions. But do it from Dom0.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.