https://bugzilla.kernel.org/show_bug.cgi?id=89621 --- Comment #4 from John Hughes <john@xxxxxxxxx> --- I've seen it 3 times so far. Once on boot, I ran fsck, the error has not come back (so far). Once (on another, but similarly configured VM) the error came back almost immediately after being fixed by fsck. A second run of fsck and no problems so far. I'm not running any odd drivers in these VM's. The host of one of them has an Eicon DIVA card with it's drivers, the host of the other doesn't. The strangest part of my setup is that I have an mdadm raid1 on the host system, that is made available as a virtio block device to a guest (running under LVM). In the guest I have LVM2 volumes, with ext3 formatted filesystems. Everything is now running this 3.16 Debian kernel. One filesystem was mounted with data=journal, the other is the root filesystem mounted with the default data=ordered. barriers are not explicitly disabled so they should be enabled by default by now (yes?) The virtio block devices have cache=none. I'll try to schedule the installation of a more up-to-date kernel on at least one of the machines, but it may take me a few days. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
