similar to: Filesystem Corruption

Hi all, I am running Xen 3.2-1 / 2.6.18 on Debian Etch (Dom0). I setup a Dom0 with several DomUs (Linux). Each DomU disk is a LV partition. I have been seeing a few mails about backups and LVM and just wanted to make sure that what I am doing is correct. Each DomU with a database has a cron that dumps the db with mysqldump. Later on, Dom0 will do an LVM Snapshot of all DomUs and then do a

Hi! DomUs can be backed up just fine, and there''s no problem to restore files as long as the DomU boots. Now I wonder how to recover hard (desaster recovery)... Backing up the disk images or partitions (from Dom0) seems to be not an option, because there are changes to them all the time, so incremental backups would always save them, and all saves would be inconsistent. Now the idea

Hello, I''m setting up a Xen system since I have diferent choices to create the domU''s partitions: raw partition, lvm, files. I''ve done some tests with hdparm and it all seems to be the same. Can anyone, please, share with me what if the best method. Best regards, Luis _______________________________________________ Xen-users mailing list

Hi All, I just tried to create a DomU using the following method... (I normally use the Xen install kernel when I create CentOS domus, but when I tried that with the PXE image, that had the same effect as below). This is the first time I have created a Fedora domu in ages... years, even. virt-install \ --paravirt \ --name demo \ --ram 500 \

Hi there, during peak load on some running domU, I noticed random iSCSI "Reported LUNs data has changed" which forced me to shutdown the respective domU, re-login the target and do a fsck before starting domU again. This occurred on a 16 core machine, having only about 14 domUs running. Spare memory has been occupied by dom0 (about 40G). Each domU has it''s own iSCSI target.

Chaps, Perhaps this question is a little basic for this list but I''m not really sure of the simplest method or best tool for the job. I''ve created some images with `dd=/dev/zero ....` and I''m using them for the domUs now. Some of them have been running for a few months with no probs. Trouble is that I''d like to create a separate partition within the domU.

Hello all, I''ve been searching through the archives and the internet for a while now, and can''t seem to find anything that helps me out. I hope you don''t my posting this to both xen-users and linux-lvm simultaneously, but i figured it''d help keep the solution in one place... even though it''ll be the same across two places... Anyways: My setup is this:

Hello Everyone. Well i want to write some information (not a complete backup) from my Virtual Machine to the tape drive, but the VM can''t read it. I guess i need to attach this device to the VM so it can read and write the tape driver but i don''t know how to do that, i found something similar but with a cd: # xm block-list <vm-id> –long # xm block-detach 1 5632 -f # xm

Hi, I''m running Xen on a Debian Xeon E3110 using the Debian 2.6.26-2-xen kernel. As filesystem for my lvm domU partitions I choosed xfs. I get the following error in kern.log of domU when booting a domU: blkfront: sda2: write barrier op failed blkfront: sda2: barriers disabled end_request: I/O error, dev sda2, sector 0 end_request: I/O error, dev sda2, sector 0 Filesystem

Hi In our office environment few servers mostly database servers and yesterday it happened for one application server(first time) the partion is getting "read only". I was checking the archives, found may be similar kind of issues in the 2007-July archives. But how it has been solved if someone describes me that will be really helpful. In our case, just at the problem started found

Hey, I have rather new installation of xen, dom0 is running ntpd and is perfectly in time. All domU''s are ~23s in future. Running ntpd on the domU''s seem to have no effect, /proc/sys/xen/independent_wallclock appears to have no effect. I''m running xen-unstable and 2.6.16-rc4 in AMD64 box. Any tip would be appricated. Thanks, -- ++ytti

Is there a recommended partitioning for dom0? Here''s what I have planned. /swap 2GB /boot 100MB (ext3) / 5GB (ext3) xenmachines LVM volume group for the remaining diskspace dom0 will install in 5GB / and each domU will have a swap and root logical volume in "xenmachines" Thank you, _______________________________________________ Xen-users mailing list

I need to installa a streaming server for live videos and for video on demand. My choice is red5. Do you think I can use a xen virtual machine to run a streaming service? Or it is better not to virtualize? Sorry for my bad english. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

We run our dom0''s with 128MB of RAM using xen 2.0.6, kernel 2.6.11 for dom0 and domUs, and typically have ~10 domUs per server. All the domU filingsystems are loopback files served from dom0 using the file method. We''ve found that really busy servers sometimes get out of memory problems on dom0. This appears as lots of x-order memory allocation failures with a variable

Hello, I looked through the archives a bit and could not find anything relevant, if you know otherwise please point me in the right direction. I have a ~3T ext3 filesystem on linux software raid that had been behaving corectly for sometime. Not to long ago it gave the following error after trying to mount it: mount: wrong fs type, bad option, bad superblock on /dev/md0, or too many

I have posted in http://vireso.blogspot.com my notes about installing Centos5 (from DVD image) into DomU on OpenSolaris Xen (xen-nv66-2007-06-24). Using OpenSolaris for Dom0 gives such advantage as zfs zvols for "phy" devices in DomUs, so zfs snapshot & zfs send gives you incredible fast and convenient full/incremental backup/restore of full DomUs.

Hi - We have had a raid failure, we have some what recovered but we continue to see the following ext3 message... Apr 17 14:59:14 acnlin84 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0); Apr 17 14:59:14 acnlin84 kernel: Possible IO failure. Since we have experienced several instances of ext3 file system corruption when we lose

Hello, I have a Xen dom0 (Debian Etch running xen 3.0.3) running different domUs. DomUs'' disks are LVM2 volumes. Now I have increased the size of one of these LVM volumes so I have to inform to the corresponding domU that its disk has increased its size (to resize it without unmounting it). How can I do this? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la

I have some Xen systems running Xen-4.1.1, dom0 linux-2.6.38 patched (it''s gentoo''s xen-sources) and domUs running linux-3.0.4 (vanilla sources from kernel.org). Block devices are phy on LVM2 volumes on DRBD-8.3.9 devices. Not immediately after boot, but after some I/O load on the disks I start seeing these in the domUs: blkfront: barrier: empty write xvdb1 op failed blkfront:

I''ve been using lvm under centos to create the backing store for domUs and although the performance seems acceptable it has some shortcomings. The biggest of which is the LVM bug which prevents me from removing an lv (it says it is still mounted and it definitely isnt). I thought this was just a centos bug but it appears to be evident in debian and ubuntu too and I really can''t