[LU-1942] 2.1.3<->2.3 Test failure on test suite sanity-benchmark, subtest test_fsx Created: 14/Sep/12 Updated: 17/Apr/17 Resolved: 17/Apr/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.4.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Maloo | Assignee: | Jinshan Xiong (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
server: 2.1.3 RHEL6 |
||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 5300 | ||||||||
| Description |
|
This issue was created by maloo for sarah <sarah@whamcloud.com> This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/6274e3b4-fe45-11e1-a707-52540035b04c. The sub-test test_fsx failed with the following error:
fsx S 0000000000000000 0 29817 29664 0x00000080 ffff8800371ab8c8 0000000000000086 ffff8800371ab938 ffffffffa0977b76 ffff8800371ab8a8 0000000000000001 ffff8800371ab888 ffffffff81039678 ffff880077cc45f8 ffff8800371abfd8 000000000000fb88 ffff880077cc45f8 Call Trace: [<ffffffffa0977b76>] ? __osc_extent_remove+0xa6/0x440 [osc] [<ffffffff81039678>] ? pvclock_clocksource_read+0x58/0xd0 [<ffffffffa043677e>] cfs_waitq_wait+0xe/0x10 [libcfs] [<ffffffffa098013f>] osc_extent_wait+0xef/0x2a0 [osc] [<ffffffff81060250>] ? default_wake_function+0x0/0x20 [<ffffffffa0982987>] osc_cache_truncate_start+0x1cf7/0x20b0 [osc] [<ffffffffa0436be0>] ? cfs_alloc+0x30/0x60 [libcfs] [<ffffffffa07a301f>] ? null_alloc_reqbuf+0x1cf/0x440 [ptlrpc] [<ffffffffa0788727>] ? ptlrpcd_add_req+0x187/0x2e0 [ptlrpc] [<ffffffffa074e88c>] ? ptlrpc_request_bufs_pack+0x5c/0x80 [ptlrpc] [<ffffffffa0764f30>] ? lustre_swab_ost_body+0x0/0x10 [ptlrpc] [<ffffffffa0971dc4>] osc_io_setattr_start+0x294/0x4c0 [osc] [<ffffffffa061a230>] ? cl_io_start+0x0/0x140 [obdclass] [<ffffffffa061a29a>] cl_io_start+0x6a/0x140 [obdclass] [<ffffffffa0a0076e>] lov_io_call+0x8e/0x130 [lov] [<ffffffffa0a03a5c>] lov_io_start+0x10c/0x190 [lov] [<ffffffffa061a29a>] cl_io_start+0x6a/0x140 [obdclass] [<ffffffffa061ebb4>] cl_io_loop+0xb4/0x1b0 [obdclass] [<ffffffffa0abfa18>] cl_setattr_ost+0x208/0x2d0 [lustre] [<ffffffffa0a8edc2>] ll_setattr_raw+0x752/0xfd0 [lustre] [<ffffffffa0a8f69b>] ll_setattr+0x5b/0xf0 [lustre] [<ffffffff81197368>] notify_change+0x168/0x340 [<ffffffff811799a4>] do_truncate+0x64/0xa0 [<ffffffff81179c70>] sys_ftruncate+0xf0/0x100 [<ffffffff8100b0f2>] system_call_fastpath+0x16/0x1b |
| Comments |
| Comment by Alex Zhuravlev [ 26/Oct/12 ] |
|
it's likely I think this quite often: PID: 5716 TASK: ffff8800550a31c0 CPU: 0 COMMAND: "dbench" |
| Comment by Alex Zhuravlev [ 26/Oct/12 ] |
|
please, have a look. |
| Comment by Alex Zhuravlev [ 26/Oct/12 ] |
|
this time with fsx: PID: 12878 TASK: ffff880051d7a8c0 CPU: 3 COMMAND: "fsx" |
| Comment by Jinshan Xiong (Inactive) [ 13/Nov/12 ] |
|
This looks similar to |
| Comment by Jinshan Xiong (Inactive) [ 15/Nov/12 ] |
|
The issue mentioned at 26/Oct/12 3:43 AM should be a different one. It looks very like that the grant was running out. The other two occurrences are the duplicate of It's lack of information, so I can't do anything else except waiting. I'd like to suggest to lower the priority of the bug. |
| Comment by Andreas Dilger [ 20/Nov/12 ] |
|
Reducing priority on this bug. There is only a single bug triaged as |
| Comment by Andreas Dilger [ 17/Apr/17 ] |
|
Close old issue. |