Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
3
-
9223372036854775807
Description
Current test implementation have a two bugs.
1) client mgc llogs processing is async to mount, so we can start a lock check before all locks processed, it caused a false alarm.
2) Server locks counting is unsafe, as it include an other server locks. so Any client reconnect may cause a false alarm.
Let's fix it.
Attachments
Issue Links
- is related to
-
LU-13231 sanity test_901: FAIL: mgs lock leak (34 != 37)
-
- Open
-