On Sat, Sep 25, 2010 at 2:43 PM, Peter Lieven <pl@xxxxxxx> wrote: > we experience filesystem corruption using virtio-blk on some guest systems togehter with XFS. We still use qemu-kvm 0.12.4. [...] > It seems that 64-bit Ubuntu LTS 10.04.1 is affected as well as an older openSuse 11.1 system with kernel 2.6.27.45-0.1-pae. Suprisingly we have > an openSuse 11.1 with 2.6.27.45-0.1-default working absolutely stable for months. Affected guests: 64-bit Ubuntu LTS 10.04.1, openSuse 11.1 2.6.27.45-0.1-pae Unaffected guests: openSuse 11.1 2.6.27.45-0.1-default qemu-kvm version: 0.12.4 qemu-kvm command-line: ? Disk image format: ? Steps to reproduce: ? Can you please provide information on the unknown items above? Does this happen with IDE (-drive file=myimage.img,if=ide) or only with virtio-blk? > The only thing I have seen in the syslog of the 64-bit Ubuntu LTS 10.04.1 is the following: > > [19001.346897] Filesystem "vda1": XFS internal error xfs_trans_cancel at line 1162 of file /build/buildd/linux-2.6.32/fs/xfs/xfs_trans.c. Caller 0xffffffffa013091d > [19001.346897] > [19002.174492] Pid: 1210, comm: diablo Not tainted 2.6.32-24-server #43-Ubuntu > [19002.174492] Call Trace: > [19002.174492] [<ffffffffa010f403>] xfs_error_report+0x43/0x50 [xfs] > [19002.174492] [<ffffffffa013091d>] ? xfs_create+0x1dd/0x5f0 [xfs] > [19002.174492] [<ffffffffa012bb35>] xfs_trans_cancel+0xf5/0x120 [xfs] > [19002.174492] [<ffffffffa013091d>] xfs_create+0x1dd/0x5f0 [xfs] XFS has given up because of an error in xfs_create() but I don't think this output gives enough information to determine what the error was. Stefan -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
