Public bug reported:
Binary package hint: qemu-kvm
Hi,
I'm getting log messages about file system recovery operations when
rebooting KVM VMs. This does happen on most (but not all) reboots.
System Information:
Host-OS: Ubuntu Ubuntu 9.10 and Ubuntu 10.04 LTS
Guest-OS: Ubuntu 10.04 LTS
Packages: qemu-kvm 0.11.0-0ubuntu6.3 on Karmic and qemu-kvm
0.12.3+noroms-0ubuntu9.1 on Lucid
Here are two typical excerpts from two different guests on different physical
hosts. Symptoms are similar for ext3 and ext4 file Systems:
-------------------------------------------------------
May 29 09:22:14 machine1 kernel: [ 0.857569] EXT3-fs: INFO: recovery
required on readonly filesystem.
May 29 09:22:14 machine1 kernel: [ 0.857573] EXT3-fs: write access will be
enabled during recovery.
May 29 09:22:14 machine1 kernel: [ 3.071081] kjournald starting. Commit
interval 5 seconds
May 29 09:22:14 machine1 kernel: [ 3.071100] EXT3-fs: sda1: orphan cleanup
on readonly fs
May 29 09:22:14 machine1 kernel: [ 3.071419] ext3_orphan_cleanup: deleting
unreferenced inode 209922
May 29 09:22:14 machine1 kernel: [ 3.071507] ext3_orphan_cleanup: deleting
unreferenced inode 209919
May 29 09:22:14 machine1 kernel: [ 3.071518] ext3_orphan_cleanup: deleting
unreferenced inode 209918
May 29 09:22:14 machine1 kernel: [ 3.077659] ext3_orphan_cleanup: deleting
unreferenced inode 209917
May 29 09:22:14 machine1 kernel: [ 3.093245] ext3_orphan_cleanup: deleting
unreferenced inode 209914
May 29 09:22:14 machine1 kernel: [ 3.093256] ext3_orphan_cleanup: deleting
unreferenced inode 209912
May 29 09:22:14 machine1 kernel: [ 3.099964] ext3_orphan_cleanup: deleting
unreferenced inode 209910
May 29 09:22:14 machine1 kernel: [ 3.099975] ext3_orphan_cleanup: deleting
unreferenced inode 209909
May 29 09:22:14 machine1 kernel: [ 3.107290] ext3_orphan_cleanup: deleting
unreferenced inode 209906
May 29 09:22:14 machine1 kernel: [ 3.107300] ext3_orphan_cleanup: deleting
unreferenced inode 209905
May 29 09:22:14 machine1 kernel: [ 3.107310] ext3_orphan_cleanup: deleting
unreferenced inode 209903
May 29 09:22:14 machine1 kernel: [ 3.117795] ext3_orphan_cleanup: deleting
unreferenced inode 209900
May 29 09:22:14 machine1 kernel: [ 3.133337] EXT3-fs: sda1: 12 orphan inodes
deleted
May 29 09:22:14 machine1 kernel: [ 3.133344] EXT3-fs: recovery complete.
May 29 09:22:14 machine1 kernel: [ 3.144669] EXT3-fs: mounted filesystem
with ordered data mode.
-------------------------------------------------------
Jun 28 22:33:17 machine2 kernel: [ 0.678191] EXT4-fs (vda1): INFO: recovery
required on readonly filesystem
Jun 28 22:33:17 machine2 kernel: [ 0.678202] EXT4-fs (vda1): write access
will be enabled during recovery
Jun 28 22:33:17 machine2 kernel: [ 1.403991] EXT4-fs (vda1): orphan cleanup
on readonly fs
Jun 28 22:33:17 machine2 kernel: [ 1.404012] EXT4-fs (vda1):
ext4_orphan_cleanup: deleting unreferenced inode 1703942
Jun 28 22:33:17 machine2 kernel: [ 1.404090] EXT4-fs (vda1):
ext4_orphan_cleanup: deleting unreferenced inode 1703941
Jun 28 22:33:17 machine2 kernel: [ 1.404100] EXT4-fs (vda1):
ext4_orphan_cleanup: deleting unreferenced inode 1703940
Jun 28 22:33:17 machine2 kernel: [ 1.404107] EXT4-fs (vda1):
ext4_orphan_cleanup: deleting unreferenced inode 1703939
Jun 28 22:33:17 machine2 kernel: [ 1.404115] EXT4-fs (vda1):
ext4_orphan_cleanup: deleting unreferenced inode 1703938
Jun 28 22:33:17 machine2 kernel: [ 1.404121] EXT4-fs (vda1): 5 orphan inodes
deleted
Jun 28 22:33:17 machine2 kernel: [ 1.404125] EXT4-fs (vda1): recovery
complete
-------------------------------------------------------
The problem occurs on all VMs on two different physical hosts. Both
hosts use LVM volumes to store the KVM guest's disks. One host uses the
KVM ide bus driver, while the other uses virtio_blk.
There are no observable problems during runtime with any of the VMs, and
there are also no other log messages that would indicate file system or
harddisk problems. I haven't seen this kind of error with Karmic guests
using a similar configuration. The VMs on the first host were in fact
upgraded from Karmic to Lucid, and I can't remember having seen those
errors before upgrading.
If you need any additional information, please let me know.
Regards,
Thomas
** Affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
Ext3/4 orphan cleanup messages on boot
https://bugs.launchpad.net/bugs/605890
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
