[LU-619] Recursive locking in ldlm_lock_change_resource Created: 23/Aug/11 Updated: 29/May/17 Resolved: 29/May/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 1.8.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Mark Hills | Assignee: | WC Triage |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Client: Lustre b1_8 Git 999530e, Linux 2.6.32.8 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 10723 | ||||||||
| Description |
|
I am using a vanilla kernel built with additional lock debugging. After mounting the Lustre, the first invocation of a simple 'ls' command results in a kernel warning of a recursive lock. This is on the client side. Whether server 1.8 or 1.6 is used does not make a difference. The log below was taken with the following server packages, and the full log is attached: lustre: 1.8.6 ============================================= but task is already holding lock: other info that might help us debug this: stack backtrace: |
| Comments |
| Comment by Mark Hills [ 23/Aug/11 ] |
|
Kernel config |
| Comment by Andreas Dilger [ 29/May/17 ] |
|
Close old ticket. |