[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] virtio-blk XFS corruption

From: Peter Lieven
Subject: [Qemu-devel] virtio-blk XFS corruption
Date: Sat, 25 Sep 2010 15:43:15 +0200

Hi all,

we experience filesystem corruption using virtio-blk on some guest systems 
togehter with XFS. We still use qemu-kvm 0.12.4.
Does someone remember if there has been a fix submitted meanwhile?

It seems that 64-bit Ubuntu LTS 10.04.1 is affected as well as an older 
openSuse 11.1 system with kernel Suprisingly we have
an openSuse 11.1 with working absolutely stable for 

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 
[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]
[19002.174492]  [<ffffffffa013c2e7>] xfs_vn_mknod+0xa7/0x1c0 [xfs]
[19002.174492]  [<ffffffffa013c430>] xfs_vn_create+0x10/0x20 [xfs]
[19002.174492]  [<ffffffff8114fb74>] vfs_create+0xb4/0xe0
[19002.174492]  [<ffffffff8114fc64>] __open_namei_create+0xc4/0x110
[19002.174492]  [<ffffffff8115340b>] do_filp_open+0xa6b/0xba0
[19002.174492]  [<ffffffff8115e6ea>] ? alloc_fd+0x10a/0x150
[19002.174492]  [<ffffffff81142439>] do_sys_open+0x69/0x170
[19002.174492]  [<ffffffff81142580>] sys_open+0x20/0x30
[19002.174492]  [<ffffffff810131b2>] system_call_fastpath+0x16/0x1b
[19002.174492] xfs_force_shutdown(vda1,0x8) called from line 1163 of file 
/build/buildd/linux-2.6.32/fs/xfs/xfs_trans.c.  Return address = 
[19002.211293] Filesystem "vda1": Corruption of in-memory data detected.  
Shutting down filesystem: vda1

I will pull:

and see if it helps here.

Any other ideas?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]