device-mapper-multipath/tests/multipathd_oom/PURPOSE
Petr Šabata de5fe16817 RHEL 9.0.0 Alpha bootstrap
The content of this branch was automatically imported from Fedora ELN
with the following as its source:
https://src.fedoraproject.org/rpms/device-mapper-multipath#2cf40b2f98808e3533e915c0a204b885d9da5e43
2020-10-14 23:36:17 +02:00

15 lines
747 B
Plaintext

the oom_adj is -17 and oom_score_adj is -1000 after installing device-mapper-multipath-0.4.9-53.el6.x86_64 and starting multipathd.
This means multipathd will never be selected to be killed by oom according to the kernel doc.
Here are the steps to reproduce this issue.
1. create a multipathed disk /dev/mapper/mpathb via scsi_debug using all the free memory. this will consume most of the free mem.
2. io stress on the multipath disk, this step is option.
#dd if=/dev/zero of=/dev/mapper/mpathb &
3. consuming the free mem
#for i in `seq 10000`; do array[$i]=$(</var/log/messages); done &
4. trigger the oom_killer manually
#while true; do echo f > /proc/sysrq-trigger ; done
5. check the console or /var/log/message if multipathd is killed