[LU-4776] suite sanity-scrub: ASSERTION( info->oti_r_locks == 0 ) Created: 18/Mar/14 Updated: 14/May/20 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.7.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Maloo | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 13141 | ||||||||
| Description |
|
This issue was created by maloo for Dmitry Eremin <dmitry.eremin@intel.com> This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/6cce6894-ae66-11e3-9c2b-52540035b04c. 17:25:05:LustreError: 18368:0:(osd_handler.c:5496:osd_key_exit()) ASSERTION( info->oti_r_locks == 0 ) failed: |
| Comments |
| Comment by Jodi Levi (Inactive) [ 18/Mar/14 ] |
|
Fan Yong and Di, |
| Comment by nasf (Inactive) [ 19/Mar/14 ] |
|
Firstly, the ASSERT() indicates that someone called dt_read_lock() but missed to call dt_read_unlock(). Secondly, the ASSERT() happened inside ptlrpcd thread stack, generally, the ptlrpcd thread should not call dt_ {read,write}_lock() to avoid blocked. Only with this log, it is not easy to locate where the issue is. Either more logs or read related code and check each dt_read_lock() one by one. |
| Comment by Nathaniel Clark [ 02/Jun/14 ] |
|
Another instance review-dne-part-1 conf-sanity/22 on master: |
| Comment by Jian Yu [ 20/Oct/14 ] |
|
The failure occurred while testing patch http://review.whamcloud.com/11213 on master branch with DNE configuration: |
| Comment by Yang Sheng [ 14/May/20 ] |
|
Another instance: |