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

Re: [Xen-users] disk image corruption

  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Justin Tianen" <jtianen@xxxxxxxxxx>
  • Date: Tue, 2 Jun 2009 09:43:41 -0500
  • Delivery-date: Tue, 02 Jun 2009 07:44:29 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcnjkIeZnNxdkdgRSfWb9D5PRflwLA==
  • Thread-topic: Re: [Xen-users] disk image corruption

I’m going through the logs right now looking for something more specific (however, I don’t know the time of day the disk remounts outside of usually during the rsync backup). I’ve already gone ahead and staggered the backup launch times to see if that helps at all. The filesystem mounting issue relates only to those being handled as block devices (sda1) which I’m not doing. Here’s what the domU configs all look like (differences are the names, uuid, vif mac, and disk image name).


name = "server1"

uuid = "52fa8774-020d-d66c-d47c-f1b3ecb66417"

maxmem = 1250

memory = 1250

vcpus = 1

bootloader = "/usr/bin/pygrub"




vfb = [  ]

disk = [ "tap:aio:/vm/ server1.img,xvda,w" ]

vif = [ "mac=00:16:3e:12:b6:bf,bridge=xenbr0" ]


This is all being ran on a CentOS 5.3 server (and each domU is also CentOS 5.3). All 3 domU were setup via the Python script “virt-install” that is included in the CentOS version of Xen.

Xen-users mailing list



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