virtual machines hosted on ext4 filesystem host crash

[corrosion]

I reported this bug into ubuntuforums to aware other users, here is a copy:

"Last week I was becoming crazy because 2 virtual machines were shutting down unexpectedly. I found that it happened every time I tried to move large files via networking from virtual machines to host machine (NFS, FTP) or from virtual machine to virtual machine. Since my server has 3 big hdds, i formatted one into ext3 (all of them were ext4) and moved the virtual machines into the ext3 hard disk. It was like magic. No more problems.
I post this here in the hope it can be useful for someone and I will look how to notify about this problem to vmware/ubuntu.

Regards,"

Maybe it is related with other ext4 problems reported, I looked into there but didn't find a bug to "attach" this. If you need more information, please, ask.
Thankyou very much.

Node information:
ProblemType: Bug
Architecture: amd64
Date: Sun Nov 15 19:35:49 2009
Dependencies:
 adduser 3.110ubuntu6
 base-files 5.0.0ubuntu7
 base-passwd 3.5.21
 busybox-initramfs 1:1.13.3-1ubuntu7
 coreutils 7.4-2ubuntu1
 cpio 2.10-1ubuntu1
 debconf 1.5.27ubuntu2
 debconf-i18n 1.5.27ubuntu2
 debianutils 2.30ubuntu3
 dpkg 1.15.4ubuntu2
 findutils 4.4.2-1
 gcc-4.4-base 4.4.1-4ubuntu8
 initramfs-tools 0.92bubuntu53
 klibc-utils 1.5.15-1ubuntu2
 libacl1 2.2.47-2
 libattr1 1:2.4.43-3
 libblkid1 2.16-1ubuntu5
 libc-bin 2.10.1-0ubuntu15
 libc6 2.10.1-0ubuntu15
 libdb4.7 4.7.25-7ubuntu2
 libgcc1 1:4.4.1-4ubuntu8
 libglib2.0-0 2.22.2-0ubuntu1
 libklibc 1.5.15-1ubuntu2
 liblocale-gettext-perl 1.05-4build1
 libncurses5 5.7+20090803-2ubuntu2
 libpam-modules 1.1.0-2ubuntu1
 libpam-runtime 1.1.0-2ubuntu1
 libpam0g 1.1.0-2ubuntu1
 libpcre3 7.8-3
 libselinux1 2.0.85-2ubuntu2
 libslang2 2.1.4-3
 libstdc++6 4.4.1-4ubuntu8
 libtext-charwidth-perl 0.04-5build1
 libtext-iconv-perl 1.7-1build1
 libtext-wrapi18n-perl 0.06-7
 libusb-0.1-4 2:0.1.12-13
 libuuid1 2.16-1ubuntu5
 lsb-base 4.0-0ubuntu5
 lzma 4.43-14ubuntu1
 module-init-tools 3.10-3
 ncurses-bin 5.7+20090803-2ubuntu2
 passwd 1:4.1.4.1-1ubuntu2
 perl-base 5.10.0-24ubuntu4
 procps 1:3.2.8-1ubuntu3
 sed 4.2.1-1
 tzdata 2009r-0ubuntu9.10
 udev 147~-6.1
 util-linux 2.16-1ubuntu5
 wireless-crda 1.10
 zlib1g 1:1.2.3.3.dfsg-13ubuntu3
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: vmnet vmci vmmon
Package: linux-image-2.6.31-14-server 2.6.31-14.48
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-server
SourcePackage: linux
Uname: Linux 2.6.31-14-server x86_64

[Jeremy Foshee (jeremyfoshee)]

Hi corrosion,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 483202

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]