https://bugzilla.kernel.org/show_bug.cgi?id=118511 Navin <navinp1912@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |navinp1912@xxxxxxxxx --- Comment #1 from Navin <navinp1912@xxxxxxxxx> --- Can you check the memory state of Host/Hypervisor if is full around the range [596476,596478.] so that 596477.535490 when ext4_bio_write_page is not able to get memory ? If your hypervisor is using encryption then this patch may help (already present in 4.6 mainline) https://patchwork.ozlabs.org/patch/602204/ If that doesn't work then ,You need to your system stats logged and check and check when ENOMEM is returned. It could genuinely out of memory or there could be something wrong with code. Hypervisor/Host cannot write/commit/allocate buffers because it is out of memory. Hence your guest is in a transient state where the change are not committed and most probably journal is aborted. [[Hypervisor]] [596477.535490] ext4_bio_write_page: ret = -12 http://lxr.free-electrons.com/source/include/uapi/asm-generic/errno-base.h#L15 15 #define ENOMEM 12 /* Out of memory */ -- 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
