← Back to team overview

registry team mailing list archive

[Bug 574665] Re: kvm + virtio disk corrupts large volumes (>1TB).

 

I patched qemu-kvm (0.12.3+noroms-0ubuntu9) with patch
(http://marc.info/?l=qemu-devel&m=127436114712437) and compiled but
still my 4TB partition corrupts.

I have setup where I have 4TB partition (from LVM) as a virtio-device in qemu-kvm. I have LVM also inside virtual machine and having 4GB partition as root and rest of 4TB used as a data-partition:
<-->
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/rootvg-root
                       9611492   3144132   5979120  35% /
none                    505832       172    505660   1% /dev
none                    511844         0    511844   0% /dev/shm
none                    511844        92    511752   1% /var/run
none                    511844         0    511844   0% /var/lock
none                    511844         0    511844   0% /lib/init/rw
/dev/mapper/rootvg-storage
                     4216750656 1325906868 2890843788  32% /storage
/dev/vda3               217347     21434    184691  11% /boot
<-->

Still my virtualmachine  seems to corrupt my virtual disk and gives
following error to dmesg:

[  325.052492] EXT4-fs error (device dm-2): ext4_mb_generate_buddy: EXT4-fs: group 9708: 27488 blocks in bitmap, 32768 in gd
[  325.273227] Aborting journal on device dm-2-8.
[  325.457530] EXT4-fs error (device dm-2): ext4_journal_start_sb: Detected aborted journal
[  325.704655] EXT4-fs (dm-2): Remounting filesystem read-only
[  325.854758] EXT4-fs (dm-2): Remounting filesystem read-only
[  326.057791] EXT4-fs (dm-2): delayed block allocation failed for inode 81264677 at logical offset 102400 with max blocks 19767 with error -30
[  326.385331]
[  326.385358] This should not happen!!  Data will be lost
[  326.575336] EXT4-fs (dm-2): ext4_da_writepages: jbd2_start: 19767 pages, ino 81264677; err -30

-- 
kvm + virtio disk corrupts large volumes (>1TB).
https://bugs.launchpad.net/bugs/574665
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for KVM.