| Re: OpenVZ 7 containers crashing with ext4 errors [message #53656 is a reply to message #53655] |
Fri, 03 July 2020 16:07   |
khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia
|
Senior Member |
|
|
Hi,
1) update, vz7 update 14 has quite a number of ploop-related fixes (kernel vz7.151.14).
2) if you face this issue again on vz7 u14, please file a bug at bugs.openvz.org
(which full logs, not just a snippet)
3)
Quote:
EXT4-fs: ext4_ext_split:1139: aborting transaction: error 28 in __ext4_handle_dirty_metadata
"error 28" means space shortage
Quote:
#define ENOSPC 28 /* No space left on device */
So please check it ploop usage is close to it's size.
4) i don't know if you have messages like
Quote:
[2040002.704309] Purging lru entry from extent tree for inode 356516155 (map_size=50243 ratio=12612%)
[2040002.704318] max_extent_map_pages=16384 is too low for ploop_io_images_size=7914092756992 bytes
if you do, increase the following parameter, say by 10 times
/sys/module/pio_direct/parameters/max_extent_map_pages
and check if it helps.
The increase can be done on the fly, no reboot required.
But first of all - update!
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
