[LU-11185] MGC lock leak Created: 27/Jul/18 Updated: 02/Nov/20 Resolved: 14/Dec/19 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.11.0, Lustre 2.12.0 |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Alexey Lyashkov | Assignee: | Alexey Lyashkov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
Regression introduced by 4335d232c3e6fa144d0a2d5e49264761e91b38c7. Additional bug exist, when lock is obtained but don't processed and marked as lost lock, so two locks objects refers to the single cld instance. |
| Comments |
| Comment by Alexey Lyashkov [ 27/Jul/18 ] |
|
easy reproduce with and dump an MGS namespace to the log. |
| Comment by Gerrit Updater [ 27/Jul/18 ] |
|
Alexey Lyashkov (c17817@cray.com) uploaded a new patch: https://review.whamcloud.com/32890 |
| Comment by Andreas Dilger [ 08/Aug/18 ] |
|
I don't see commit hash 4335d232c3e6fa144d in our tree. Could you please provide the summary line for this patch. |
| Comment by Alexey Lyashkov [ 08/Aug/18 ] |
|
commit 4335d232c3e6fa144d0a2d5e49264761e91b38c7 This patch does the following work: Signed-off-by: Jinshan Xiong <jay@whamcloud.com> |
| Comment by Andreas Dilger [ 09/Aug/18 ] |
|
Is this in some other branch? I still can't find that commit hash, but that patch is very old - 2011, so it should be in every release available today. The commit hash on master for that patch is 5538eee216a194d47ae67fbcff80bfbcd95f3d69. |
| Comment by Gerrit Updater [ 14/Dec/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/32890/ |
| Comment by Peter Jones [ 14/Dec/19 ] |
|
Landed for 2.14 |
| Comment by Gerrit Updater [ 02/Nov/20 ] |
|
Jian Yu (yujian@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/40520 |