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 logging) 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@lists.xensource.com http://lists.xensource.com/xen-users
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 logging) 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@lists.xensource.com http://lists.xensource.com/xen-users
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 logging) 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@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Roman ZARAGOCI schrieb:> Nobody can help me about this fatal problems ? Our servers are all in a > production network.Does the corruption happen after an unclean dom0 shutdown/crash, or during a normal operation as well? In any case, using loop/files for keeping domU data is a really really bad idea. -- Tomasz Chmielewski http://wpkg.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Roman ZARAGOCI wrote:> Nobody can help me about this fatal problems ? Our servers are all in > a production network. >If you need a guarantee that someone will handle your problem, especially when in production envirenment, you should consider commercial offerings, like the one from XenSource.> I can give more information about whatever you want. > > Roman ZARAGOCI a écrit : >> >> Any suggestions about using caches management for DomU and Dom0 ? (do we >> need to delete cache and ext3 logging on DomUs) >> >>You should use LVM (recommended) or partitions as storage for domU fs. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,> Our virtual machines have some filesystem corruption problems. > The filesystem is being mounted on read-only mode.[...]> 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.I don''t understand, if you mount read only, why should there be any write order to guarantee ? Mehdi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Roman,>> Our virtual machines have some filesystem corruption problems. >> The filesystem is being mounted on read-only mode. When running fsck >> command, everything goes ok.I had this one time that in DomU a partition went read-only during normal operation. fsck didn''t find any errors as well. In the end, this was bad hardware, you may read my posts in this lists'' archive: They were all because of bad hardware. Our new servers run under full load without any errors since months. Remember: The filesystem-driver holds parts of the fs'' metadata in memory. If the structure is getting corrupt, the driver will refuse to write any block to the harddisk, so the filesystem on disk stays clean. If it wouldn''t refuse writes when there are corrupt fs structures in memory, this would surely end in bad damage on the disk. cu cp -- Die Homepage meines Vertrauens: www.cpur.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Roman ZARAGOCI wrote:> 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/ LVMYou 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 : 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.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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users