[LU-5131] insanity test 13: ll_ost00_006 invoked oom-killer Created: 02/Jun/14 Updated: 02/Jun/14 Resolved: 02/Jun/14 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.5.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jian Yu | Assignee: | WC Triage |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | dne | ||
| Environment: |
Lustre build: http://build.whamcloud.com/job/lustre-b2_5/60/ |
||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 14159 | ||||||||
| Description |
|
insanity test 13 hit oom failure on OSS as follows: 19:21:59:Lustre: lustre-OST0002: Client lustre-MDT0001-mdtlov_UUID (at 10.1.6.48@tcp) reconnecting 19:21:59:ll_ost00_006 invoked oom-killer: gfp_mask=0xd0, order=0, oom_adj=0, oom_score_adj=0 19:21:59:ll_ost00_006 cpuset=/ mems_allowed=0 19:21:59:Pid: 23907, comm: ll_ost00_006 Not tainted 2.6.32-431.17.1.el6_lustre.g7e33f1f.x86_64 #1 19:21:59:Call Trace: 19:21:59: [<ffffffff810d0211>] ? cpuset_print_task_mems_allowed+0x91/0xb0 19:21:59: [<ffffffff811225c0>] ? dump_header+0x90/0x1b0 19:21:59: [<ffffffff8122781c>] ? security_real_capable_noaudit+0x3c/0x70 19:21:59: [<ffffffff81122a42>] ? oom_kill_process+0x82/0x2a0 19:21:59: [<ffffffff8112293e>] ? select_bad_process+0x9e/0x120 19:21:59: [<ffffffff81122e80>] ? out_of_memory+0x220/0x3c0 19:21:59: [<ffffffff8112f79f>] ? __alloc_pages_nodemask+0x89f/0x8d0 19:21:59: [<ffffffff8116e082>] ? kmem_getpages+0x62/0x170 19:21:59: [<ffffffff8116ec9a>] ? fallback_alloc+0x1ba/0x270 19:21:59: [<ffffffff8116e6ef>] ? cache_grow+0x2cf/0x320 19:21:59: [<ffffffff8116ea19>] ? ____cache_alloc_node+0x99/0x160 19:21:59: [<ffffffff8124bd21>] ? __crypto_alloc_tfm+0x41/0x130 19:21:59: [<ffffffff8116f7e9>] ? __kmalloc+0x189/0x220 19:21:59: [<ffffffff8124bd21>] ? __crypto_alloc_tfm+0x41/0x130 19:21:59: [<ffffffff8124c5ba>] ? crypto_alloc_base+0x5a/0xb0 19:21:59: [<ffffffffa046a2ca>] ? cfs_crypto_hash_alloc+0x7a/0x290 [libcfs] 19:21:59: [<ffffffffa046a5da>] ? cfs_crypto_hash_digest+0x6a/0xf0 [libcfs] 19:21:59: [<ffffffff8116f86c>] ? __kmalloc+0x20c/0x220 19:21:59: [<ffffffffa0fe5473>] ? lustre_msg_calc_cksum+0xd3/0x130 [ptlrpc] 19:21:59: [<ffffffffa101e571>] ? null_authorize+0xa1/0x100 [ptlrpc] 19:21:59: [<ffffffffa100d5d6>] ? sptlrpc_svc_wrap_reply+0x56/0x1c0 [ptlrpc] 19:21:59: [<ffffffffa0fdda2c>] ? ptlrpc_send_reply+0x1fc/0x7f0 [ptlrpc] 19:21:59: [<ffffffffa0ff3f75>] ? ptlrpc_at_check_timed+0xc05/0x1360 [ptlrpc] 19:21:59: [<ffffffffa0fec139>] ? ptlrpc_wait_event+0xa9/0x2d0 [ptlrpc] 19:21:59: [<ffffffffa0ff5ea0>] ? ptlrpc_main+0xbd0/0x1740 [ptlrpc] 19:21:59: [<ffffffffa0ff52d0>] ? ptlrpc_main+0x0/0x1740 [ptlrpc] 19:21:59: [<ffffffff8109ab56>] ? kthread+0x96/0xa0 19:21:59: [<ffffffff8100c20a>] ? child_rip+0xa/0x20 19:21:59: [<ffffffff8109aac0>] ? kthread+0x0/0xa0 19:21:59: [<ffffffff8100c200>] ? child_rip+0x0/0x20 Maloo report: https://maloo.whamcloud.com/test_sets/bd58ba48-e995-11e3-93d5-52540035b04c By searching on Maloo, I found that this failure has only occurred once on Lustre b2_5 branch. It did not occur on other branches. |
| Comments |
| Comment by Di Wang [ 02/Jun/14 ] |
|
Actually we saw that on master too, https://jira.hpdd.intel.com/i#browse/LU-5121 |