From: baotiao <baotiao@gmail.com>
To: xfs@oss.sgi.com
Subject: XFS: possible memory allocation deadlock in kmem_alloc
Date: Mon, 30 May 2016 12:45:07 +0800 [thread overview]
Message-ID: <AD1240BA-DB24-44F2-893D-28A824063F99@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2557 bytes --]
Hello.
we have experience this problem many time, and we try many ways to solve this problem, but always failed.
such as sync && echo 3 > /proc/sys/vm/drop_caches to free more memory, however, after a while, the message come again.
the dmesg show:
May 30 12:35:51 w-openstack21 kernel: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)
May 30 12:35:53 w-openstack21 kernel: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)
May 30 12:35:55 w-openstack21 kernel: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)
May 30 12:35:57 w-openstack21 kernel: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)
May 30 12:35:59 w-openstack21 kernel: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)
our kernel version is 3.10.0-327.4.5.el7.x86_64
we think this is the kernel memory fragmentation problem, when dmesg show the error message, we check the buddyinfo
[root@w-openstack21 /home/xusiliang]# cat /proc/buddyinfo
Node 0, zone DMA 1 0 1 0 2 1 1 0 1 1 3
Node 0, zone DMA32 2190 1898 1367 583 284 81 21 8 5 0 4
Node 0, zone Normal 85195 90572 56688 32379 16793 5568 930 230 184 11 0
Node 1, zone Normal 95799 127034 94363 49321 21555 5239 225 2 2 0 0
and I think the kernel have enough free memory
[root@w-openstack21 /home/xusiliang]# free -m
total used free shared buff/cache available
Mem: 64269 50357 11802 65 2109 11757
Swap: 32255 347 31908
This machine is running for qemu, the file is qemu qcow file type
[root@w-openstack20 /data/nova/instances/7898b630-c4ef-49ab-9ce9-3735e090c282]# file disk
disk: QEMU QCOW Image (v3), has backing file (path /data/nova/instances/_base/3f27393376152ac352b2d85703011e38517e), 429496729600 bytes
we also use xfs_db to check the fragmentation
[root@w-openstack20 /home/xusiliang]# xfs_db -r /dev/mapper/VolGroup00-LogVol04
xfs_db> frag
actual 48421430, ideal 20716, fragmentation factor 99.96%
How can I solve this problem, what do you suggest me to do?
thank you
----------------------------------------
Github: https://github.com/baotiao
Blog: http://baotiao.github.io
Stackoverflow: http://stackoverflow.com/users/634415/baotiao
Linkedin: http://www.linkedin.com/profile/view?id=145231990
[-- Attachment #1.2: Type: text/html, Size: 6916 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-05-30 4:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 4:45 baotiao [this message]
2016-05-30 5:04 ` XFS: possible memory allocation deadlock in kmem_alloc Dave Chinner
2016-05-30 8:48 ` baotiao
2016-05-30 9:20 ` Carlos Maiolino
2016-05-31 2:43 ` 陈宗志
2016-05-31 3:10 ` Dave Chinner
2016-05-31 11:00 ` 陈宗志
2016-05-31 12:14 ` Carlos Maiolino
-- strict thread matches above, loose matches on Subject: below --
2019-11-04 23:38 Chris Holcombe
2019-11-05 0:01 ` Darrick J. Wong
2019-11-05 0:31 ` Eric Sandeen
[not found] ` <CAC752AmahECFry9x=pvqDkwQUj1PEJjoWGa2KFG1uaTzT1Bbnw@mail.gmail.com>
2019-11-05 4:21 ` Eric Sandeen
2019-11-05 16:25 ` Chris Holcombe
2019-11-05 17:11 ` Eric Sandeen
2019-11-05 19:53 ` Chris Holcombe
2019-11-05 20:08 ` Eric Sandeen
[not found] ` <CAC752AnZ4biDGk6V17URQm5YVp=MwZBhiMH8=t733zaypxUsmA@mail.gmail.com>
2019-11-05 20:47 ` Eric Sandeen
[not found] ` <CAC752A=y9PMEQ1e4mXskha1GFeKXWi8PsdBW-nX40pgFCYp1Uw@mail.gmail.com>
2019-11-05 21:23 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AD1240BA-DB24-44F2-893D-28A824063F99@gmail.com \
--to=baotiao@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox