https://bugzilla.kernel.org/show_bug.cgi?id=89621 Michal Cihar <michal@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michal@xxxxxxxxx --- Comment #8 from Michal Cihar <michal@xxxxxxxxx> --- I've seen this several times as well. All cases were after upgrade to Debian Jessie with 3.16.0 kernel running in KVM. The host kernel is unchanged, so I'm pretty sure the guest kernel is guilty here. The host does LVM + RAID, the guest just gets virtio based disk so nothing complex on it's side. The error in my case: [149757.256024] EXT4-fs (vda1): pa ffff88001c92bd90: logic 0, phys. 1944064, len 64 [149757.323573] EXT4-fs error (device vda1): ext4_mb_release_inode_pa:3773: group 59, free 4, pa_free 2 [149757.349776] Aborting journal on device vda1-8. [149757.386808] EXT4-fs (vda1): Remounting filesystem read-only [236229.600081] EXT4-fs (vda1): error count since last fsck: 1 [236229.600086] EXT4-fs (vda1): initial error at time 1432088178: ext4_mb_release_inode_pa:3773 [236229.600088] EXT4-fs (vda1): last error at time 1432088178: ext4_mb_release_inode_pa:3773 I'm not able to reproduce this, but I've already seen the error several times. -- 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
