Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
3
-
9223372036854775807
Description
'lctl lfsck_stop ...' stops all lfsck threads on current node synchronously, and it also notifies slave nodes to stop lfsck threads there, but it's asynchronous, and when this command returns, lfsck threads on slave nodes may not stop yet.
This may cause some sanity-lfsck.sh test fail because when one test finishes, there are lfsck threads left on slave nodes, and it may cause the next test fail.
To fix this issue, a new function lfsck_stop_wait() can be added, which stops lfsck on master node, and also wait for lfsck stop on all server nodes.
Attachments
Issue Links
- is related to
-
EX-14175 Loading...