[LU-4417] Failure on test suite sanity-lfsck test_13: ASSERTION( offset < LUSTRE_MAX_OPCODES ) Created: 27/Dec/13 Updated: 28/Dec/13 Resolved: 27/Dec/13 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | nasf (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 12131 |
| Description |
|
This issue was created by maloo for sarah <sarah@whamcloud.com> This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/7b5ec0d6-6edb-11e3-9dbc-52540035b04c. The sub-test test_13 failed with the following error:
MDS2 console shows: 19:27:13:Lustre: DEBUG MARKER: == sanity-lfsck test 13: LFSCK can repair crashed lmm_oi == 19:26:48 (1388114808) 19:27:13:Lustre: DEBUG MARKER: grep -c /mnt/mds2' ' /proc/mounts 19:27:13:Lustre: DEBUG MARKER: umount -d -f /mnt/mds2 19:27:13:LustreError: 13910:0:(lproc_ptlrpc.c:175:ll_opcode2str()) ASSERTION( offset < LUSTRE_MAX_OPCODES ) failed: offset 4294967295 >= LUSTRE_MAX_OPCODES 87 19:27:13:LustreError: 13910:0:(lproc_ptlrpc.c:175:ll_opcode2str()) LBUG 19:27:13:Pid: 13910, comm: lfsck_layout 19:27:13: 19:27:13:Call Trace: 19:27:13: [<ffffffffa0757895>] libcfs_debug_dumpstack+0x55/0x80 [libcfs] 19:27:13: [<ffffffffa0757e97>] lbug_with_loc+0x47/0xb0 [libcfs] 19:27:13: [<ffffffffa12803b1>] ll_opcode2str+0x131/0x140 [ptlrpc] 19:27:13: [<ffffffffa124b8e1>] after_reply+0x8b1/0xda0 [ptlrpc] 19:27:13: [<ffffffffa1250781>] ptlrpc_check_set+0xf71/0x1b40 [ptlrpc] 19:27:13: [<ffffffff810811e0>] ? process_timeout+0x0/0x10 19:27:13: [<ffffffffa125165a>] ptlrpc_set_wait+0x30a/0x860 [ptlrpc] 19:27:13: [<ffffffff81063990>] ? default_wake_function+0x0/0x20 19:27:13: [<ffffffffa1669a60>] ? lfsck_layout_master_async_interpret+0x0/0x430 [lfsck] 19:27:13: [<ffffffffa166dce9>] lfsck_layout_master_query_others+0x509/0x600 [lfsck] 19:27:13: [<ffffffffa1674ba7>] lfsck_layout_assistant+0x847/0x15b0 [lfsck] 19:27:13: [<ffffffff81063990>] ? default_wake_function+0x0/0x20 19:27:13: [<ffffffffa1674360>] ? lfsck_layout_assistant+0x0/0x15b0 [lfsck] 19:27:13: [<ffffffff81096a36>] kthread+0x96/0xa0 19:27:13: [<ffffffff8100c0ca>] child_rip+0xa/0x20 19:27:13: [<ffffffff810969a0>] ? kthread+0x0/0xa0 19:27:13: [<ffffffff8100c0c0>] ? child_rip+0x0/0x20 19:27:13: 19:27:13:Kernel panic - not syncing: LBUG 19:27:13:Pid: 13910, comm: lfsck_layout Not tainted 2.6.32-358.23.2.el6_lustre.g2851e84.x86_64 #1 19:27:13:Call Trace: 19:27:13: [<ffffffff8150deec>] ? panic+0xa7/0x16f 19:27:13: [<ffffffffa0757eeb>] ? lbug_with_loc+0x9b/0xb0 [libcfs] 19:27:13: [<ffffffffa12803b1>] ? ll_opcode2str+0x131/0x140 [ptlrpc] 19:27:13: [<ffffffffa124b8e1>] ? after_reply+0x8b1/0xda0 [ptlrpc] 19:27:13: [<ffffffffa1250781>] ? ptlrpc_check_set+0xf71/0x1b40 [ptlrpc] 19:27:13: [<ffffffff810811e0>] ? process_timeout+0x0/0x10 19:27:14: [<ffffffffa125165a>] ? ptlrpc_set_wait+0x30a/0x860 [ptlrpc] 19:27:14: [<ffffffff81063990>] ? default_wake_function+0x0/0x20 19:27:14: [<ffffffffa1669a60>] ? lfsck_layout_master_async_interpret+0x0/0x430 [lfsck] 19:27:14: [<ffffffffa166dce9>] ? lfsck_layout_master_query_others+0x509/0x600 [lfsck] 19:27:14: [<ffffffffa1674ba7>] ? lfsck_layout_assistant+0x847/0x15b0 [lfsck] 19:27:14: [<ffffffff81063990>] ? default_wake_function+0x0/0x20 19:27:14: [<ffffffffa1674360>] ? lfsck_layout_assistant+0x0/0x15b0 [lfsck] 19:27:14: [<ffffffff81096a36>] ? kthread+0x96/0xa0 19:27:14: [<ffffffff8100c0ca>] ? child_rip+0xa/0x20 19:27:14: [<ffffffff810969a0>] ? kthread+0x0/0xa0 19:27:14: [<ffffffff8100c0c0>] ? child_rip+0x0/0x20 19:27:14:Initializing cgroup subsys cpuset 19:27:14:Initializing cgroup subsys cpu |
| Comments |
| Comment by Andreas Dilger [ 27/Dec/13 ] |
|
Looks like a bug in the LFSCK patch series ? |
| Comment by Sarah Liu [ 27/Dec/13 ] |
|
Hi Andreas, yes it is in the patch series and I will close it now, thanks. |
| Comment by Sarah Liu [ 27/Dec/13 ] |
|
this is a bug in patch #7524 |
| Comment by nasf (Inactive) [ 28/Dec/13 ] |
|
It is an known LFSCK bug in the patch http://review.whamcloud.com/#/c/8623/4, I will resubmit patch to fix it. |