Hi everyone. I've noticed that my iotop is showing the following:
TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND
7252 be/3 root 0.00 B/s 3.83 K/s 0.00 % 99.99 % [jbd2/loop0-8]
249 be/3 root 0.00 B/s 0.00 B/s 0.00 % 99.99 % [jbd2/md2-8]
Doing some debugging with
echo 1 > /sys/kernel/debug/tracing/events/ext4/ext4_sync_file_enter/enable
and checking file
/sys/kernel/debug/tracing/trace_pipe
I've noticed that every send there is sync for mysql and loop0 which is probably single LXC container - currently in RAW format, created through proxmox (version 4,4 - running under Debian 8).
Whole VM is terribly slow and disk i/o is causing problems. What options do I have and how to solve this? I've read on forums that some people switched from raw to chroot and that helped?
TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND
7252 be/3 root 0.00 B/s 3.83 K/s 0.00 % 99.99 % [jbd2/loop0-8]
249 be/3 root 0.00 B/s 0.00 B/s 0.00 % 99.99 % [jbd2/md2-8]
Doing some debugging with
echo 1 > /sys/kernel/debug/tracing/events/ext4/ext4_sync_file_enter/enable
and checking file
/sys/kernel/debug/tracing/trace_pipe
I've noticed that every send there is sync for mysql and loop0 which is probably single LXC container - currently in RAW format, created through proxmox (version 4,4 - running under Debian 8).
Whole VM is terribly slow and disk i/o is causing problems. What options do I have and how to solve this? I've read on forums that some people switched from raw to chroot and that helped?